[MOV] content/*: move resource files into their related page's directory
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#2064
@@ -9,13 +9,13 @@ Configure the helpdesk team
|
||||
Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select a team and enable
|
||||
*Onsite Interventions*.
|
||||
|
||||
.. image:: media/onsite-interventions-helpdesk-setting.png
|
||||
.. image:: plan_onsite/onsite-interventions-helpdesk-setting.png
|
||||
:align: center
|
||||
:alt: Onsite interventions setting in Odoo Helpdesk
|
||||
|
||||
The helpdesk tickets of the team now display the *Plan Intervention* button. Click on it to create a
|
||||
new task under your field service project.
|
||||
|
||||
.. image:: media/plan-intervention-from-ticket.png
|
||||
.. image:: plan_onsite/plan-intervention-from-ticket.png
|
||||
:align: center
|
||||
:alt: Plan intervention from helpdesk ticket in Odoo Helpdesk
|
||||
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 16 KiB |
@@ -18,13 +18,13 @@ Go to :menuselection:`Field Service --> Configuration --> Products` and create o
|
||||
|
||||
#. If you use them, select your *Worksheet Template* and then click on *Save*.
|
||||
|
||||
.. image:: media/product-configuration-tasks-from-sales-orders.png
|
||||
.. image:: onsite_tasks_from_sales_orders/product-configuration-tasks-from-sales-orders.png
|
||||
:align: center
|
||||
:alt: Product configuration to create tasks from sales orders in Odoo Field Service
|
||||
|
||||
From the *Sales* app, create a quotation with the product and confirm it. A task is automatically
|
||||
set up under your Field Service project. It is directly accessible from the sales order.
|
||||
|
||||
.. image:: media/field-service-task-on-sales-order.png
|
||||
.. image:: onsite_tasks_from_sales_orders/field-service-task-on-sales-order.png
|
||||
:align: center
|
||||
:alt: Field Service task on a sales order in Odoo Sales
|
||||
|
Before Width: | Height: | Size: 5.8 KiB After Width: | Height: | Size: 5.8 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
@@ -13,7 +13,7 @@ Set up the after sales services
|
||||
Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable the after sales
|
||||
options: *Refunds, Returns, Coupons, Repairs and Onsite Interventions*.
|
||||
|
||||
.. image:: ./media/aftersales1.png
|
||||
.. image:: after_sales/aftersales1.png
|
||||
:align: center
|
||||
|
||||
Generate credit notes from tickets
|
||||
@@ -23,7 +23,7 @@ You can use a credit note to refund a customer or adjust the amount due. For tha
|
||||
your ticket page, click on *Refund* and select the corresponding *Invoice*. Clicking on *Reverse*
|
||||
generates a credit note, and you can *Post* it while still being in the *Helpdesk* app.
|
||||
|
||||
.. image:: ./media/aftersales2.png
|
||||
.. image:: after_sales/aftersales2.png
|
||||
:align: center
|
||||
|
||||
Allow product returns from tickets
|
||||
@@ -32,7 +32,7 @@ Allow product returns from tickets
|
||||
The process of a product return from your customer back to your warehouse is taken into action when,
|
||||
at the ticket page, you choose the option *Return*.
|
||||
|
||||
.. image:: ./media/aftersales3.png
|
||||
.. image:: after_sales/aftersales3.png
|
||||
:align: center
|
||||
|
||||
Grant coupons from tickets
|
||||
@@ -41,7 +41,7 @@ Grant coupons from tickets
|
||||
First, be sure to have your *Coupon Program* planned in the *Sales* or *Website* application. Then,
|
||||
in *Helpdesk*, open your ticket, click on *Coupon*, and choose the respective one.
|
||||
|
||||
.. image:: ./media/aftersales4.png
|
||||
.. image:: after_sales/aftersales4.png
|
||||
:align: center
|
||||
|
||||
Repairs from tickets
|
||||
@@ -50,7 +50,7 @@ Repairs from tickets
|
||||
Clicking on *Repair* option, on your ticket page, a new repair order form is shown. Fill in the
|
||||
information as needed and choose the next step.
|
||||
|
||||
.. image:: ./media/aftersales5.png
|
||||
.. image:: after_sales/aftersales5.png
|
||||
:align: center
|
||||
|
||||
Plan onsite interventions from tickets
|
||||
@@ -59,7 +59,7 @@ Plan onsite interventions from tickets
|
||||
At the ticket's page click on *Plan Intervention*, and set up your onsite intervention exactly the
|
||||
same way as if you were on the *Field Service* application.
|
||||
|
||||
.. image:: ./media/aftersales6.png
|
||||
.. image:: after_sales/aftersales6.png
|
||||
:align: center
|
||||
:height: 300
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 8.8 KiB After Width: | Height: | Size: 8.8 KiB |
|
Before Width: | Height: | Size: 25 KiB After Width: | Height: | Size: 25 KiB |
|
Before Width: | Height: | Size: 4.4 KiB After Width: | Height: | Size: 4.4 KiB |
|
Before Width: | Height: | Size: 2.2 KiB After Width: | Height: | Size: 2.2 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 16 KiB |
@@ -11,21 +11,21 @@ Configure the feature
|
||||
To configure the feature go to :menuselection:`Helpdesk --> Settings --> Helpdesk Teams --> Edit`
|
||||
and enable *Ticket closing*.
|
||||
|
||||
.. image:: media/closetickets1.png
|
||||
.. 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:: media/closetickets2.png
|
||||
.. 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:: media/closetickets3.png
|
||||
.. image:: close_tickets/closetickets3.png
|
||||
:align: center
|
||||
:alt: Ticket closing in Odoo Helpdesk
|
||||
|
||||
@@ -37,7 +37,7 @@ The Costumer Portal
|
||||
|
||||
Now, once the user logs into his Portal, the option *Close this ticket* is available.
|
||||
|
||||
.. image:: media/closetickets4.png
|
||||
.. image:: close_tickets/closetickets4.png
|
||||
:align: center
|
||||
:alt: Ticket closing in Odoo Helpdesk
|
||||
|
||||
@@ -48,7 +48,7 @@ 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:: media/closetickets5.png
|
||||
.. image:: close_tickets/closetickets5.png
|
||||
:align: center
|
||||
:height: 300
|
||||
:alt: Reports on Ticket closing in Odoo Helpdesk
|
||||
|
||||
|
Before Width: | Height: | Size: 5.0 KiB After Width: | Height: | Size: 5.0 KiB |
|
Before Width: | Height: | Size: 9.8 KiB After Width: | Height: | Size: 9.8 KiB |
|
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 58 KiB |
|
Before Width: | Height: | Size: 4.6 KiB After Width: | Height: | Size: 4.6 KiB |
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 15 KiB |
@@ -15,7 +15,7 @@ Set up
|
||||
|
||||
Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and enable *Help Center*.
|
||||
|
||||
.. image:: media/help_center_feature.png
|
||||
.. image:: forum_and_elearning/help_center_feature.png
|
||||
:align: center
|
||||
:alt: Overview of the settings page of a helpdesk team emphasizing the help center feature in
|
||||
Odoo Helpdesk
|
||||
@@ -24,20 +24,20 @@ Create, or edit a forum by clicking on the external link. Among the editing opti
|
||||
if you would like the *Forum Mode* to be *Questions*: only one answer is allowed per question or
|
||||
*Discussions*: multiple answers are allowed per question.
|
||||
|
||||
.. image:: media/help_center_customer_care.png
|
||||
.. image:: forum_and_elearning/help_center_customer_care.png
|
||||
:align: center
|
||||
:alt: Overview of a forum’s settings page in Odoo Helpdesk
|
||||
|
||||
From now on, logged in users can start their discussions. To keep track of posts, go to
|
||||
:menuselection:`Website --> Forum --> Posts`.
|
||||
|
||||
.. image:: media/customer_care_website.png
|
||||
.. image:: forum_and_elearning/customer_care_website.png
|
||||
:align: center
|
||||
:alt: Overview of the Forums page of a website to show the available ones in Odoo Helpdesk
|
||||
|
||||
Turn tickets into forum posts by simply clicking on *Share on the Forum* on the ticket's page.
|
||||
|
||||
.. image:: media/share_forum.png
|
||||
.. image:: forum_and_elearning/share_forum.png
|
||||
:align: center
|
||||
:alt: Overview of the Forums page of a website to show the available ones in Odoo Helpdesk
|
||||
|
||||
@@ -53,20 +53,20 @@ Set up
|
||||
|
||||
Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *eLearning*.
|
||||
|
||||
.. image:: media/elearning_feature.png
|
||||
.. image:: forum_and_elearning/elearning_feature.png
|
||||
:align: center
|
||||
:alt: Overview of the settings page of a customer care team emphasizing the feature elearning in
|
||||
Odoo Helpdesk
|
||||
|
||||
Once the structure and content of your course are ready, *Publish* it by clicking on *Unpublished*.
|
||||
|
||||
.. image:: media/course_website.png
|
||||
.. image:: forum_and_elearning/course_website.png
|
||||
:align: center
|
||||
:alt: View of a course being published for Odoo Helpdesk
|
||||
|
||||
To keep track of your course statistics, go to *eLearning* and *View Course*.
|
||||
|
||||
.. image:: media/view_course_elearning.png
|
||||
.. image:: forum_and_elearning/view_course_elearning.png
|
||||
:align: center
|
||||
:alt: View of the elearning applications dashboard for Odoo Helpdesk
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 141 KiB After Width: | Height: | Size: 141 KiB |
|
Before Width: | Height: | Size: 107 KiB After Width: | Height: | Size: 107 KiB |
|
Before Width: | Height: | Size: 75 KiB After Width: | Height: | Size: 75 KiB |
|
Before Width: | Height: | Size: 47 KiB After Width: | Height: | Size: 47 KiB |
|
Before Width: | Height: | Size: 54 KiB After Width: | Height: | Size: 54 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
@@ -13,7 +13,7 @@ Set up teams
|
||||
| Setting up multiple teams allows you to group tickets by your channels (example: BE/US), or by
|
||||
your support services' types (example: IT, accounting, admin, etc.).
|
||||
|
||||
.. image:: media/helpdesk_teams_view.png
|
||||
.. image:: getting_started/helpdesk_teams_view.png
|
||||
:align: center
|
||||
:alt: View of the helpdesk teams page in Odoo Helpdesk
|
||||
|
||||
@@ -30,7 +30,7 @@ person:
|
||||
- *Balanced*: tickets are assigned to the person with the least amount of tickets so that everyone
|
||||
fairly gets the same amount. Thereby, you ensure that all tickets get to be taken care of.
|
||||
|
||||
.. image:: media/productivity_visibility.png
|
||||
.. image:: getting_started/productivity_visibility.png
|
||||
:align: center
|
||||
:alt: View of a helpdesk team settings page emphasizing the productivity and visibility features
|
||||
in Odoo Helpdesk
|
||||
@@ -48,7 +48,7 @@ Set up stages and share it among teams
|
||||
To set up stages, go to :menuselection:`Helpdesk --> Configuration --> Stages`. Then, create and/or
|
||||
edit stages as you need and set specific teams to use certain stages under *Team*.
|
||||
|
||||
.. image:: media/stages_teams.png
|
||||
.. image:: getting_started/stages_teams.png
|
||||
:align: center
|
||||
:alt: View of a stage’s setting page emphasizing the option to add teams in Odoo Helpdesk
|
||||
|
||||
@@ -56,7 +56,7 @@ Stages can be shared between one or multiple teams, allowing you to adapt the pi
|
||||
individual needs. They also apply a visibility and access rule, as other teams are not able to see
|
||||
or use the stage.
|
||||
|
||||
.. image:: media/helpdesk_kanbanview.png
|
||||
.. image:: getting_started/helpdesk_kanbanview.png
|
||||
:align: center
|
||||
:alt: View of a team’s kanban view in Odoo Helpdesk
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 66 KiB After Width: | Height: | Size: 66 KiB |
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 38 KiB After Width: | Height: | Size: 38 KiB |
|
Before Width: | Height: | Size: 35 KiB After Width: | Height: | Size: 35 KiB |
@@ -13,7 +13,7 @@ Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable
|
||||
tickets*. The feature automatically adds a default email template on the non-folded *closing
|
||||
stage(s)* of that team.
|
||||
|
||||
.. image:: media/ratings_on_tickets.png
|
||||
.. image:: ratings/ratings_on_tickets.png
|
||||
:align: center
|
||||
:alt: Overview of the settings page of a helpdesk team emphasizing the rating on ticket feature
|
||||
in Odoo Helpdesk
|
||||
@@ -21,14 +21,14 @@ stage(s)* of that team.
|
||||
To edit the email template and the stage(s) set as the closing ones, go to the Kanban view of your
|
||||
helpdesk team and click on *Settings*, then on *Edit Stage*.
|
||||
|
||||
.. image:: media/edit_stage.png
|
||||
.. image:: ratings/edit_stage.png
|
||||
:align: center
|
||||
:alt: Overview of a helpdesk team kanban view emphasizing the menu edit stage in Odoo Helpdesk
|
||||
|
||||
Now, once a ticket reaches the stage(s) designated as the *Closing Stage*, an email is sent to the
|
||||
customer.
|
||||
|
||||
.. image:: media/email_customer_feedback.png
|
||||
.. image:: ratings/email_customer_feedback.png
|
||||
:align: center
|
||||
:alt: View of a standard helpdesk customer review email template for Odoo Helpdesk
|
||||
|
||||
@@ -42,7 +42,7 @@ Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable
|
||||
Customer Portal*. Now, by clicking on the helpdesk team’s name on their ticket, customers can see
|
||||
its ratings.
|
||||
|
||||
.. image:: media/customer_portal.png
|
||||
.. image:: ratings/customer_portal.png
|
||||
:align: center
|
||||
:alt: View of the helpdesk ticket from a user’s portal emphasizing the link to the helpdesk team
|
||||
in Odoo Helpdesk
|
||||
|
||||
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 24 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 61 KiB After Width: | Height: | Size: 61 KiB |
@@ -13,7 +13,7 @@ Channels options to submit tickets
|
||||
Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, and enable the following
|
||||
features as you want them to be available to your users.
|
||||
|
||||
.. image:: media/channels_options.png
|
||||
.. image:: receiving_tickets/channels_options.png
|
||||
:align: center
|
||||
:alt: View of a helpdesk teams setting page emphasizing the channels options in Odoo Helpdesk
|
||||
|
||||
@@ -25,7 +25,7 @@ Email Alias
|
||||
| Select *Configure domain name* to be redirected to *Settings* and, from there, enable *External
|
||||
Email Servers* to determine or change your *Alias Domain*.
|
||||
|
||||
.. image:: media/channels_emailalias.png
|
||||
.. image:: receiving_tickets/channels_emailalias.png
|
||||
:align: center
|
||||
:height: 250
|
||||
:alt: View of the settings page of a helpdesk team emphasizing the email alias feature
|
||||
@@ -41,14 +41,14 @@ Website Form
|
||||
| Allow your customers to submit a ticket by filling in a form through your website.
|
||||
| Once the feature is activated, get redirected to your website by clicking on *Go to Website*.
|
||||
|
||||
.. image:: media/go_to_website.png
|
||||
.. image:: receiving_tickets/go_to_website.png
|
||||
:align: center
|
||||
:alt: View of the settings page of a helpdesk team emphasizing the Go to Website button in
|
||||
Odoo Helpdesk
|
||||
|
||||
From the website page customize the form as you like. Then, publish it by clicking on *Unpublished*.
|
||||
|
||||
.. image:: media/submit_a_ticket_form.png
|
||||
.. image:: receiving_tickets/submit_a_ticket_form.png
|
||||
:align: center
|
||||
:alt: View of the website form to submit a ticket for Odoo Helpdesk
|
||||
|
||||
@@ -60,7 +60,7 @@ Live Chat
|
||||
| Click on your helpdesk team's name - for the example below: *Customer Care* -
|
||||
and :doc:`set up your channel </applications/websites/livechat/overview/get_started>`.
|
||||
|
||||
.. image:: media/live_chat.png
|
||||
.. image:: receiving_tickets/live_chat.png
|
||||
:align: center
|
||||
:alt: View of the settings page of a helpdesk team emphasizing the live chat features and links
|
||||
in Odoo Helpdesk
|
||||
@@ -78,7 +78,7 @@ the Kanban view.
|
||||
- 2 stars = *High priority*
|
||||
- 3 stars = *Urgent*
|
||||
|
||||
.. image:: media/kanban_view_prioritize.png
|
||||
.. image:: receiving_tickets/kanban_view_prioritize.png
|
||||
:align: center
|
||||
:height: 330
|
||||
:alt: View of a team’s kanban view and the prioritized tasks in Odoo Helpdesk
|
||||
|
||||
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 27 KiB After Width: | Height: | Size: 27 KiB |
|
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 21 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 15 KiB |
@@ -18,7 +18,7 @@ Some examples of the reports Odoo Helpdesk can generate include:
|
||||
| Apply *Time Ranges* if you would like to make comparisons to a *Previous Period* or a *Previous
|
||||
Year*.
|
||||
|
||||
.. image:: media/report_team_ticket_type.png
|
||||
.. image:: reports/report_team_ticket_type.png
|
||||
:align: center
|
||||
:alt: View of a helpdesk ticket analysis by team and ticket type in Odoo Helpdesk
|
||||
|
||||
@@ -27,7 +27,7 @@ Some examples of the reports Odoo Helpdesk can generate include:
|
||||
Get an overview of how many requests each team is closing per day in order to measure their
|
||||
performance. Identify productivity levels to understand how many requests they are able to handle.
|
||||
|
||||
.. image:: media/report_close_date_team.png
|
||||
.. image:: reports/report_close_date_team.png
|
||||
:align: center
|
||||
:alt: View of a helpdesk ticket analysis by team and close date in Odoo Helpdesk
|
||||
|
||||
@@ -39,7 +39,7 @@ performance. Identify productivity levels to understand how many requests they a
|
||||
Check if your expectations are met by *measuring* the *Time to close (hours)*. Your
|
||||
customers not only expect fast responses but they also want their issues to be handled quickly.
|
||||
|
||||
.. image:: media/report_time_to_close.png
|
||||
.. image:: reports/report_time_to_close.png
|
||||
:align: center
|
||||
:alt: View of helpdesk ticket analysis of the hours to close by ticket type and team in
|
||||
Odoo Helpdesk
|
||||
@@ -50,7 +50,7 @@ Save filters
|
||||
Save the filters you use the most and avoid having to reconstruct them every time they are
|
||||
needed. To do so, set the groups, filters, and measures needed. Then, go to *Favorites*.
|
||||
|
||||
.. image:: media/favorites.png
|
||||
.. image:: reports/favorites.png
|
||||
:align: center
|
||||
:alt: View of helpdesk ticket analysis emphasizing the option to add a filter as a favorite one
|
||||
in Odoo Helpdesk
|
||||
|
||||
|
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 64 KiB |
|
Before Width: | Height: | Size: 48 KiB After Width: | Height: | Size: 48 KiB |
|
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 58 KiB |
|
Before Width: | Height: | Size: 61 KiB After Width: | Height: | Size: 61 KiB |
@@ -14,7 +14,7 @@ Create your policies
|
||||
| Create your policies through the team’s settings page or go to :menuselection:`Helpdesk -->
|
||||
Configuration --> SLA Policies`.
|
||||
|
||||
.. image:: media/new_sla.png
|
||||
.. image:: sla/new_sla.png
|
||||
:align: center
|
||||
:height: 340
|
||||
:alt: View of an SLA form in Odoo Helpdesk
|
||||
@@ -28,7 +28,7 @@ Create your policies
|
||||
| When a ticket has satisfied an SLA policy, the SLA tag appears in green and the deadline field
|
||||
is not shown anymore.
|
||||
|
||||
.. image:: media/ticket_green_tag.png
|
||||
.. image:: sla/ticket_green_tag.png
|
||||
:align: center
|
||||
:height: 330
|
||||
:alt: View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk
|
||||
@@ -39,7 +39,7 @@ SLA Analysis
|
||||
Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply *Filters* and
|
||||
*Group by* to identify tickets that should be prioritized and keep track of upcoming deadlines.
|
||||
|
||||
.. image:: media/sla_analysis.png
|
||||
.. image:: sla/sla_analysis.png
|
||||
:align: center
|
||||
:alt: View of the SLA status analysis page emphasizing the group by option in Odoo Helpdesk
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 37 KiB After Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 43 KiB |
@@ -19,7 +19,7 @@ Step 1: Set up a helpdesk team
|
||||
the one at which employees timesheet on by default. However, it can be ultimately modified on
|
||||
each ticket.
|
||||
|
||||
.. image:: media/sell_track_hours.png
|
||||
.. image:: invoice_time/sell_track_hours.png
|
||||
:align: center
|
||||
:alt: View of a helpdesk team settings page emphasizing the timesheet on ticket and time
|
||||
reinvoicing features in Odoo Helpdesk
|
||||
@@ -32,7 +32,7 @@ Step 2: Set up a service
|
||||
| Then, go to :menuselection:`Sales --> Products --> Products`, create or edit an existing one, and
|
||||
set its *Product Type* as *Service*.
|
||||
|
||||
.. image:: media/product_type_unit.png
|
||||
.. image:: invoice_time/product_type_unit.png
|
||||
:align: center
|
||||
:alt: View of a product's form emphasizing the product type and unit of measure fields in Odoo
|
||||
Sales
|
||||
@@ -40,7 +40,7 @@ Step 2: Set up a service
|
||||
Now, select the invoicing management you would like to have under the *Sales* tab. We recommend the
|
||||
following configuration:
|
||||
|
||||
.. image:: media/product_invoicing.png
|
||||
.. image:: invoice_time/product_invoicing.png
|
||||
:align: center
|
||||
:alt: View of a product form and the invoicing options under the tab sales in Odoo Sales
|
||||
|
||||
@@ -64,7 +64,7 @@ Go to :menuselection:`Sales --> Orders --> Orders` and create one for the helpde
|
||||
you have previously set up, with the customer who needs the ticket to be opened. Set the number of
|
||||
hours needed to assist the customer and *Confirm* the order.
|
||||
|
||||
.. image:: media/sales_order_new.png
|
||||
.. image:: invoice_time/sales_order_new.png
|
||||
:align: center
|
||||
:alt: View of a sales order emphasizing the order lines in Odoo Sales
|
||||
|
||||
@@ -73,7 +73,7 @@ Step 2: Invoice the customer
|
||||
|
||||
In *Sales*, select the respective sales order to *Create Invoice*.
|
||||
|
||||
.. image:: media/create_invoice.png
|
||||
.. image:: invoice_time/create_invoice.png
|
||||
:align: center
|
||||
:height: 330
|
||||
:alt: View of a sales order emphasizing the create invoice button in Odoo Sales
|
||||
@@ -84,7 +84,7 @@ Step 3: Link the task to the ticket
|
||||
Now, in *Helpdesk*, create or edit the respective ticket and link it to the task created by the
|
||||
confirmation of the sales order.
|
||||
|
||||
.. image:: media/helpdesk_task.png
|
||||
.. image:: invoice_time/helpdesk_task.png
|
||||
:align: center
|
||||
:alt: View of a helpdesk ticket emphasizing the field task in Odoo Helpdesk
|
||||
|
||||
@@ -93,14 +93,14 @@ Step 4: Record the time spent
|
||||
|
||||
Still on the respective helpdesk ticket, record the hours performed under the *Timesheets* tab.
|
||||
|
||||
.. image:: media/helpdesk_timesheet.png
|
||||
.. image:: invoice_time/helpdesk_timesheet.png
|
||||
:align: center
|
||||
:alt: View of a helpdesk ticket emphasizing the timesheets tab in Odoo Helpdesk
|
||||
|
||||
Note that the hours recorded on the ticket form are shown on the *Delivered* column in the sales
|
||||
order.
|
||||
|
||||
.. image:: media/quotation_delivered.png
|
||||
.. image:: invoice_time/quotation_delivered.png
|
||||
:align: center
|
||||
:alt: View of a sales order emphasizing the delivered column in Odoo Sales
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 33 KiB After Width: | Height: | Size: 33 KiB |
|
Before Width: | Height: | Size: 59 KiB After Width: | Height: | Size: 59 KiB |
|
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 58 KiB |
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 58 KiB |
|
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 30 KiB |
|
Before Width: | Height: | Size: 51 KiB After Width: | Height: | Size: 51 KiB |
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
@@ -14,7 +14,7 @@ Configuration
|
||||
| Under *Timesheet on Ticket*, choose the *Project* to which tickets (and timesheets) will be
|
||||
linked by default. Open its *External link* to enable the feature *Bill from tasks*.
|
||||
|
||||
.. image:: media/reinvoice_time1.png
|
||||
.. image:: reinvoice_from_project/reinvoice_time1.png
|
||||
:align: center
|
||||
:alt: Bill from Tasks in Odoo Helpdesk
|
||||
|
||||
@@ -24,13 +24,13 @@ Create a sales order and an invoice
|
||||
Now, once you have recorded the time you spent on the helpdesk ticket, under the *Timesheets* tab,
|
||||
access the task clicking on its name.
|
||||
|
||||
.. image:: media/reinvoice_time2.png
|
||||
.. image:: reinvoice_from_project/reinvoice_time2.png
|
||||
:align: center
|
||||
:alt: Sales Order from a task in Odoo Helpdesk
|
||||
|
||||
*Create Sales Order* and proceed to create the invoice.
|
||||
|
||||
.. image:: media/reinvoice_time3.png
|
||||
.. image:: reinvoice_from_project/reinvoice_time3.png
|
||||
:align: center
|
||||
:height: 300
|
||||
:alt: Sales Order from a task in Odoo Helpdesk
|
||||
|
||||
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 9.0 KiB After Width: | Height: | Size: 9.0 KiB |
@@ -22,7 +22,7 @@ Configure the email alias in your project
|
||||
the wanted email alias and choose the policy to receive a message.
|
||||
| In addition, you can now directly set it when creating a new project.
|
||||
|
||||
.. image:: media/email_project.png
|
||||
.. image:: email_alias/email_project.png
|
||||
:align: center
|
||||
:alt: In the settings of your project, define the emails alias under the tab email in Odoo Project
|
||||
|
||||
@@ -31,7 +31,7 @@ Configure the email alias in your project
|
||||
|
||||
The email can be seen under the name of your project on the dashboard.
|
||||
|
||||
.. image:: media/email_dashboard_project.png
|
||||
.. image:: email_alias/email_dashboard_project.png
|
||||
:align: center
|
||||
:height: 300
|
||||
:alt: View of the email alias chosen on the dashboard view in Odoo Project
|
||||
|
||||
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
@@ -9,14 +9,14 @@ and questions after hours that have not been timesheeted by the employee.
|
||||
Activate the :ref:`developer mode <developer-mode>`, go to *Timesheets*, and change the *Project*
|
||||
and *Task* set by default, if you like.
|
||||
|
||||
.. image:: media/record_time_off.png
|
||||
.. image:: time_off/record_time_off.png
|
||||
:align: center
|
||||
:alt: View of Timesheets setting enabling the feature record time off in Odoo Timesheets
|
||||
|
||||
Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select or create the
|
||||
needed type, and decide if you would like the requests to be validated or not.
|
||||
|
||||
.. image:: media/time_off_types.png
|
||||
.. image:: time_off/time_off_types.png
|
||||
:align: center
|
||||
:alt: View of a time off types form emphasizing the time off requests and timesheets section in
|
||||
Odoo Time Off
|
||||
@@ -26,7 +26,7 @@ needed type, and decide if you would like the requests to be validated or not.
|
||||
respective project and task.
|
||||
| On the example below, the user requested *Paid Time off* from July 13th to 15th.
|
||||
|
||||
.. image:: media/time_off_request.png
|
||||
.. image:: time_off/time_off_request.png
|
||||
:align: center
|
||||
:alt: View of the time off request form in Odoo Time Off
|
||||
|
||||
@@ -34,13 +34,13 @@ Considering that validation is not required, the requested time off is automatic
|
||||
*Timesheets*. If validation is necessary, the time is automatically allocated after the responsible
|
||||
person for validating does it so.
|
||||
|
||||
.. image:: media/timesheets.png
|
||||
.. image:: time_off/timesheets.png
|
||||
:align: center
|
||||
:alt: Video of timesheets emphasizing the requested time off from the employee in Odoo Timesheets
|
||||
|
||||
Click on the magnifying glass, hovering over the concerned cell, to access all the aggregated data
|
||||
on that cell (day), and see details regarding the project/task.
|
||||
|
||||
.. image:: media/timesheet_description.png
|
||||
.. image:: time_off/timesheet_description.png
|
||||
:align: center
|
||||
:alt: View of the details of a project/task in Odoo Timeheets
|
||||
|
Before Width: | Height: | Size: 69 KiB After Width: | Height: | Size: 69 KiB |
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 75 KiB After Width: | Height: | Size: 75 KiB |
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 44 KiB |