Antoine Vandevenne (anv)
e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
109 lines
3.1 KiB
ReStructuredText
109 lines
3.1 KiB
ReStructuredText
======================================
|
|
How to gather feedback from customers?
|
|
======================================
|
|
|
|
Overview
|
|
========
|
|
|
|
As a manager, it's not always simple to follow everything your teams do.
|
|
Having a simple customer feedback can be very interesting to evaluate
|
|
the performances of your teams. You can very easily gather feedbacks
|
|
from your customers using Odoo.
|
|
|
|
An e-mail can be sent during the project to get the customer feedbacks.
|
|
He just has to choose between 3 smileys to assess your work (Smile,
|
|
Neutral or Sad).
|
|
|
|
How to gather feedbacks from customers
|
|
======================================
|
|
|
|
Before getting started some configuration is necessary. First of all
|
|
it's necessary to install the **Project** application. To do so simply
|
|
go to the apps module and install it.
|
|
|
|
.. image:: media/feedback01.png
|
|
:align: center
|
|
|
|
Moreover, in the same menu, you have to install the **Project Rating**
|
|
module.
|
|
|
|
.. image:: media/feedback02.png
|
|
:align: center
|
|
|
|
Next, go back into the back-end and enter the project module. Select the
|
|
**Configuration** button and click on **Settings** in the dropdown menu. Next
|
|
select **Allow activating customer rating on projects, at issue
|
|
completion**. Don't forget to apply your changes.
|
|
|
|
.. image:: media/feedback03.png
|
|
:align: center
|
|
|
|
How to get a Customer feedback?
|
|
===============================
|
|
|
|
A e-mail can be sent to the customers at each stage of the ongoing
|
|
projects.
|
|
|
|
First, you need to choose for which projects you want to get a feedback.
|
|
|
|
Project configuration
|
|
---------------------
|
|
|
|
Go to the **Project** application, in the project settings select the
|
|
**Customer satisfaction** option.
|
|
|
|
.. image:: media/feedback04.png
|
|
:align: center
|
|
|
|
Email Template
|
|
--------------
|
|
|
|
Go to the stage settings (click on the gear icon on the top of the stage
|
|
column, then select **Edit**). Choose the e-mail template that will be used.
|
|
You can directly edit it from there.
|
|
|
|
.. image:: media/feedback05.png
|
|
:align: center
|
|
|
|
Here is an email example that a customer can receive :
|
|
|
|
.. image:: media/feedback06.png
|
|
:align: center
|
|
|
|
.. note::
|
|
The customer just has to click on a smiley (Smile, Neutral or
|
|
Sad) to assess your work. The customer can reply to the email to add
|
|
more information. It will be added to the chatter of the task.
|
|
|
|
Reporting
|
|
---------
|
|
|
|
You have a brief summary on the satisfaction in the upper right corner
|
|
of the project.
|
|
|
|
.. image:: media/feedback07.png
|
|
:align: center
|
|
|
|
How to display the ratings on your website?
|
|
===========================================
|
|
|
|
First of all it's necessary to install the **Website Builder** application.
|
|
To do so simply go to the apps module and search for the website
|
|
builder.
|
|
|
|
.. image:: media/feedback08.png
|
|
:align: center
|
|
|
|
Moreover, in the same menu, you have to install the **Website Rating
|
|
Project Issue** module.
|
|
|
|
.. image:: media/feedback09.png
|
|
:align: center
|
|
|
|
Then, you will be able to publish your result on your website by
|
|
clicking on the website button in the upper right corner and confirming
|
|
it in the front end of the website.
|
|
|
|
.. image:: media/feedback10.png
|
|
:align: center
|