msgid "This feature allows for field service tasks to be automatically created from a sales order. When you create a quotation with the :ref:`service product <sales/invoicing/configured-service-product>` and confirm it, a task is automatically created in your Field Service project. Click the :guilabel:`Tasks` smart button to access it from the sales order."
msgid "By default, **Odoo Field Service** shows a static map where all task locations for the day are pinned. To make it more useful for the field service workers, it is possible to display an itinerary on the map using MapBox. To do so, enable the **Map Routes** feature as follows:"
msgid "In Odoo, go to the :guilabel:`Settings` app and scroll down to the :guilabel:`Integrations` section. Paste your Mapbox access token in the :guilabel:`Token` field under :guilabel:`Map Routes`, and click :guilabel:`Save`."
msgid "To display your tasks on a map, go to :menuselection:`Field Service --> My Tasks --> Map`. To create your itinerary, Odoo sorts out your field service tasks based on their :guilabel:`Planned Date` to show the way from one location to the next."
msgid "To open your itinerary on the Google Maps website or app, click :guilabel:`View in Google Maps`. Google Maps includes your current location as a starting point for your itinerary."
msgid "By default, the map shows today’s tasks. Remove the :guilabel:`Today` filter in the search bar to display all tasks. Your tasks are then sorted by date in the left column."
msgid "Click your task in the left column or the map pin to display the task's details. From there, you can :guilabel:`Open` the task or click :guilabel:`Navigate to` to get an itinerary from your current location to this specific task's location."
msgid "When field service workers perform tasks on-site, they commonly use products to complete their work. Odoo Field Service allows them to record these products using the **product catalog** and **default warehouse** features. Doing so keeps your inventory up-to-date in real-time and automatically adds the products to the invoice."
msgid "To activate the product catalog for Field Service, go to :menuselection:`Field Service --> Configuration --> Settings` and enable the :guilabel:`Time and Material Invoicing` feature."
msgid "Going back to your task, the smart button now displays the amount of products you added and the price. You can return to the product catalog at any time to edit the product selection."
msgid "Setting up a **default warehouse** can be useful for field technicians who keep a supply on the go in their van or those who always resupply from the same warehouse. It also allows field workers to switch between warehouses from their profiles."
msgid "To set up a user default warehouse, the :doc:`storage locations <../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations>` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database."
msgid "To set up a default warehouse for yourself, click your **profile icon** in the upper right corner of the screen, then, go to :menuselection:`My Profile --> Preferences --> Default Warehouse`. Select the default warehouse from the drop-down menu."
msgid "To set up a default warehouse for a specific user, go to :menuselection:`Settings --> Users --> Manage users`, select a user, then go to the :guilabel:`Preferences` tab. Scroll down to :guilabel:`Inventory`, and select the default warehouse from the drop-down menu."
msgid "Once a default warehouse has been configured for a user, the materials used for a sales order related to a Field Service task are pulled from that specific warehouse. Open the related sales order, go to the :guilabel:`Other Info` tab, then scroll down to :guilabel:`Delivery`. The default warehouse is applied correctly."
msgid "**Worksheets** help your field service workers perform and report their on-site tasks. They can feature various information, such as instructions, to-do lists, etc. You can also format your worksheet using checkboxes, bullet points, blank fields to fill in, HTML, and add files, images, links, and more."
msgid "It is common for businesses to have their workers perform the same type of field service repeatedly. Making custom **worksheet templates** eliminates the need to recreate the same worksheet each time you plan a similar field service task."
msgid "To use worksheets in Field Service, go to :menuselection:`Field Service --> Configuration --> Settings`, enable the :guilabel:`Worksheets` feature, and click :guilabel:`Save`."
msgid "Worksheet templates are designed using **Studio**. Enabling the :guilabel:`Worksheets` feature automatically installs the **Studio** app, which may impact your price plan."
msgid "To create your **worksheet templates**, go to :menuselection:`Field Service --> Configuration --> Worksheet Templates`. Click :guilabel:`New` and give your worksheet template a name. Manually save, then click :guilabel:`Design Template` to open **Studio** and customize your worksheet template."
msgid "In Studio, drag and drop the desired fields from the left column into your worksheet on the right. To rearrange the fields on the worksheet, drag and drop them in the desired order. Click a field to customize its :ref:`properties <studio/fields/properties>`."
msgid "By default, the :guilabel:`Default Worksheet` template is selected. To define another default worksheet template, click the :guilabel:`➔` (:guilabel:`Internal link`) icon that appears when you hover your mouse over the :guilabel:`Project` field on the task form."
msgid "Then, in the :guilabel:`Settings` tab, scroll down to the :guilabel:`Field service` section and select the :guilabel:`Worksheet Template` you want to set up as default."
msgid "As soon as you save a worksheet, the label of the :guilabel:`Worksheet` smart button on the task changes to :guilabel:`Worksheet Complete` instead, even if some fields are left blank."
msgid "Odoo **Helpdesk** is a ticket-based customer support application. Multiple teams can be configured and managed in one dashboard, each with their own pipeline for tickets submitted by customers. Pipelines are organized in customizable stages that enable teams to track, prioritize, and solve customer issues quickly and efficiently."
msgid "To view or modify **Helpdesk** teams, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. To create a new team, click the :guilabel:`New` button on the top-left of the dashboard."
msgid "On the blank Helpdesk team form, enter a :guilabel:`Name` for the new team. Then, enter a description of the team in the field below the team name, if desired. To change the company this team is assigned to, select it from the :guilabel:`Company` drop-down menu."
msgid "The team description is published on the public facing :doc:`website form <helpdesk/overview/receiving_tickets>`, where customers and portal users submit tickets. The description included in this field should **not** include any information that is for internal use only."
msgid "The *Visibility* settings alter which internal users and portal users have access to this team and its tickets. The *Assignment* settings alter how users are assigned to handle each ticket."
msgid ":guilabel:`Invited internal users (private)`: Internal users can access the team and the tickets they are following. This access can be modified on each ticket individually by adding or removing the user as a follower. Internal users are considered *invited* once they are added as followers to an individual ticket, or :ref:`to the team itself <helpdesk/follow>`."
msgid ":guilabel:`Invited portal users and all internal users (public)`: All internal users can access the team and all of its tickets. Portal users can only access the tickets they are following."
msgid "A `Customer Support` team, meant to handle general shipping and product issues, would have the visibility set on :guilabel:`Invited portal users and all internal users`."
msgid "At the same time, a `Financial Services` team handling tickets related to accounting or tax information would only need to be visible to :guilabel:`Invited internal users`."
msgid "A team's visibility can be altered after the initial configuration. However, if the team changes from *Invited portal users and all internal users (public)* access to either *Invited internal users (private)* or *All internal users (company)*-only access, portal users are removed as followers from both the team, and from individual tickets."
msgid "If a user should be notified about any updates regarding tickets for this team, select their name from the :guilabel:`Followers` drop-down menu, located in the :guilabel:`Follow All Team's Tickets` field. Multiple users can be selected to follow a single team."
msgid "External contacts can be selected in the :guilabel:`Followers` field. If the team's visibility is set to :guilabel:`Invited internal users (private)`, followers are notified about updates to the team's tickets, but are **not** able to view them in the portal."
msgid "When tickets are received, they need to be assigned to a member of the team. This is done either manually on each individual ticket, or through :guilabel:`Automatic Assignment`. Check the :guilabel:`Automatic Assignment` checkbox to enable this feature for the team."
msgid ":guilabel:`Each user is assigned an equal number of tickets`: Tickets are assigned to team members based on total ticket count, regardless of the number of open or closed tickets they are currently assigned."
msgid ":guilabel:`Each user has an equal number of open tickets`: Tickets are assigned to team members based on how many open tickets they are currently assigned."
msgid "When :guilabel:`Each user is assigned an equal number of tickets` is selected, the overall number of tickets assigned to team members is the same, but it does **not** consider the current workload."
msgid "When :guilabel:`Each user has an equal number of open tickets` is selected, it ensures a balanced workload among team members, as it takes the current number of active tickets into account."
msgid "Finally, add the :guilabel:`Team Members` who are to be assigned tickets for this team. Leave the field empty to include all employees who have the proper assignments and access rights configured in their user account settings."
msgid "If an employee has time off scheduled in the **Time Off** application, they are **not** assigned tickets during that time. If no employees are available, the system looks ahead until there is a match."
msgid "The *merge* feature is **only** accessible if the :doc:`Data Cleaning <../productivity/data_cleaning>` application is installed on the database."
msgid "To merge two or more tickets, navigate to :menuselection:`Helpdesk app --> Tickets --> All Tickets`. Identify the tickets to be merged, and tick the checkbox at the far-left of each ticket to select them. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, and select :guilabel:`Merge` from the drop-down menu. Doing so opens a new page where the selected tickets are listed with their :guilabel:`Similarity` rating. From here, click either :ref:`Merge <data_cleaning/merge-records>` to combine the tickets, or :guilabel:`DISCARD`."
msgid "Some tickets may be better handled by the sales team, rather than the support team. In this case, tickets can be converted to *opportunities* and assigned to a sales team for follow-up."
msgid "To convert a ticket to an opportunity, first navigate to a ticket, either from a team's pipeline, or by navigating to :menuselection:`Helpdesk app --> Tickets` and clicking a ticket to open it."
msgid "If :doc:`leads <../sales/crm/acquire_leads/convert>` are enabled on the **CRM** app, tickets are converted to *leads*, and the button reads :guilabel:`Convert to Lead`."
msgid ":guilabel:`Customer`: Select whether to :guilabel:`Create a new customer`, :guilabel:`Link to an existing customer`, or :guilabel:`Do not link to a customer`. If :guilabel:`Link to a customer` is chosen, select the appropriate customer name from the :guilabel:`Customer` drop-down."
msgid "After completing the form, click :guilabel:`Convert to Opportunity`. Doing so creates a new opportunity in the **CRM** app. The original ticket is linked in the chatter of the new opportunity for traceability."
msgid "*After-Sales* services can be configured in the *Helpdesk* application for individual teams. Once enabled, users can :ref:`issue refunds <helpdesk/refunds>`, :ref:`generate coupons <helpdesk/coupons>`, :ref:`process returns <helpdesk/returns>`, and :ref:`schedule repairs <helpdesk/repairs>` or :ref:`field service interventions <helpdesk/field>` directly from a ticket."
msgid "Start by enabling the after-sales services on a specific *Helpdesk* team, by going to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and click on the team the services should be applied to. Then, scroll to the :guilabel:`After-Sales` section on the team's settings page, and choose which of the following options to enable:"
msgid "Since all the after-sales services in Odoo require integration with other applications, enabling any of them may result in the installation of additional modules or applications. Installing a new application on a One-App-Free database triggers a 15-day trial. At the end of the trial, if a paid subscription has not been added to the database, it will no longer be accessible."
msgid "A *credit note* is a document issued to a customer informing them that they have been credited a certain amount of money. They can be used to provide a full refund to a customer, or to adjust any remaining amount due. While they are usually created through the *Accounting* or *Invoicing* applications, they can be created through a *Helpdesk* ticket, as well."
msgid "To create a credit note, navigate to a ticket on the :menuselection:`Helpdesk app`, and click the :guilabel:`Refund` button in the top-left corner of the ticket form. This opens a :guilabel:`Refund` pop-up window."
msgid ":guilabel:`Product`: the product the ticket is about. If an item is selected in this field, only the sales orders, deliveries, and invoices including this product can be selected."
msgid ":guilabel:`Invoices to Refund`: this field is **required**. If no invoices are available in the drop-down, it indicates this customer currently has no posted invoices, or the :guilabel:`Product` has no related invoices."
msgid ":guilabel:`Reason displayed on Credit Note`: this field automatically populates with the ticket number, though it can be edited with additional information."
msgid ":guilabel:`Journal`: the accounting journal where the credit note should be posted. After an invoice is selected, this field defaults to the journal listed on the original invoice, though it can be changed, if necessary."
msgid ":guilabel:`Reversal date`: when this field is clicked, use the pop-up calendar that appears to select a date for the credit note invoice. This field is **required**."
msgid ":guilabel:`Reverse` creates a credit note in a draft state that can be edited before it is posted. This option can be used to provide a partial refund."
msgid ":guilabel:`Reverse and Create Invoice` creates a credit note that is automatically posted as well as an invoice in a draft state. The invoice contains the same information as the original invoice, though this information can be altered."
msgid "Coupons can be used to alter the price of products or orders. Conditional rules define the usage constraints of a coupon. *Coupon Programs* are configured in the *Sales*, *Point of Sale*, or *Website* applications."
msgid "To generate a coupon, open a *Helpdesk* ticket and click on the :guilabel:`Coupon` button in the top-left corner. Select an option from the :guilabel:`Coupon Program` drop-down menu in the :guilabel:`Generate a Coupon` pop-up window that appears."
msgid "To create a new :guilabel:`Coupon Program`, navigate to :menuselection:`Sales app --> Products --> Discount & Loyalty` and click :guilabel:`New`. To make the program available to share with *Helpdesk* customers, the :guilabel:`Program Type` **must** be set to :guilabel:`Coupons`. This generates single-use coupon codes that grant immediate access to rewards and discounts."
msgid "Coupon programs can also be created in the *Point of Sale* application or *Website* application. Refer to :doc:`discount and loyalty programs <../../../sales/sales/products_prices/loyalty_discount>` for more information."
msgid "Click on the :guilabel:`Valid Until` field, and use the pop-up calendar to select an expiration date for this coupon code. If this field is left blank, the code does **not** expire."
msgid "When emailing a coupon code, **all** the followers of the ticket are added as recipients to the email. Additional recipients can be added to the email as well, in the :guilabel:`Recipients` field of the :guilabel:`Compose Email` pop-up window. If an expiration date was selected for the code, it is included in the message template."
msgid "Click :guilabel:`Get Share Link` to generate a link to send directly to the customer. Doing so opens a :guilabel:`Share Coupons` pop-up window. Click the :guilabel:`Copy` button next to the :guilabel:`Share Link` field and paste the results to any communication with the customer. When the customer uses the link, the code is automatically applied to their cart."
msgid "After a :guilabel:`Coupon Code` has been generated, a :guilabel:`Coupons` smart button is added to the top of the ticket; click the smart button to view the coupon code, expiration date, and additional information."
msgid "Returns are completed through *reverse transfers*, which generate new warehouse operations for the returning products. Click the :guilabel:`Return` button in the top-left corner of a ticket to open the :guilabel:`Reverse Transfer` pop-up window."
msgid "By default, the quantity matches the validated quantity from the delivery order. Update the :guilabel:`Quantity` field, if necessary. To remove a line, click the :guilabel:`🗑️ (trash can)` icon."
msgid "If the ticket is related to an issue with a faulty or broken product, a *repair order* can be created from the *Helpdesk* ticket, and managed through the *Repairs* application."
msgid "To create a new repair order, open a :menuselection:`Helpdesk` ticket and click on the :guilabel:`Repair` button in the top-left corner. This opens a :guilabel:`Repair Reference` form."
msgid ":guilabel:`Product to Repair`: if a product was specified in the :guilabel:`Product` field on the ticket, it is added to this field automatically. If not, click into the field to select a product from the drop-down menu."
msgid ":guilabel:`Scheduled Date`: this field defaults to the current date. To select a new date, click into the field and select a date using the drop-down calendar."
msgid "If parts are required for the repair, they can be added in the :guilabel:`Parts` tab. Additional information for the internal repair team can be added to the :guilabel:`Repair Notes` tab."
msgid "Once the form is complete, click :guilabel:`Confirm Repair`. To create, edit, and send a quote for this repair, click :guilabel:`Create Quotation`."
msgid "Once a user creates a repair order from a *Helpdesk* ticket, they can access it through the ticket's :guilabel:`Repair` smart button, or from a link in the chatter, even if they do not have access rights to the *Repair* application."
msgid "On-site interventions can be planned from a ticket and managed through the *Field Service* application. Customers with :doc:`portal access <../../../general/users/portal>` are able to track the progress of a *Field Service* task just as they would a *Helpdesk* ticket."
msgid "To change the default *Field Service* project for the team, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` to select a :guilabel:`Team`. Scroll to the :guilabel:`After-Sales` section, and choose a project under :guilabel:`Field Service`."
msgid "To create a new *Field Service* task, navigate to a :menuselection:`Helpdesk` ticket. Click :guilabel:`Plan Intervention` to open the :guilabel:`Create a Field Service task` pop-up window."
msgid "The :guilabel:`Project` field on the :guilabel:`Create a Field Service task` pop-up window defaults to the same *Field Service* project that was identified on the team's settings page. To change the project for this specific task, select one from the :guilabel:`Project` field."
msgid "*Field Service Worksheets* are reports that detail the work completed during an on-site task. When work is completed, worksheets are signed by the customer to confirm the job is done and the customer is satisfied."
msgid "If the *Field Service* project assigned to the *Helpdesk* team has worksheets enabled, and has a default template assigned, that template automatically appears in the :guilabel:`Worksheet Template` drop-down field. Even so, the field can be edited, and another template can be selected."
msgid "If the *Field Service* project does **not** have worksheets enabled, the :guilabel:`Worksheet Template` field does not appear on the :guilabel:`Create a Field Service task` pop-up window."
msgid "Once work has been completed on a *Helpdesk* ticket in Odoo, there are several ways it can be closed. Manually closing solved tickets keeps the pipeline up to date, while automatically closing inactive tickets prevents unnecessary blocking issues. Allowing customers to close their own tickets minimizes confusion around whether an issue is considered solved or not. This results in increased operational capacity for support teams, and higher customer satisfaction."
msgid "As work on a ticket progresses, it is moved along to the next stage in the pipeline. Once the issue is solved, the ticket is moved to a *folded* stage. This marks the ticket as *closed*."
msgid "To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and click on a team to open the pipeline. Hover over a stage's heading, and then click the gear icon that appears in the top-right corner of that stage's kanban column."
msgid "Clicking the gear icon also displays the option to :guilabel:`Fold` the stage. This setting folds the stage *temporarily* to simplify the kanban view. This does *not* close the tickets in this stage. It also does not permanently fold the stage. If a stage needs to be folded so the tickets can be marked as closed, continue following the steps below."
msgid "From the menu that appears, select :guilabel:`Edit Stage`. This will open the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` towards the top of the window, and then :guilabel:`Save & Close` to confirm the changes. Now, tickets that reach this stage will be considered as *closed*."
msgid "Go to the team's settings page by going to :menuselection:`Helpdesk --> Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable :guilabel:`Automatic Closing`."
msgid "If one of the team's stages is set to be folded in the kanban view, it will be the default selection in the :guilabel:`Move to Stage` field. If the team has more than one folded stage, the stage that occurs first in the pipeline will be the default. If no stage is folded, the default selection will be the last stage in the pipeline."
msgid "The :guilabel:`After days of inactivity` field does **not** take the working calendar into account when tracking the amount of time a ticket has been inactive."
msgid "Tickets can linger in the :guilabel:`Customer Feedback stage`, because once an issue is solved, customers may not respond immediately. At that point, the tickets can be closed automatically. However, tickets in the :guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due to assignment or workload issues. Closing these tickets automatically would result in issues going unsolved."
msgid "Enabling the :guilabel:`Closure by Customers` setting allows customers to close their own ticket(s) when they determine that their issue has been resolved."
msgid "Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams` and select a team. On the team's settings page, scroll to the :guilabel:`Self-Service` section and check the box for :guilabel:`Closure by Customers`."
msgid "Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` button will be available for customers when they view their ticket through the customer portal."
msgid "Customers are able to view their tickets by clicking the :guilabel:`View the ticket` link they receive by email. The link is included in the :guilabel:`Request Acknowledgment` template, which is added to the first stage of a team by default. This link does not require a customer to have access to the portal to view or respond to their ticket."
msgid "Odoo *Helpdesk* provides teams with the ability to track the amount of hours spent working on a ticket, and to bill a customer for that time. Through integrations with the *Sales*, *Timesheets*, *Project* and *Accounting* applications, customers can be charged once the work is completed, or before it has even begun."
msgid "Since the *Track & Bill Time* features require integration with other applications, enabling them may result in the installation of additional modules or applications."
msgid "Installing a new application on a *One-App-Free* database triggers a 15-day trial. At the end of the trial, if a paid subscription has not been added to the database, it will no longer be active or accessible."
msgid "Before a customer can be invoiced for support services, the *Track & Bill Time* features **must** be enabled on each *Helpdesk* team individually."
msgid "To view and enable the *Track & Bill Time* features on a *Helpdesk* team, first navigate to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. Then, select a team from the list, or create a :doc:`new one <../../helpdesk>`. This reveals a team's settings page."
msgid "On the team's settings page, scroll to the :guilabel:`Track & Bill Time` section. Check the boxes labeled :guilabel:`Timesheets` and :guilabel:`Time Billing`."
msgid "If this is the first time this feature has been enabled on this database, the page may need to be manually saved and refreshed before the :guilabel:`Project` field appears."
msgid "The project selected in this field represents where all the timesheets for this team's tickets are recorded. Click into the :guilabel:`Project` drop-down menu to select a project."
msgid "To create a new project where the timesheets are recorded, click into the :guilabel:`Project` drop-down menu, type a name for the project, and then click :guilabel:`Create` from the drop-down menu beneath."
msgid "When the :guilabel:`Time Billing` feature is enabled, a new product is created in the *Sales* app called *Service on Timesheets*. This product can be found under :menuselection:`Sales app--> Products --> Products`. Then, search for `Service on Timesheets` in the :guilabel:`Search...` bar. This is the product that is used when invoicing for *post-paid support services* **after** they have been completed."
msgid "Select :guilabel:`Service on Timesheets` from the product page. This reveals the product detail form. The product is configured with the :guilabel:`Product Type` set to :guilabel:`Service` and the :guilabel:`Invoicing Policy` set to :guilabel:`Based on Timesheets`. Make any necessary changes to the product record, such as the :guilabel:`Cost` or :guilabel:`Sales Price`."
msgid "In order to invoice for support services **before** the work has been completed (also known as *prepaid support services*), a separate product with a different invoicing policy must be created."
msgid "To create a new service product, go to :menuselection:`Sales app --> Products --> Products`, and click :guilabel:`New`. This reveals a blank product detail form."
msgid "On the new product form, add a :guilabel:`Product Name`, and set the :guilabel:`Product Type` to :guilabel:`Service`. Then, set the :guilabel:`Invoicing Policy` to :guilabel:`Prepaid/Fixed Price`. This means an invoice can be generated and payment can be received for this product before any timesheets entries have been recorded for these services."
msgid "When support services are billed on a fixed price, an invoice can be created before any work is completed on the issue. In this case, a service product with the *Invoicing Policy* set to *Prepaid/Fixed Price* would be used, just like :ref:`the section above <helpdesk/configure-service-products>`."
msgid "To invoice a customer for prepaid support services, first create a sales order (SO) with the support services product. To do this, go to :menuselection:`Sales app --> Orders --> Quotations`. Then, click :guilabel:`New` to reveal a blank quotation form."
msgid "Go to the :guilabel:`Order Lines` tab of the quotation and click :guilabel:`Add a Product`. Then, select the *prepaid services product* configured in the steps above. Update the :guilabel:`Quantity` field with the number of hours."
msgid "After updating any other necessary information, :guilabel:`Confirm` the quotation. This converts the quotation into an :abbr:`SO (sales order)`."
msgid "Once the :abbr:`SO (sales order)` has been confirmed, click the :guilabel:`Create Invoice` button. This opens a :guilabel:`Create invoices` pop-up window."
msgid "If no down payment is collected, the :guilabel:`Create Invoice` type can remain as :guilabel:`Regular Invoice`. If a :doc:`down payment <../../../sales/sales/invoicing/down_payment>` is collected, choose between either :guilabel:`Down payment (percentage)` or :guilabel:`Down payment (fixed amount)`."
msgid "To create a *Helpdesk* ticket for prepaid services, navigate to :menuselection:`Helpdesk` and click the :guilabel:`Tickets` button to reveal a specific team's pipeline. Click :guilabel:`New` to create a new ticket."
msgid "When the customer name is added, the :guilabel:`Sales Order Item` field automatically populates with the most recent prepaid sales order item that has time remaining."
msgid "On the ticket detail form, click on the :guilabel:`Timesheets` tab and click :guilabel:`Add a line`. Choose an :guilabel:`Employee`, add a :guilabel:`Description` of the task, and enter the number of :guilabel:`Hours Spent`."
msgid "As new lines are added to :guilabel:`Timesheets` tab, the :guilabel:`Remaining Hours on SO` field, at the bottom-right of the tab, is automatically updated."
msgid "As hours are added to the :guilabel:`Timesheets` tab, they are automatically updated in the :guilabel:`Delivered` field on the :abbr:`SO (sales order)`, as well."
msgid "When support services are billed based on the amount of time spent on an issue, an invoice cannot be created before the total number of hours required to solve the problem have been entered on a timesheet. In this case, a service product with the *Invoicing Policy* set to *Based on Timesheets* would be used, like the one created in :ref:`the section above <helpdesk/configure-service-products>`."
msgid "To invoice a customer for post-paid support services, first create a sales order (SO) with the *support services product*. To do this, go to :menuselection:`Sales app --> Orders --> Quotations`. Then, click :guilabel:`New` to reveal a blank quotation form."
msgid "On the :guilabel:`Order Lines` tab, click :guilabel:`Add a Product`. Select the post-paid services product configured in the steps above. After updating any other necessary information, :guilabel:`Confirm` the quotation."
msgid "Unlike with the prepaid services quotation, Odoo does **not** allow an invoice to be created at this time. That is because no services have been performed; in other words, nothing has been delivered, therefore, there is nothing to invoice."
msgid "To record a *Timesheet* entry for time-tracker services, go to the :menuselection:`Helpdesk` app, and select the appropriate team for which these services apply."
msgid "If there is already an existing ticket for this issue, select it from the Kanban view. This opens the ticket details form. If there is no existing ticket for this customer issue, click :guilabel:`New` to create a new ticket and enter the necessary customer information on the blank ticket details form."
msgid "After selecting or creating a ticket, go to the :guilabel:`Sales Order Item` drop-down menu. Select the :abbr:`SO (sales order)` created in the previous step."
msgid "In order to create an invoice for a product based on timesheets, hours need to be tracked and recorded. At this point, the service is considered *delivered*. To record hours for this support service, click on the :guilabel:`Timesheets` tab of the ticket."
msgid "Click :guilabel:`Add a Line` to record a new entry. Select an :guilabel:`Employee` from the drop-down menu, and record the time spent in the :guilabel:`Hours Spent` column."
msgid "After the customer's issue has been solved, and it is determined no new timesheet entries need to be made, an invoice can be created, and the customer can be billed."
msgid "Before creating the invoice, confirm that the number in the :guilabel:`Delivered` column matches the total number of :guilabel:`Hours Spent` listed in the :guilabel:`Timesheets` tab on the ticket."
msgid "If no down payment is collected, the :guilabel:`Create Invoice` type can remain as :guilabel:`Regular Invoice`. If a down payment is collected, choose between either :guilabel:`Down payment (percentage)` or :guilabel:`Down payment (fixed amount)`."
msgid "Use the :guilabel:`Timesheets Period` field if this invoice should **only** include timesheets from a certain time period. If this field is left blank, **all** applicable timesheets that have not yet been invoiced will be included."
msgid "When the necessary information has been entered, click :guilabel:`Create Draft`. The invoice can then be reviewed, edited, and sent to the customer for payment."
msgid "Odoo **Helpdesk** integrates with the **Forums**, **eLearning**, and **Knowledge** apps to create the *Help Center*. The *Help Center* is a centralized location where teams and customers can search for and share detailed information about products and services."
msgid "To activate any of the *Help Center* features on a *Helpdesk* team, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one <../../helpdesk>`. Verify the :guilabel:`Visibility` of the team is set to :guilabel:`Invited portal users and all internal users (public)` in the :guilabel:`Visibility & Assignment` section."
msgid "Additionally, the :guilabel:`Website Form` option on the **Helpdesk** team form **must** be enabled to activate any of the *Help Center* features. When one or more of the *Help Center* features is enabled, the :guilabel:`Website Form` is automatically enabled, as well."
msgid "Since all of the *Help Center* features require integration with other applications, enabling any of them may result in the installation of additional modules or applications."
msgid "Installing a new application on a *One-App-Free* database will trigger a 15-day trial. At the end of the trial, if a `paid subscription <https://www.odoo.com/pricing>`_ has **not** been added to the database, it will no longer be active or accessible."
msgid "Odoo's **Knowledge** application is a collaborative library, where users can store, edit, and share information. The **Knowledge** app can be used to publish user guides and :abbr:`FAQs (Frequently Asked Questions)` with customers externally, while also collaborating internally on shared documents."
msgid "To enable the **Knowledge** feature on a *Helpdesk* team, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one <../../helpdesk>`."
msgid "On the team's detail form, scroll down to the :guilabel:`Help Center` section. Then, click the box next to :guilabel:`Knowledge` to activate the **Knowledge** feature. When clicked, a new field labeled, :guilabel:`Article` appears."
msgid "Clicking the :guilabel:`Article` field reveals a drop-down menu. At first, there is only one option in the drop-down menu titled :guilabel:`Help`, which Odoo provides by default. Select :guilabel:`Help` from the drop-down menu to choose this article."
msgid "To create a new article, go to the :menuselection:`Knowledge app`, then hover the cursor next to the :guilabel:`Workspace` section heading, located in the left sidebar. Moving the cursor there reveals a hidden |plus|."
msgid "Click the |plus| to create a new article in the :guilabel:`Workspace`. Click the :icon:`fa-share-alt` :guilabel:`Share` icon, and slide the :guilabel:`Share to Web` toggle switch until it reads :guilabel:`Article Published`. It can then be added to a **Helpdesk** team."
msgid "When members of a **Helpdesk** team are trying to solve a ticket, they can search through the content in the **Knowledge** app for more information on the issue."
msgid "To search **Knowledge** articles, open a ticket — either from the **Helpdesk** app dashboard, or by going to :menuselection:`Helpdesk app --> Tickets --> All Tickets`, then select a ticket from the list."
msgid "**Knowledge** articles can also be searched by pressing :command:`Ctrl + K` to open the command palette, then typing :kbd:`?`, followed by the name of the desired article."
msgid "When Odoo reveals the desired article, click it, or highlight the :guilabel:`Article` title, and press :command:`Enter`. This will open the article in the :guilabel:`Knowledge` application."
msgid "Even though the *Help* article has been enabled on a team, Odoo does **not** share all the nested articles to the web. Individual articles intended for customers **must** be published for them to be viewable on the website."
msgid "To publish an article, navigate to the desired article, by following the above steps, and click the :icon:`fa-share-alt` :guilabel:`Share` icon. This reveals a menu. Slide the toggle button labeled :guilabel:`Share to Web` to read :guilabel:`Article Published`."
msgid "*Clipboard* boxes can be added to **Knowledge** articles to allow content to be reused, copied, sent as messages, or added to the description on a ticket. This allows teams to maintain consistency when answering customer tickets, and minimize the amount of time spent on responding to repeat questions."
msgid "To create a clipboard box, go to :menuselection:`Knowledge app --> Help`. Click on an existing nested article or create a new one by clicking the |plus| next to *Help*."
msgid "Type :kbd:`/` to open the *powerbox*, and view a drop-down list of :doc:`commands <../../../productivity/knowledge/articles_editing>`. Select or type :kbd:`clipboard`. A gray block is then added to the page. Add any necessary content to this block."
msgid "Clipboard boxes only display the :guilabel:`Use as description` or :guilabel:`Send as Message` options if they are accessed directly from the **Helpdesk**."
msgid "To use clipboard boxes in a **Helpdesk** ticket, first, open a ticket, either from the :guilabel:`Helpdesk` dashboard or by going to :menuselection:`Helpdesk app --> Tickets --> All Tickets` and selecting a ticket from the list."
msgid "Click on the :guilabel:`Knowledge (bookmark)` icon in the top-right corner. This opens a search window. In this search window, select, or search, for the desired article. Doing so reveals that article page in the Odoo **Knowledge** application."
msgid "To use a clipboard box to respond to a ticket, click :guilabel:`Send as message` in the upper-right corner of the clipboard box, located in the body of the article."
msgid "Doing so opens a :guilabel:`Compose Email` pop-up window. In this window, select the recipients, make any necessary additions or edits to the clipboard content, then click :guilabel:`Send`."
msgid "To use a clipboard box to add information to a ticket's description, click :guilabel:`Use as description` in the upper-right corner of the clipboard box, located in the body of the article. Doing so does **not** replace the existing text in a ticket's description. The content from the clipboard box is added as additional text."
msgid "A *Community Forum* provides a space for customers to answer each other's questions and share information. By integrating a forum with a **Helpdesk** team, tickets submitted by customers can be converted to posts and shared."
msgid "To enable :guilabel:`Community Forums` on a **Helpdesk** team, start by navigating to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one <../../helpdesk>`."
msgid "Selecting or creating a team reveals that team's detail form. Scroll down to the :guilabel:`Help Center` section of features, and enable :guilabel:`Community Forum`, by checking the box beside it."
msgid "Click the empty :guilabel:`Forums` field to reveal a drop-down menu. By default, there is only one option to begin with, labeled :guilabel:`Help`. That is the option Odoo automatically created when the :guilabel:`Community Forums` feature was enabled. Select :guilabel:`Help` from the drop-down menu to enable that forum."
msgid "To create a new forum, type a name into the blank :guilabel:`Forums` field, then click the :guilabel:`Create and Edit` option. Multiple forums can be selected in this field."
msgid "To do that, select a ticket, either from a team's pipeline or from :menuselection:`Tickets --> All Tickets` in the :guilabel:`Helpdesk` application."
msgid "When clicked, a pop-up window appears. Here, the :guilabel:`Forum` post and :guilabel:`Title` can be edited to correct any typos, or modified to remove any proprietary or client information."
msgid ":guilabel:`Tags` can also be added to help organize the post in the forum, making it easier for users to locate during a search. When all adjustments have been made, click :guilabel:`Create and View Post`."
msgid "To create a ticket, navigate to a forum post, and click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon. Then, click :guilabel:`Create Ticket`."
msgid "This opens a :guilabel:`Create Ticket` pop-up. Make any necessary edits to the :guilabel:`Create Ticket` field. Then, confirm the :guilabel:`Helpdesk Team` the ticket should be assigned to."
msgid "Odoo **eLearning** courses offer customers additional training and content in the form of videos, presentations, and certifications/quizzes. Providing additional training enables customers to work through issues and find solutions on their own. They can also develop a deeper understanding of the services and products they are using."
msgid "To enable **eLearning** courses on a **Helpdesk** team, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one <../../helpdesk>`."
msgid "On the team's settings page, scroll to the :guilabel:`Help Center` section, and check the box next to :guilabel:`eLearning`. A new field appears below, labeled :guilabel:`Courses`."
msgid "Click the empty field next to :guilabel:`Courses` beneath the :guilabel:`eLearning` feature to reveal a drop-down menu. Select an available course from the drop-down menu, or type a title into the field, and click :guilabel:`Create and edit` to create a new course from this page. Multiple courses can be assigned to a single team."
msgid "A new **eLearning** course can be created from the :guilabel:`Helpdesk` team's settings page, as in the step above, or from the **eLearning** app."
msgid "To create a course directly through the **eLearning** application, navigate to :menuselection:`eLearning --> New`. This reveals a blank course template that can be customized and modified as needed."
msgid "The :guilabel:`Show Course To` field defines who can access the courses. The :guilabel:`Enroll Policy` field specifies how they can register for the course."
msgid "To add content to a course, click the :guilabel:`Content` tab and select :guilabel:`Add Content`. Choose the :guilabel:`Content Type` from the drop-down menu and upload the file, or paste the link, where instructed. Click :guilabel:`Save` when finished. Click :guilabel:`Add Section` to organize the course in sections."
msgid "In order to add a certification to a course, go to :menuselection:`eLearning --> Configuration --> Settings`, check the box labeled :guilabel:`Certifications`, and :guilabel:`Save` to activate the setting."
msgid "If the course is published, but the contents of the course are **not** published, customers can enroll in the course on the website, but they are **not** able to view any of the course content. Knowing this, it may be beneficial to publish the course first, if the course contents are intended to be released over time, such as classes with a weekly schedule."
msgid "To publish a course, choose a course from the **eLearning** dashboard. On the course template page, click the :guilabel:`Go to Website` smart button."
msgid "This will reveal the front end of the course's web page. At the top of the course web page, move the :guilabel:`Unpublished` toggle switch to :guilabel:`Published`."
msgid "To publish **eLearning** course content from the back-end, choose a course from the **eLearning** dashboard. On the course template page, click the :guilabel:`Published Contents` smart button."
msgid "Doing so reveals a separate page displaying all the published content related to that course. Remove the default :guilabel:`Published` filter from the search bar in the upper-right corner, to reveal all the content related to the course - even the non-published content."
msgid "While in list view, there is a checkbox on the far-left of the screen, above the listed courses, to the left of the :guilabel:`Title` column title. When that checkbox is clicked, all the course contents are selected at once."
msgid "With all the course content selected, click any of the boxes in the :guilabel:`Is Published` column. This reveals a pop-up window, asking for confirmation that all selected records are intended to be published. Click :guilabel:`Confirm` to automatically publish all course content."
msgid "Asking customers to rate the support they received from a *Helpdesk* team provides an opportunity to gauge team performance and track customer satisfaction. Ratings can be published on the portal, providing customers with a general overview of the team's performance."
msgid "To enable *customer ratings* on a helpdesk team, navigate to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. Select a team from the list and click on it to open the settings page. Scroll to the :guilabel:`Performance` section, and tick the :guilabel:`Customer Ratings` checkbox."
msgid "After the :guilabel:`Customer Ratings` :ref:`setting has been enabled <helpdesk/enable-ratings>` on the team's settings page, click the :guilabel:`Set an Email Template on Stages` link. Select a stage from the list, or click :guilabel:`New` to create a new stage."
msgid "Customers should only be asked to rate tickets once an issue has been resolved and their ticket is *closed*. Therefore, a *ratings request* email should **only** be added to a stage that is folded in the Kanban, as tickets in a *folded stage* are considered closed."
msgid "On the stage's settings page, select the template, `Helpdesk: Ticket Rating Request` in the :guilabel:`Email Template` field. This template has been preconfigured with ratings customers can use to provide feedback. To view the template, click the arrow button to the right of the field."
msgid "After the template is added to the stage, it automatically sends a message when a ticket is moved to that stage. Customers are then asked to rate the support they received with colored icons."
msgid "After selecting a rating, customers are taken to a webpage where they can provide specific written feedback to support their rating. The rating is then submitted, and the rating, as well as any additional comments, are added to the chatter on the ticket."
msgid "Customer ratings can also be viewed through the :guilabel:`Customer Ratings` report. To view this report, go to :menuselection:`Helpdesk app --> Reporting --> Customer Ratings`."
msgid "After enabling the :guilabel:`Customer Ratings` setting, an option to publish ratings on the team's website appears. Enabling this setting provides portal users with an overview of the ratings the team has received over the last thirty days. Specific written feedback will not be included; only statistics of the team's performance will be visible."
msgid "To display ratings on the customer portal, a team **must** have their visibility setting set to :guilabel:`Invited portal users and all internal users (public)`. To enable this setting, navigate to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. Select a team from the list and click on it to open the settings page. Scroll to the :guilabel:`Visibility & Assignment` section, and tick the :guilabel:`Invited portal users and all internal users (public)` checkbox."
msgid "Next, to publish the ratings, go to :menuselection:`Helpdesk app--> Configuration --> Helpdesk Teams` and select a team. Scroll to :guilabel:`Performance` and tick the checkbox for :guilabel:`Publish this team's ratings on your website`."
msgid "To view the ratings for a team, a customer will log into the portal and navigate to one of their tickets. After clicking on the team name in the :guilabel:`Managed By` field, they will be directed to a page with the team's ratings over the past thirty days."
msgid "Individual ratings can be manually hidden from the portal. This allows for specific ratings to be kept out of the performance metrics shared with customers."
msgid "Navigate to :menuselection:`Helpdesk app--> Tickets --> All Tickets` and remove the :guilabel:`Open` filter from the search bar. Then filter by :guilabel:`Satisfied`, :guilabel:`Okay` and/or :guilabel:`Dissatisfied`. Select a ticket from the results. Click the :guilabel:`Rating` smart button."
msgid "Odoo's **Helpdesk** app offers multiple channels where customers can reach out for assistance, such as email, live chat, and through a website's submission form. The variety of these contact options provides customers with multiple opportunities to receive support quickly while also allowing the support team to manage multi-channel support tickets from one central location."
msgid "Go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and choose an existing team, or click :guilabel:`New` to :doc:`create a new team <../../helpdesk>`."
msgid "On the team's settings page, scroll down to the :guilabel:`Channels` and :guilabel:`Help Center` sections. Enable one or more channels by checking the respective boxes."
msgid "The following steps are for **Odoo Online** and **Odoo.sh** databases. For **On-premise** databases, external servers are required for email aliases."
msgid "To change a **Helpdesk** team's email alias, navigate to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and click on a team name to open its settings page."
msgid "If the database does not have a custom domain already configured, click :guilabel:`Set an Alias Domain` to be redirected to the :guilabel:`Settings` page. From there, enable :guilabel:`Custom Email Servers`."
msgid "When an email is received, the subject line becomes the title of a new **Helpdesk** ticket. The body of the email is also added to the ticket, under the :guilabel:`Description` tab, and in the ticket's chatter."
msgid "The **Live Chat** feature lets website visitors connect directly with a support agent or chatbot. **Helpdesk** tickets can be instantly created during these conversations using the :doc:`response command </applications/websites/livechat/responses>` `/ticket`."
msgid "To enable **Live Chat**, navigate to the :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` list view, select a team, and on the team's settings page, click the checkbox next to :guilabel:`Live Chat`, under the :guilabel:`Channels` section."
msgid "If this is the first time :doc:`Live Chat </applications/websites/livechat>` has been enabled on the database, the page may need to be saved manually and refreshed before any further steps can be taken."
msgid "After the :guilabel:`Live Chat` setting is enabled on a **Helpdesk** team, a new **Live Chat** channel is created. Click on :guilabel:`Configure Live Chat Channel` to update the channel's settings."
msgid "On the channel's settings page, :guilabel:`Channel Name` can be edited, though, Odoo names the channel to match the **Helpdesk** team name, by default."
msgid "*Operators* are the users who act as agents and respond to live chat requests from customers. The user who created the live chat channel is added by default."
msgid "Creating a new user can impact the status of an Odoo subscription, as the total number of users in a database counts towards the billing rate. Proceed with caution before creating a new user. If a user already exists, adding them as an operator will **not** alter the subscription or billing rate for a database."
msgid "Additionally, current operators can be edited or removed by clicking on their respective boxes in the :guilabel:`Operators` tab, and then adjusting their form values on the pop-up form that appears, or by using one of the buttons located at the bottom of the form, such as :guilabel:`Remove`."
msgid ":guilabel:`Livechat Button Color`: This field alters the color of the live chat button as it appears on the website. To change the color, click on a color bubble to open the color selection window, then click and drag the circle along the color gradient. Click out of the selection window once complete. Click the refresh icon to the right of the color bubbles to reset the colors to the default selection."
msgid ":guilabel:`Show with notification`: The chat button is displayed, with the addition of the :guilabel:`Notification text` from the :guilabel:`Options` tab."
msgid ":guilabel:`Open automatically`: The chat button is displayed, and automatically opens the chat window after a designated amount of time. The amount of time is designated in the :guilabel:`Open automatically timer` field, which appears only when this display option is selected."
msgid "Color selection, for the button or header, can be made manually, or through RGB, HSL, or HEX code selection. Different options are available, depending on the operating system or browser."
msgid "The :guilabel:`Channel Rules` tab determines when the live chat window opens on the website by logic of when a :guilabel:`URL Regex` action is triggered (e.g., a page visit)."
msgid "A regex, or regular expression, is sometimes referred to as a rational expression. It is a sequence of characters that specifies a match pattern in text. A match is made within the given range of numbers or for the set of characters."
msgid "To include a :guilabel:`Chatbot` on this channel, select it from the drop-down menu. If the chatbot should only be active when no operators are available, check the box labeled :guilabel:`Enabled only if no operator`."
msgid "If a :doc:`chatbot </applications/websites/livechat/chatbots>` is added to a live chat channel, a new :guilabel:`Chatbots` smart button appears on the channel settings form. Click here to create and update the chatbot *script*."
msgid "Each line in the script contains a :guilabel:`Message`, :guilabel:`Step Type`, :guilabel:`Answers`, and conditional *Only If* logic that applies when certain pre-filled answers are chosen."
msgid "Add the URLs for the pages where the channel should appear in the :guilabel:`URL Regex` field. Only the path from the root domain is needed, not the full URL."
msgid "If this channel should only be available to users in specific countries, add those countries to the :guilabel:`Country` field. If this field is left blank, the channel is available to all site visitors."
msgid "The :guilabel:`Widget` tab on the live chat channel form offers a website widget that can be added to third-party websites. Additionally, a URL is available, that can provide instant access to a live chat window."
msgid "The live chat :guilabel:`Widget` can be applied to websites created through Odoo by navigating to the :menuselection:`Website app --> Configuration --> Settings --> Email & Marketing`. Then, scroll to the :guilabel:`Live Chat` field, and select the channel to add to the site. Click :guilabel:`Save` to apply."
msgid "To add the widget to a website created on a third-party website, click the :guilabel:`Copy` button next to the first listed code, and paste the code into the `<head>` tag on the site."
msgid "To send a live chat session to a customer or supplier, click the :guilabel:`Copy` button next to the second listed code, and send the URL via email."
msgid "During the conversation, an operator can use the shortcut :doc:`command </applications/websites/livechat/responses>` `/ticket` to create a ticket without leaving the chat window. The transcript from the conversation is added to the new ticket, under the :guilabel:`Description` tab."
msgid "**Helpdesk** tickets can also be created through the :doc:`WhatsApp </applications/productivity/whatsapp>` app using the same `/ticket` command."
msgid "Enabling the *Website Form* setting adds a new page to the website with a customizable form. A new ticket is created once the required form fields are filled out and submitted."
msgid "To activate the website form, navigate to a team's settings page under :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and selecting the desired team from the list."
msgid "If more than one website is active on the database, confirm the correct website is listed in the :guilabel:`Website` field. If not, select the correct one from the drop-down list."
msgid "After the feature is activated, click the :guilabel:`Go to Website` smart button at the top of the :guilabel:`Teams` settings page to view and edit the new website form, which is created automatically by Odoo."
msgid "After enabling the :guilabel:`Website Form` setting, the team's settings page may need to be refreshed before the :guilabel:`Go to Website` smart button appears."
msgid "Additionally, if a *Help Center* is published, the smart button navigates there first. Simply click the :guilabel:`Contact Us` button, at the bottom of the forum, to navigate to the ticket submission form."
msgid "To customize the default ticket submission form, while on the website, click the :guilabel:`Edit` button in the upper-right corner of the page. This opens the editing sidebar on the right side. Then, click on one of the fields in the form, on the body of the website, to edit it."
msgid ":guilabel:`Label`: give the form field a label (e.g. `Full Name`, `Email Address`, etc.). Also control the label position on the form by using the nested :guilabel:`Position` options."
msgid ":guilabel:`Description`: determine whether or not to add an editable line under the input box to provide additional contextual information related to the field."
msgid ":guilabel:`Default Value`: add common use case values that most customers would find valuable. For example, this can include prompts of information customers should include to make it easier to solve their issue, such as an account number, or product number."
msgid ":guilabel:`Required`: determine whether or not to mark a field as required, in order for the form to be submitted. Toggle the switch from gray to blue."
msgid ":guilabel:`Visibility`: allow for absolute or conditional visibility of the field. Nested options, such as, device visibility, appear when certain options are selected."
msgid "Once the form has been optimized, and is ready for public use, click :guilabel:`Save` to apply the changes. Then, publish the form by toggling the :guilabel:`Unpublished` switch to :guilabel:`Published` at the top of the page, if necessary."
msgid "Tickets are set to low priority (0 stars) by default. To change the priority level, select the appropriate number of stars on the Kanban card, or on the ticket."
msgid "As priority levels can be used as criteria for assigning :doc:`SLAs <sla>`, changing the priority level of a ticket can alter the :abbr:`SLA (Service Level Agreement)` deadline."
msgid "Reports in Odoo *Helpdesk* provide the opportunity to manage employee workloads, identify areas for improvement, and confirm if customer expectations are being met."
msgid "Details about the reports available in Odoo *Helpdesk* can be found below. To view the different reports, go to :menuselection:`Helpdesk app --> Reporting`, and select one of the following: :guilabel:`Tickets Analysis`, :guilabel:`SLA Status Analysis`, or :guilabel:`Customer Ratings`."
msgid "The *Tickets Analysis* report (:menuselection:`Helpdesk app --> Reporting --> Tickets Analysis`) provides an overview of every customer support ticket in the database."
msgid "This report is useful for identifying where teams are spending the most time, and helps determine if there is an uneven workload distribution among the support staff. The default report counts the number of tickets per team and groups them by stage."
msgid "Alternative measures can be selected to track where the most time is spent at different points in the workflow. To change the measures used for the report that is currently displayed, or to add more, click the :guilabel:`Measures` button, and select one or more options from the drop-down menu:"
msgid ":guilabel:`Average Hours to Respond`: average number of working hours between a message sent from the customer and the response from the support team. *This does not include messages sent when the ticket was in a folded stage.*"
msgid ":guilabel:`Hours Open`: number of hours between the date the ticket was created and the closed date. If there is no closed date on the ticket, the current date is used. **This measure is not specific to working hours.**"
msgid ":guilabel:`Hours Spent`: number of *Timesheet* hours logged on a ticket. *This measure is only available if Timesheets are enabled on a team, and the current user has the access rights to view them.*"
msgid ":guilabel:`Hours to First Response`: number of working hours between the date the ticket was received and the date on which the first message was sent. *This does not include email sent automatically when a ticket reaches a stage.*"
msgid "*Working hours* are calculated based on the default working calendar. To view or change the working calendar, go to the :menuselection:`Settings` application and select :menuselection:`Employees --> Company Working Hours`."
msgid "The *SLA Status Analysis* report (:menuselection:`Helpdesk app --> Reporting --> SLA Status Analysis`) :ref:`analyzes the performance <helpdesk/analyze-sla-performance>` of individual SLA (Service Level Agreement) policies."
msgid "By default, this report is filtered to show the number of |SLAs| failed, in progress, and the number that have been successful. The results are grouped by teams."
msgid "To change the measures used for the report that is currently displayed, or to add more, click the :guilabel:`Measures` button, and select one or more options from the drop-down menu:"
msgid ":guilabel:`Working Hours to Assign`: number of working hours between the date the ticket was created and when it was assigned to a team member."
msgid "The *Customer Ratings* report (:menuselection:`Helpdesk app--> Reporting --> Customer Ratings`) displays an overview of the ratings received on individual support tickets, as well as any additional comments submitted with the rating."
msgid "On any Odoo report, the view and filter options vary, depending on what data is being analyzed, measured, and grouped. See below for additional information on the available views for the *Helpdesk* reports."
msgid "To add a group to a row or column to the pivot view, click the :icon:`fa-plus-square` :guilabel:`(plus)` icon next to :guilabel:`Total`, and then select one of the groups. To remove one, click the :icon:`fa-minus-square-o` :guilabel:`(minus)` icon, and de-select the appropriate option."
msgid "Switch to the graph view by selecting the :icon:`fa-area-chart` :guilabel:`(area chart)` icon at the top-right of the screen. To switch between the different charts, select the *related icon* at the top-left of the chart, while in graph view."
msgid "Both the *bar chart* and *line chart* can utilize the *stacked* view option. This presents two or more groups of data on top of each other, instead of next to each other, making it easier to compare data. While viewing either a bar chart or line chart, click the :icon:`fa-database` :guilabel:`(stacked)` icon to toggle the stacked view option on or off."
msgid "The *Favorites* feature found on *Helpdesk* reports allows users to save their most commonly used filters, without having to reconstruct them every time they are needed."
msgid "Tick the :guilabel:`Default Filter` checkbox to have these filter settings automatically displayed when the report is opened. Otherwise, leave it blank."
msgid "Tick the :guilabel:`Shared` checkbox to make this filter configuration available to all other database users. If this checkbox is not ticked, only the user who creates the filter can access it."
msgid "A *service level agreement* (SLA) defines the level of support a customer can expect from a service provider. |SLAs| provide a timeline that tells customers when they can expect results and keeps the support team on target."
msgid "To turn off the feature, or edit the working hours, navigate to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. Click on a team to open that team's configuration page."
msgid "From here, scroll to the :guilabel:`Performance` section. To turn off the |SLAs| feature for the team, clear the :guilabel:`SLA Policies` checkbox."
msgid "Alternatively, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and click on a team. Then, click the :guilabel:`SLA Policies` smart button at the top of the team's settings page, and click :guilabel:`New`."
msgid "On the blank |SLA| policy form, enter a :guilabel:`Title` and a :guilabel:`Description` for the new policy, and proceed to fill out the form using the steps below."
msgid ":guilabel:`Priority`: The priority level for a ticket is identified by selecting one, two, or three of the :icon:`fa-star-o` :guilabel:`(star)` icons, representing the priority level on the Kanban card or on the ticket itself. The |SLA| is **only** applied after the priority level has been updated on the ticket to match the |SLA| criteria. If no selection is made in this field, this policy only applies to tickets marked as `Low Priority`, meaning those with zero :icon:`fa-star-o` :guilabel:`(star)` icons."
msgid ":guilabel:`Services`: This field is available only if a team has the **Timesheets** app enabled. This allows the ticket to link directly to a specific line on a sales order, which must be indicated on the ticket in the :guilabel:`Sales Order Items` field."
msgid "The new policy, titled `8 Hours to close`, is assigned to the `VIP Support` team. It **only** applies to tickets that are assigned three :icon:`fa-star-o` :guilabel:`(star)` icons, which equates to an `Urgent` priority level."
msgid "At the same time, the tickets can be related to multiple issues, so the policy applies to tickets with `Repair`, `Service`, or `Emergency` tags."
msgid "A *target* is the stage a ticket needs to reach, and the time allotted to reach that stage, in order to satisfy the |SLA| policy. Any stage assigned to a team may be selected for the :guilabel:`Reach Stage` field."
msgid "An |SLA| titled `8 Hours to Close` tracks the working time before a ticket is completed, and would have `Solved` as the :guilabel:`Reach Stage`. Simultaneously, an |SLA| titled `2 Days to Start` tracks the working time before work on a ticket has begun, and would have `In Progress` as the :guilabel:`Reach Stage`."
msgid "As soon as it is determined that a ticket fits the criteria of an |SLA| policy, a deadline is calculated. The deadline is based on the creation date of the ticket, as well as the targeted working hours."
msgid "The value indicated next to the :guilabel:`Working Hours` field of an |SLA| policy is used to determine the deadline. By default, this is determined by the value set in the :guilabel:`Company Working Hours` field under :menuselection:`Settings app --> Employees --> Work Organization`."
msgid "If a ticket fits the criteria for more than one |SLA|, the earliest occurring deadline is displayed on the ticket. After that deadline has passed, the next deadline is displayed."
msgid "If the |SLA| deadline passes and the ticket has not moved to the :guilabel:`Reach Stage`, the |SLA| tag turns red. After the |SLA| has failed, the red tag stays on the ticket, even after the ticket is moved to the :guilabel:`Reach Stage`."
msgid "The :guilabel:`SLA Status Analysis` report tracks how quickly an |SLA| is fulfilled, as well as the performance of individual team members. Navigate to the report, and corresponding pivot table, by going to :menuselection:`Helpdesk app --> Reporting --> SLA Status Analysis`."
msgid "By default, the report displays in a :guilabel:`Pivot` view. Any |SLA| policies in the database with tickets that failed to fulfill a policy, are in progress, or have satisfied a policy are listed. By default, they are grouped by team and ticket count."
msgid "To change the display, or add additional measurements, click the :guilabel:`Measures` button to reveal a drop-down menu of reporting criteria, and choose from the options available."
msgid "Whenever a measurement is picked, a :icon:`fa-check` :guilabel:`(check)` icon appears in the drop-down menu to indicate that the measurement is included, and a corresponding new column emerges in the pivot table to show the relevant calculations."
msgid "To add a group to a row or column, click the :icon:`fa-plus-square` :guilabel:`(plus)` icon next to the policy name and then select one of the groups. To remove one, click the :icon:`fa-minus-square-o` :guilabel:`(minus)` icon next to the policy name."
msgid "Switch to the graph view by selecting the :icon:`fa-area-chart` :guilabel:`(graph view)` icon at the top of the screen. To switch between the different charts, select the *related icon* at the top of the chart, while in graph view."
msgid "The *cohort* view is used to track the changes in data over a period of time. To display the :guilabel:`SLA Status Analysis` report in a cohort view, click the :icon:`oi-view-cohort` :guilabel:`(cohort)` icon, next to the other view options."
msgid "*Stages* are used to organize the **Helpdesk** pipeline and track the progress of tickets. Stages are customizable, and can be renamed to fit the needs of each team."
msgid ":ref:`Developer mode <developer-mode>` **must** be activated to access the stages menu. To activate developer mode, go to :menuselection:`Settings app --> General Settings --> Developer Tools`, and click :guilabel:`Activate the developer mode`."
msgid "The default list view on the :guilabel:`Stages` page displays the stages currently available in the **Helpdesk** app. They are listed in the order they appear in the pipeline."
msgid "To change the order of the stages, click the :icon:`oi-draggable` :guilabel:`(draggable)` icon, to the left of the stage name, and drag it to the desired place on the list."
msgid "When an :guilabel:`Email Template` is added to a stage, a preconfigured email is automatically sent to the customer when a ticket reaches that specific stage in the pipeline. Likewise, adding an :guilabel:`SMS Template` triggers a preconfigured SMS text message to send to the customer."
msgid "SMS text messaging is an :doc:`In-App Purchase (IAP) </applications/essentials/in_app_purchase/>` service that requires prepaid credits to work. Refer to `SMS Pricing FAQ <https://iap-services.odoo.com/iap/sms/pricing>`_ for additional information."
msgid "To select an existing email template, select it from the :guilabel:`Email Template` field. After choosing a template, click on the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon to the right of the field to edit the chosen template."
msgid "To create a new template from this form, click the field, and enter a title for the new template. Then, select :guilabel:`Create and edit` from the drop-down menu that appears, and complete the form details."
msgid "By default, stages are unfolded in the Kanban view of either tickets dashboard: :guilabel:`My Tickets` (:menuselection:`Helpdesk app --> Tickets --> My Tickets`) or :guilabel:`All Tickets` (:menuselection:`Helpdesk app --> Tickets --> All Tickets`)."
msgid "Tickets that reach a *folded* stage are considered *closed*. Closing a ticket before the work is completed can result in reporting and communication issues. This setting should **only** be enabled for stages that are considered *closing* stages."
msgid "Hover the cursor at the top of the desired stage to fold temporarily, then click the :icon:`fa-gear` :guilabel:`(gear)` icon that appears, and select :guilabel:`Fold` from the drop-down menu."
msgid "Make a selection in the :guilabel:`Helpdesk Teams` field on the :guilabel:`Stages` form. More than one team may be selected, since the same stage can be assigned to multiple teams."
msgid "Handling your team's planning comes with specific requirements that may vary widely depending on your business needs. The following concepts were introduced in Odoo Planning to meet those needs:"
msgid "**Shifts** are dispatched to **resources**, which can be either :ref:`human <planning/employees>` (employees) or :ref:`material <planning/materials>` (e.g., equipment). The resources are assigned :ref:`roles <planning/roles>`, which allows for organization of work within the team."
msgid "Once the initial configuration is done, :ref:`planning shifts <planning/shifts>` can be done manually or automated by using the :ref:`Auto Plan <planning/open-shifts>` feature."
msgid "An integration between the Planning and Sales apps allows the linking of sold services to roles and shifts in Planning. Additionally, integration with :doc:`Project <project>` allows dedicating shifts, and thus time and resources, to specific projects."
msgid "To define the roles your resources perform (e.g., chef, bartender, waiter), go to :menuselection:`Planning --> Configuration --> Roles`, then click :guilabel:`New`, and fill in the :guilabel:`Name` (e.g., assistant, receptionist, manager). Then, choose the :guilabel:`Resources` that will perform this role. Resources can be either :ref:`Employees <planning/employees>` or :ref:`Materials <planning/materials>`."
msgid "If the Sales app is installed in your database, the :guilabel:`Services` field appears, allowing you to specify which roles are needed to perform services so that the shifts are dispatched to the right person."
msgid "**Property fields** allow you to add custom fields to forms across several Odoo applications. Planning includes the possibility of adding property fields linked to roles to shifts."
msgid "To create a property field, switch to the list view from any schedule. From there, click :guilabel:`View` on the shift that you wish to edit. If the :guilabel:`Role` field is empty, fill it in with the desired role, then click the cog icon and select :guilabel:`Add Properties`. :doc:`Configure <../productivity/knowledge/properties>` the new field according to your needs."
msgid "To adapt the employee's planning settings, go to :menuselection:`Planning --> Configuration --> Employees`, and choose the employee for whom you want to edit the settings. Then, go to the :guilabel:`Work Information` tab."
msgid "Two sections of the employee's :guilabel:`Work Information` tab have an impact on Planning: :guilabel:`Schedule` (namely, the :guilabel:`Working Hours` field) and :guilabel:`Planning`."
msgid "The :guilabel:`Working Hours` are taken into account when the :guilabel:`Allocated Time` and its percentage is calculated for :ref:`shifts <planning/templates>`. If the :guilabel:`Working Hours` field is left blank, the employee is considered to be working flexible hours."
msgid "To create individual :guilabel:`Working Hours`, for example, for employees working part-time, click :guilabel:`Search more...`, then :guilabel:`New`."
msgid "The :guilabel:`Working Hours` and the :guilabel:`Allocated Time` in Planning can impact **Payroll**, if the employee's contract is configured to generate work entries based on shifts."
msgid "If the Planning roles fields are left empty, there are no restrictions in the shift templates and open shifts shared with the employee. However, it’s not possible to use the **Auto Plan** feature for employee with no roles."
msgid "**Materials** are resources that can be assigned shifts and working hours but are not employees. For example, a construction company could use materials to create shifts for shared machines (e.g., cranes, forklifts)."
msgid "To create a shift template, click :guilabel:`New` on any schedule, then fill in the :ref:`details of the shift <planning/create-shift>`. In order for the shift to be saved as a template, tick :guilabel:`Save as Template`."
msgid "Alternatively, you can go to :menuselection:`Planning --> Configuration --> Shift Templates`, then click :guilabel:`New`. Fill in the :guilabel:`Start Hour` and :guilabel:`Shift Duration`. The shift’s :guilabel:`End Time` is then calculated based on the :guilabel:`Working Hours`, taking into account working time as well as breaks."
msgid "Creating a shift template with a start hour of 9 am and a duration of 8 hours will result in the end hour being 5 pm, based on the working hours and the 1-hour break."
msgid "Creating a shift template with a start hour of 10 am and a duration of 10 hours will result in the end hour of 10 am the following day, as the company is closed at 5 pm according to the working hours."
msgid "On opening the Planning app, the users see their own schedule. Users with admin roles can also see :guilabel:`Schedule by Resource`, :guilabel:`Role`, :guilabel:`Project`, or :guilabel:`Sales Order`, as well as reporting and configuration menus."
msgid "The schedule is displayed in the Gantt view, which allows you to edit (with a drag and drop), resize, split, and duplicate shifts without having to open them."
msgid "**Grayed-out shift**: when copying shifts, the copied shifts are shown in full color, whereas previously existing shifts are temporarily greyed out. The color changes back to full color or diagonal stripes on the next refresh of the page or by removing the filter."
msgid "**Templates**: If there is one or more templates existing in your database, they are displayed in the upper section of the pop-up window. Once selected, a template prefills the shift form accordingly."
msgid ":guilabel:`Resource`: Resources can be both employees or materials. If this field is left empty, the shift is considered an :ref:`open shift <planning/open-shifts>`."
msgid ":guilabel:`Role`: Select the role that the resource assigned will be performing. This field is used when :ref:`auto-planning <planning/open-shifts>` shifts. Once you select a role, the shift templates associated with it are displayed in the upper section of the pop-up window."
msgid ":guilabel:`Project`: If the Project app is installed in your database, this field allows you to link the project to the shift is available, allowing you to plan and track shifts dedicated to work on the selected project."
msgid ":guilabel:`Repeat`: Tick the checkbox and configure the :guilabel:`Repeat Every` field according to your needs. The following rules apply to recurring shifts:"
msgid "All fields (e.g., :guilabel:`Resource`, :guilabel:`Role`, :guilabel:`Project`) are copied from the original shift except for the date, which is adjusted according to the :guilabel:`Repeat Every` field."
msgid "By default, planned shifts are created six months in advance, after which they are created gradually. To change the time frame, :ref:`activate the Developer mode <developer-mode>`, then go to :menuselection:`Planning --> Configuration --> Settings` and edit the :guilabel:`Recurring Shifts`."
msgid ":guilabel:`Save as Template`: When this option is ticked, a shift template is created with the same :guilabel:`Start and End hours`, :guilabel:`Allocated time`, :guilabel:`Role`, and :guilabel:`Project`."
msgid ":guilabel:`Allocated time`: Is calculated based on the date and the employee’s :guilabel:`Working Schedule`. See more in :ref:`Shift Templates <planning/templates>`."
msgid "The draft is visible on the admin planning view and can be identified by diagonal lines. The employee is only notified of the shift once it's published."
msgid "The :guilabel:`Auto Plan` button allows you to assign **Open shifts** (shifts with no resource assigned) and create and assign shifts linked to sales orders or project."
msgid "**Roles**: Open shifts are only assigned to resources (employees or materials) that have the corresponding role assigned. It is not possible to use the :guilabel:`Auto Plan` feature for employee with no roles."
msgid "These features are mutually exclusive. Switching shifts is possible by default and cannot be disabled. However, once the **Allow unassignment** feature is enabled, it replaces the option to switch shifts."
msgid "Once shifts are planned and published, employees receive an email notification. If an employee wishes to switch a shift, they can click the unwanted shift and click :guilabel:`Ask to switch`."
msgid "The shift remains assigned to the original employee, but in the schedule, a notification informing that the assigned employee would like to switch shifts is visible on the shift."
msgid "The shift is then displayed to other employees who share the same role, and if they wish to assign it to themselves, they can click the :guilabel:`I take it` button."
msgid "To allow employees to unassign themselves from shifts, go to :menuselection:`Planning --> Configuration --> Settings`, then tick the checkbox :guilabel:`Allow Unassignment`. Then, specify the maximum number of days that the employees can unassign themselves before the shift."
msgid "Once shifts are planned and published, employees receive an email notification. If shift unassignment is allowed, the employees can click the :guilabel:`I am unavailable` button, and the shift reverts to an open shift."
msgid "Odoo Project is a tool to manage your ongoing projects. Schedule tasks, assign activities to coworkers, and keep track of each project's profitability."
msgid "The project dashboard allows you to get a comprehensive overview of your project's status. It displays information such as the total number of tasks, timesheets, and planned hours linked to the project, as well as detailed information about project milestones and its costs and revenues. Within the project dashboard, you can create :guilabel:`Project updates`, which allow you to take a snapshot of the project's status at a certain point in time. As such, it is a crucial tool for effective project management and ensuring that your project stays on track."
msgid "To access the project dashboard, open the **Project** app and hover over the desired project’s card. Then, click the :icon:`fa-vertical-ellipsis` (:guilabel:`vertical ellipsis`) icon and select :guilabel:`Dashboard`. Alternatively, you can access the project dashboard from the project’s :ref:`top bar <project/project-management/top-bar>`."
msgid "The left side of the dashboard displays a list of existing :ref:`project updates <project/project-dashboard/updates>`, and the right side provides :ref:`detailed information about records linked to the project <project/project-dashboard/smart-buttons>`, as well as :ref:`milestones <project/project-dashboard/milestones>`, :ref:`profitability <project/project-dashboard/profitability>`, and :ref:`budgets <project/project-dashboard/budgets>`."
msgid "The information displayed on the project dashboard varies depending on the applications installed on your database. For example, you will not see information about **Timesheets**, **Planning**, or **Purchase Orders** if the corresponding applications are not installed."
msgid ":guilabel:`Tasks`: the number of completed (i.e., :guilabel:`Done` or :guilabel:`Canceled` :ref:`tasks <project/tasks/task_stages_statuses/statuses>`) and all tasks, in format completed/all, as well as the entire project's completion percentage estimation."
msgid ":guilabel:`Timesheets`: the number of hours or days (depending on the **Timesheets** app configuration) allocated in the project’s **settings**. This includes all :doc:`timesheets <../timesheets>`, whether or not they have been validated."
msgid ":guilabel:`Planned`: the number of hours that have been planned for shifts in the **Planning** app. This includes all :doc:`planned shifts <../planning>`, including past shifts and shifts that have not yet been published."
msgid ":guilabel:`Burndown Chart`: click the smart button to access a :doc:`report </applications/essentials/reporting>` on the status of the project’s tasks over time."
msgid ":guilabel:`Timesheets and Planning`: click the smart button to access a :doc:`report </applications/essentials/reporting>` on the project’s timesheets and shifts. This allows you to easily compare planned and effective hours of work on the project."
msgid "**Additional fields**, such as :guilabel:`Sales Orders`, :guilabel:`Sales Order Items`, :guilabel:`Purchase Orders`, and more, represent the number of records linked to the project."
msgid "Use the project dashboard smart buttons to update the project records easily. Click :guilabel:`Timesheets` to validate timesheets, :guilabel:`Planned` to create project planning, :guilabel:`Documents` to view and validate documents, etc."
msgid "This section is only visible if :doc:`milestones </applications/sales/sales/invoicing/milestone>` have been enabled in the Project’s app settings. Click :guilabel:`Add Milestone` to create a new milestone. Click a milestone in the checklist to edit it, enable its checkbox to mark it as completed, or click the :icon:`fa-trash` (:guilabel:`trash`) icon to remove it."
msgid "The milestones are displayed in red if they’re past their deadline, or in green if they are ready to be marked as reached (i.e. tasks linked to the milestone that have been marked with :guilabel:`done` or :guilabel:`canceled` :ref:`status <project/tasks/task_stages_statuses/statuses>`)."
msgid "This section provides a breakdown of project costs and revenues, which are impacted by all records linked to the project and its :doc:`Analytic account </applications/finance/accounting/reporting/analytic_accounting>`."
msgid "If a budget has been set for the project, its status and related details are displayed in this section. Click :guilabel:`Add Budget` to create a new budget for the project."
msgid ":doc:`Budgets </applications/finance/accounting/reporting/budget>` must be enabled in your database’s **Accounting** application in order for this section to be displayed."
msgid "Project updates allow you to take a snapshot of the project’s overall status at a given point in time, for example, during a periodic (weekly, bi-weekly, or monthly) review. This allows you to compare specific data points, note any aspects of the project that need improvement, and estimate if the project is on or off track."
msgid ":guilabel:`Status`: Choose between :guilabel:`On Track`, :guilabel:`At Risk`, :guilabel:`Off Track`, :guilabel:`On Hold`, and :guilabel:`Done`. Once the status is set, a color-coded dot is displayed on the project’s Kanban card, allowing the project manager to easily identify which projects need attention."
msgid ":guilabel:`Date` and :guilabel:`Author`: These fields are automatically filled in with appropriate information based on the user who created the update and the current date."
msgid ":guilabel:`Description`: Use this rich-text field to gather notes. Depending on the project configuration (e.g., if the project is billable), this field may be pre-filled with current information on aspects such as profitability, budget, milestones, etc."
msgid "Odoo Project uses the **Kanban** project management system. This means all projects are broken down into tasks, which are categorized on a whiteboard according to what production phase they are in."
msgid "Open the **Project** app and click :guilabel:`Create` to start a new project. Enter a :guilabel:`Name` for your project and click :guilabel:`Create Project`."
msgid "You can customize your existing **projects** from the dashboard by clicking the drop-down toggle button (:guilabel:`⋮`) on your project's **card**."
msgid ":guilabel:`View`: see an overview of your project's components, such as its :guilabel:`Tasks`, :guilabel:`Milestones` and :guilabel:`Project Updates`. Depending on which apps you have activated, more options may be available, such as :guilabel:`Documents`. All uploaded files can be found under this menu, as well as in the **Documents** app, under :guilabel:`Projects`;"
msgid "Additionally, you can mark the project as :guilabel:`Favorite`, allowing you to find it using the :guilabel:`My Favorites` filter on the Kanban view;"
msgid "You can schedule **activities** (ex. :guilabel:`Call`, :guilabel:`Meeting`, etc.) per project by clicking on the **clock** icon on a project. Doing so opens a list with already scheduled activities and allows planning **new** activities by clicking :guilabel:`+ Schedule an activity`. On the pop-up window, select the :guilabel:`Activity Type`, enter a :guilabel:`Summary` for that activity, a :guilabel:`Due Date`, and assign it to an employee. According to the :guilabel:`Activity Type`, you may have **additional options** available."
msgid "In project management, reviewing the various records and documents related to a project is often necessary. Odoo Project’s **top bar** provides quick access to these essential resources. You can customize each project's top bar to match its specific needs."
msgid "To set up the top bar for a project, go to the :guilabel:`Project` app, click the project's card, then click the top bar :icon:`fa-sliders` :guilabel:`(sliders)` button. In the bar that appears above the search bar, click the :icon:`fa-sliders` :guilabel:`(sliders)` button to select the records you want to display, such as timesheets, sales orders, invoices, documents, dashboards, etc."
msgid "You can then click the buttons to access the related records without leaving the Project app. To return to your project tasks' Kanban view, click the :guilabel:`Tasks` button in the top bar."
msgid "When handling a project, the same task often needs to be performed several times: for example, weekly meetings or status reports. The **recurring tasks** feature allows you to automate the creation of those tasks."
msgid "To enable recurring tasks, go to :menuselection:`Project --> Configuration --> Settings`, then activate :guilabel:`Recurring Tasks`, and press :guilabel:`Save`."
msgid "In an existing task, click the :icon:`fa-repeat` (:guilabel:`Recurrent`) button next to the :guilabel:`Deadline` field. Then, configure the :guilabel:`Repeat Every` field according to your needs."
msgid ":guilabel:`Name`, :guilabel:`Description`, :guilabel:`Project`, :guilabel:`Assignees`, :guilabel:`Customer`, :guilabel:`Tags`: are copied from the original task;"
msgid ":guilabel:`Deadline`: is updated based on the :guilabel:`Repeat Every` field (e.g., if the task is set to repeat once a week, 7 days will be added to the deadline);"
msgid ":guilabel:`Milestones`, :guilabel:`Timesheets`, :guilabel:`Chatter`, :guilabel:`Activities`, :guilabel:`Subtasks`: are **not** copied from the original task."
msgid "**To edit** the recurrence, open the last task in recurrence. Any changes made on the task will be applied to the tasks that will be created in the future."
msgid "When handling project tasks, you can often benefit from splitting the workload into smaller **sub-tasks**, making it easier to track progress and manage the work."
msgid "The original task to which sub-tasks are linked is referred to as the **parent task**. The sub-tasks of the parent task are known as **child tasks**."
msgid "You can edit several fields of a sub-task directly from the parent task’s sub-task tab without opening the individual sub-task. By default, those are: :guilabel:`Title`, :guilabel:`Priority`, :guilabel:`Status`, and :guilabel:`Assignees`. Use the :icon:`fa-sliders` (:guilabel:`sliders`) icon to add or remove fields."
msgid "A **smart button** displays the total number of sub-tasks, as well as the number of closed (**done** or **canceled**) sub-tasks. Click the smart button to access the list of the sub-tasks."
msgid "The :guilabel:`Allocated time` displays the amount of time allocated to the parent task, as well as time allocated to the sub-tasks. This can be used to ensure that the time allocated to sub-tasks does not exceed time allocated to the parent task."
msgid "Click :guilabel:`View` to open the sub-task you created. The sub-task form is identical to the :ref:`task form <task_creation/task-configuration>`."
msgid "Clicking the :icon:`fa-plus` (:guilabel:`plus`) button in the upper left corner. This creates a new task in the first stage of your Kanban view."
msgid ":icon:`fa-star-o` (:guilabel:`Star`): click the :icon:`fa-star-o` (:guilabel:`star`) icon to mark the task as high priority. The icon will turn yellow. Click it again to remove the high priority."
msgid ":guilabel:`Customer`: the person or company that will be billed for this task. This field only appears in tasks that belong to billable projects."
msgid ":guilabel:`Sales Order Item`: this can be either the sales order that was used to create this task, or a sales order that was linked to this task manually. This field only appears in tasks linked to billable projects."
msgid ":guilabel:`Deadline`: the expected end date of the task. Once this field is filled in, you can also add a start date to designate the entire time frame of the tasks' duration."
msgid "The following fields can also be edited directly from the Kanban view without opening the individual task: :icon:`fa-star-o` (**priority**), :guilabel:`Allocated hours`, :guilabel:`Assignees`, and **task status**. You can also **color code** or :guilabel:`Set a Cover image` to your task by clicking the :icon:`fa-ellipsis-v` (**vertical ellipsis**)."
msgid "You can use the following keyboard shortcuts in the task title to configure new tasks (modify the values in the examples below according to your needs):"
msgid "Along with using the correct format, follow this order: the task's name, followed by the allocated time, the tags, the assignee, and then the priority."
msgid "For example, if you want to create a task named \"Prepare workshop\", allocate 5h hours to it, add the \"School\" tag, assign it to Audrey and set its priority to :guilabel:`High`, enter the following task title: Prepare workshop 5h #school @Audrey !"
msgid "To configure it, open the Project app, then click the :icon:`fa-ellipsis-v` (:guilabel:`vertical ellipsis`) icon next to the desired project's name. Select :guilabel:`Settings`, then open the :guilabel:`Settings` tab."
msgid "If you have the Website app installed in your database, you can configure any form on your website to trigger the creation of tasks in a project."
msgid "Go to the website page where you wish to add the the form and :ref:`add the Form building block <websites/website/web_design/building_blocks>`."
msgid "Odoo Project allows you to break down projects into tasks and establish relationships between those tasks to determine the order in which they are executed. Task dependencies ensure that certain tasks begin only after the preceding tasks are completed."
msgid "To enable task dependencies in projects, go to :menuselection:`Project --> Configuration --> Settings`, enable :guilabel:`Task Dependencies`, and click :guilabel:`Save`."
msgid "Task dependencies can be created from the task form or the project's Gantt view by linking the successor task (i.e., the task blocked by other tasks) to its predecessor task(s) (i.e., the tasks blocking the successor task)."
msgid "To create task dependencies from the task form, access the desired task and, in the :guilabel:`Blocked by` tab, click :guilabel:`Add a line`. Click :guilabel:`View` to access the predecessor task. To access the successor tasks from the predecessor task, click the :guilabel:`Blocked Tasks` smart button."
msgid "To create a task dependency from the Gantt view, hover your mouse over the predecessor task, then click one of the dots that appear around it. Drag and drop the dot onto the successor task. An arrow appears, indicating the dependency from the predecessor task to the successor."
msgid "Odoo automatically manages task progress based on their dependency. Successor tasks are assigned the :guilabel:`Waiting` status and cannot be moved to :guilabel:`In Progress` until their predecessor task(s) are marked as :guilabel:`Approved`, :guilabel:`Cancelled`, or :guilabel:`Done`."
msgid "From the Gantt view, click the red :icon:`fa-times` (:guilabel:`times`) button that appears at the center of the arrow when you hover your mouse over it."
msgid "Task stages are displayed as columns in the project's Kanban view, and allow you to update the progress of its tasks with a drag-and-drop. In most projects, the stages will be akin to **New**, **In progress**, **Backlog**, etc."
msgid "Odoo Project doesn’t provide default stages but instead allows you to create custom stages tailored to your specific business needs. You are prompted to do so immediately after :ref:`creating a new project <project_management/configuration>`."
msgid ":guilabel:`Automations`: to create :doc:`custom rules that trigger automatic actions <../../../studio/automated_actions>` (e.g., creating activities, adding followers, or sending webhook notifications). Note that this will activate Studio in your database, which may impact your pricing plan."
msgid "Task statuses are used to track the status of tasks within the Kanban stage, as well as to close the task when it’s done or canceled. Unlike Kanban stages, they cannot be customized; five task statuses exist in Odoo and are used as follows:"
msgid ":guilabel:`In Progress`: this is the default state of all tasks, meaning that work required for the task to move to the next Kanban stage is ongoing."
msgid ":guilabel:`Changes Requested`: to highlight that changes, either requested by the customer or internally, are needed before the task is moved to the next Kanban stage."
msgid "The :guilabel:`Changes Requested` and :guilabel:`Approved` task statuses are cleared as soon as the task is moved to another Kanban stage. The task status reverts to the default :guilabel:`In Progress` status so that :guilabel:`Changes Requested` or :guilabel:`Approved` status can be applied again once the necessary work has been completed in this Kanban stage."
msgid "The :guilabel:`Done` and :guilabel:`Canceled` statuses are independent from the Kanban stage. Once a task is marked as :guilabel:`Done` or :guilabel:`Canceled`, it is closed. If needed, it can be reopened by changing its status."
msgid "Odoo automatically timesheets on project/tasks upon time off requests. This allows for better overall control over the validation of timesheets, as it does not leave place for forgetfulness and questions after hours that have not been timesheeted by the employee."
msgid "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."
msgid "Now, once the employee has requested his time off and the request has been validated (or not, depending on the setting chosen), the time is automatically allocated on *Timesheets*, under the respective project and task."
msgid "Considering that validation is not required, the requested time off is automatically displayed in *Timesheets*. If validation is necessary, the time is automatically allocated after the responsible person for validating does it so."
msgid "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."
