
Since odoo/documentation#903, the guideline for the location of new resource (images, downloadable files, RST includes...) files is to place those inside the directory of the RST page that references them. For example, if `doc1.rst` has a reference to `image.png` and to `download.zip`, the file structure should look like this: ├── parent_doc/ │ └── doc1/ │ │ └── image.png │ │ └── download.zip │ └── doc1.rst │ └── doc2.rst ├── parent_doc.rst Before this commit, most of the resource files were still located inside 'media' directories holding all the resource files referenced by RST pages located at the same level as these directories. In the example above, a single 'media' directory would hold all the resource files referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from figuring out easily which resource file was referenced by which RST page and, thus, lead to unused resource files piling up in the repository. It also made it more complicated to define codeowners regex rules because a team could not simply be assigned to `/some_page.*` but needed to be assigned to both `/some_page\.rst` and to the location of 'media'. In order to help new content writers figure out the guideline when taking examples from other RST pages, this commit retroactively applies the guideline to existing resource files and 'media' directories. The left-over resource files that are not referenced by any RST page are removed. task-2497965 Part-of: odoo/documentation#2068
55 lines
1.9 KiB
ReStructuredText
55 lines
1.9 KiB
ReStructuredText
======================================
|
|
Allow Customers to Close their Tickets
|
|
======================================
|
|
|
|
Allowing customers to close their tickets gives them autonomy and minimize misunderstandings about
|
|
when an issue is considered solved, or not. It makes communication and actions more efficient.
|
|
|
|
Configure the feature
|
|
=====================
|
|
|
|
To configure the feature go to :menuselection:`Helpdesk --> Settings --> Helpdesk Teams --> Edit`
|
|
and enable *Ticket closing*.
|
|
|
|
.. image:: close_tickets/closetickets1.png
|
|
:align: center
|
|
:alt: Ticket closing in Odoo Helpdesk
|
|
|
|
In order to designate to which stage the ticket migrates to once it is closed, go to
|
|
:menuselection:`Helpdesk --> Overview --> Tickets`.
|
|
|
|
.. image:: close_tickets/closetickets2.png
|
|
:align: center
|
|
:alt: Ticket closing in Odoo Helpdesk
|
|
|
|
You can either create a new Kanban stage or work with an existing one. For both scenarios, go to
|
|
:menuselection:`Helpdesk --> Settings --> Edit Stage` and enable *Closing Stage*.
|
|
|
|
.. image:: close_tickets/closetickets3.png
|
|
:align: center
|
|
:alt: Ticket closing in Odoo Helpdesk
|
|
|
|
If a closing stage is not specified, by default, the ticket is moved to the last stage;
|
|
contrarily, if you have more than one stage set as closing, the ticket is put in the first one.
|
|
|
|
The Costumer Portal
|
|
===================
|
|
|
|
Now, once the user logs into his Portal, the option *Close this ticket* is available.
|
|
|
|
.. image:: close_tickets/closetickets4.png
|
|
:align: center
|
|
:alt: Ticket closing in Odoo Helpdesk
|
|
|
|
Get reports on tickets closed by costumers
|
|
==========================================
|
|
|
|
To do an analysis of the tickets that have been closed by costumers go to
|
|
:menuselection:`Helpdesk --> Reporting --> Tickets --> Filters --> Add Custom filter -->
|
|
Closed by partner --> Applied`.
|
|
|
|
.. image:: close_tickets/closetickets5.png
|
|
:align: center
|
|
:height: 300
|
|
:alt: Reports on Ticket closing in Odoo Helpdesk
|