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
127 lines
4.0 KiB
ReStructuredText
127 lines
4.0 KiB
ReStructuredText
===================================
|
|
Record and invoice time for tickets
|
|
===================================
|
|
|
|
You may have service contracts with your clients to provide them
|
|
assistance in case of a problem. For this purpose, Odoo will help you
|
|
record the time spent fixing the issue and most importantly, to invoice
|
|
it to your clients.
|
|
|
|
The modules needed
|
|
==================
|
|
|
|
In order to record and invoice time for tickets, the following modules
|
|
are needed : Helpdesk, Project, Timesheets, Sales. If you are missing
|
|
one of them, go to the Apps module, search for it and then click on
|
|
*Install*.
|
|
|
|
Get started to offer the helpdesk service
|
|
=========================================
|
|
|
|
Step 1 : start a helpdesk project
|
|
---------------------------------
|
|
|
|
To start a dedicated project for the helpdesk service, first go to
|
|
:menuselection:`Project --> Configuration --> Settings` and make sure
|
|
that the *Timesheets* feature is activated.
|
|
|
|
.. image:: media/invoice_time01.png
|
|
:align: center
|
|
|
|
Then, go to your dashboard, create the new project and allow timesheets
|
|
for it.
|
|
|
|
Step 2 : gather a helpdesk team
|
|
-------------------------------
|
|
|
|
To set a team in charge of the helpdesk, go to :menuselection:`Helpdesk
|
|
--> Configuration --> Helpdesk Teams` and create a new team or select
|
|
an existing one. On the form, tick the box in front of *Timesheet on
|
|
Ticket* to activate the feature. Make sure to select the helpdesk
|
|
project you have previously created as well.
|
|
|
|
.. image:: media/invoice_time02.png
|
|
:align: center
|
|
|
|
Step 3 : launch the helpdesk service
|
|
------------------------------------
|
|
|
|
Finally, to launch the new helpdesk service, first go to
|
|
:menuselection:`Sales --> Configuration --> Settings` and make sure
|
|
that the *Units of Measure* feature is activated.
|
|
|
|
.. image:: media/invoice_time03.png
|
|
:align: center
|
|
|
|
Then, go to :menuselection:`Products --> Products` and create a new
|
|
one. Make sure that the product is set as a service.
|
|
|
|
.. image:: media/invoice_time04.png
|
|
:align: center
|
|
|
|
.. note::
|
|
Here, we suggest that you set the *Unit of Measure* as
|
|
*Hour(s)*, but any unit will do.
|
|
|
|
Finally, select the invoicing management you would like to have under
|
|
the *Sales* tab of the product form. Here, we recommend the following
|
|
configuration :
|
|
|
|
.. image:: media/invoice_time05.png
|
|
:align: center
|
|
|
|
Now, you are ready to start receiving tickets !
|
|
|
|
Solve issues and record time spent
|
|
==================================
|
|
|
|
Step 1 : place an order
|
|
-----------------------
|
|
|
|
You are now in the Helpdesk module and you have just received a ticket
|
|
from a client. To place a new order, go to :menuselection:`Sales -->
|
|
Orders --> Orders` and create one for the help desk service product you
|
|
have previously recorded. Set the number of hours needed to assist the
|
|
client and confirm the sale.
|
|
|
|
.. image:: media/invoice_time06.png
|
|
:align: center
|
|
|
|
Step 2 : link the task to the ticket
|
|
------------------------------------
|
|
|
|
If you access the dedicated helpdesk project, you will notice that a new
|
|
task has automatically been generated with the order. To link this task
|
|
with the client ticket, go to the Helpdesk module, access the ticket in
|
|
question and select the task on its form.
|
|
|
|
.. image:: media/invoice_time07.png
|
|
:align: center
|
|
|
|
Step 3 : record the time spent to help the client
|
|
-------------------------------------------------
|
|
|
|
The job is done and the client's issue is sorted out. To record the
|
|
hours performed for this task, go back to the ticket form and add them
|
|
under the *Timesheets* tab.
|
|
|
|
.. image:: media/invoice_time08.png
|
|
:align: center
|
|
|
|
.. tip::
|
|
The hours recorded on the ticket will also automatically appear
|
|
in the Timesheet module and on the dedicated task.
|
|
|
|
Step 4 : invoice the client
|
|
---------------------------
|
|
|
|
To invoice the client, go back to the Sales module and select the order
|
|
that had been placed. Notice that the hours recorded on the ticket form
|
|
now appear as the delivered quantity.
|
|
|
|
.. image:: media/invoice_time09.png
|
|
:align: center
|
|
|
|
All that is left to do, is to create the invoice from the order and then
|
|
validate it. Now you just have to wait for the client's payment !
|