documentation/locale/pl/LC_MESSAGES/services.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# 
# Translators:
# Tiffany Chang, 2024
# Wil Odoo, 2025
# Marta Wacławek, 2025
# 
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-02-20 16:01+0000\n"
"PO-Revision-Date: 2024-10-08 06:34+0000\n"
"Last-Translator: Marta Wacławek, 2025\n"
"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pl\n"
"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"

#: ../../content/applications/services.rst:5
msgid "Services"
msgstr "Usługi"

#: ../../content/applications/services/field_service.rst:8
msgid "Field Service"
msgstr "Serwis Terenowy"

#: ../../content/applications/services/field_service.rst:11
msgid ""
"`Odoo Tutorials: Field Service <https://www.odoo.com/slides/field-"
"service-49>`_"
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:3
msgid "Creating field service tasks"
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:5
msgid ""
"Tasks in Odoo Field Service can be created manually or automatically, "
"including from sales orders or helpdesk tickets."
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:9
#: ../../content/applications/services/project/tasks/task_creation.rst:9
msgid "Manual task creation"
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:11
msgid "To create a new field service task:"
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:13
msgid ""
"Open the Field service app and go to :menuselection:`Field Service --> All "
"Tasks --> All Tasks`."
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:14
msgid "Click :guilabel:`New`."
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:15
msgid ""
"Fill in the task title, :guilabel:`Customer` and any other :ref:`optional "
"field <task_creation/task-configuration>`, then save manually."
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:19
msgid "Task creation from a sales order"
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:21
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."
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:27
msgid "Task creation from a helpdesk ticket"
msgstr ""

#: ../../content/applications/services/field_service/creating_tasks.rst:29
msgid ""
"If you have the Helpdesk app installed, you can :ref:`create field service "
"tasks from a helpdesk ticket <helpdesk/field>`."
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:3
msgid "Planning an itinerary"
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:5
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:"
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:9
msgid ""
"Create or sign in to a MapBox account using the following link: "
"`<https://www.mapbox.com/>`_."
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:10
msgid ""
"`Create a token <https://docs.mapbox.com/help/getting-started/access-"
"tokens/#adding-url-restrictions-to-access-tokens>`_."
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:11
msgid ""
"Go to the `Access tokens page on Mapbox <https://account.mapbox.com/access-"
"tokens/>`_ and copy your token."
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:13
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`."
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:18
msgid "Displaying your itinerary on a map"
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:21
msgid ""
"For a field service task to be featured on the map, a **valid address** must"
" be provided for the customer."
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:24
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."
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:28
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."
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:32
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."
msgstr ""

#: ../../content/applications/services/field_service/planning_itinerary.rst:34
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."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:3
msgid "Product management"
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:5
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."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:11
msgid "Product catalog"
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:13
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."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:16
msgid "To add products to a task, proceed as follows:"
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:18
msgid "Go to Field Service and open a task."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:19
msgid "Click the :guilabel:`Products` smart button."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:20
msgid "Click :guilabel:`Add` on a product card to add it to your task."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:21
msgid ""
"If needed, adjust the number of products using the :guilabel:`-` and "
":guilabel:`+` buttons."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:23
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."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:27
msgid ""
"To create and edit products from Field Service, go to :menuselection:`Field "
"Service --> Configuration --> Products`."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:29
msgid ""
"To find your products more easily, use the search bar and filter your "
"products by :guilabel:`Product Category` and :guilabel:`Attributes`."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:33
msgid "User default warehouse"
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:35
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."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:39
msgid ""
"Products in sales orders created during field interventions are always "
"pulled from the default warehouse, keeping the inventory accurate."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:43
msgid ":doc:`../../inventory_and_mrp/inventory`"
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:46
#: ../../content/applications/services/field_service/worksheets.rst:15
#: ../../content/applications/services/helpdesk/overview/help_center.rst:15
#: ../../content/applications/services/planning.rst:29
#: ../../content/applications/services/project/project_management.rst:19
#: ../../content/applications/services/project/tasks/recurring_tasks.rst:13
msgid "Configuration"
msgstr "Konfiguracja"

#: ../../content/applications/services/field_service/product_management.rst:48
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."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:53
msgid ""
"You can either set it up :ref:`for your profile <default-warehouse/my-"
"profile>`, or :ref:`for all users <default-warehouse/all-users>`."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:57
msgid ""
":doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations`"
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:62
msgid "For your profile"
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:64
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."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:71
msgid "For all users"
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:73
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."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst-1
msgid "Selection of a default warehouse on a user profile."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:81
msgid "Use in field service tasks"
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:83
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."
msgstr ""

#: ../../content/applications/services/field_service/product_management.rst:88
msgid ""
"Once the Field Service task is marked as done, the stock of the default "
"warehouse is automatically updated."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:3
msgid "Worksheets"
msgstr "Karty pracy"

#: ../../content/applications/services/field_service/worksheets.rst:5
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."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:10
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."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:17
msgid ""
"To use worksheets in Field Service, go to :menuselection:`Field Service --> "
"Configuration --> Settings`, enable the :guilabel:`Worksheets` feature, and "
"click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:21
msgid ""
"Worksheet templates are designed using **Studio**. Enabling the "
":guilabel:`Worksheets` feature automatically installs the **Studio** app, "
"which may impact your price plan."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:25
msgid "Create a worksheet template"
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:27
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."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:31
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>`."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:35
msgid ""
"When your worksheet template is complete, click :guilabel:`Close` in the top"
" right corner of the page to leave **Studio**."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:39
msgid ":doc:`Fields and widgets in Studio <../../studio/fields>`"
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:42
msgid "Add a worksheet template to a field service task"
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:44
msgid ""
"Go to your field service task, select a :guilabel:`Worksheet Template`, and "
"click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:46
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."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst-1
msgid "Mouse on project name to setup default worksheet template"
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:54
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."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:58
msgid "Use worksheets on site"
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:60
msgid ""
"To complete the worksheet on site, access the task and click the "
":guilabel:`Worksheet` smart button."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:63
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."
msgstr ""

#: ../../content/applications/services/field_service/worksheets.rst:66
msgid ""
"Any field defined as :guilabel:`Required` has to be filled for a worksheet "
"to be saved."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:6
msgid "Helpdesk"
msgstr "Punkt Pomocy"

#: ../../content/applications/services/helpdesk.rst:8
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:14
msgid "Create a Helpdesk team"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:16
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst-1
msgid "View of the Helpdesk teams page in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:23
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:28
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:0
msgid ""
"View of a Helpdesk team's website form displaying the team description."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:37
msgid "Visibility & Assignment"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:39
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:43
msgid "Determine team visibility"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:45
msgid ""
"Under the :guilabel:`Visibility` section, select one of the following "
"options to determine who can view this team and its tickets:"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:48
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>`."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:52
msgid ""
":guilabel:`All internal users (company)`: All internal users can access the "
"team and all of its tickets."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:54
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:58
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`."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:61
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`."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:65
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:73
msgid "Follow all team's tickets"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:75
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:80
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:85
msgid "Automatically assign new tickets"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:87
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst-1
msgid ""
"View of a Helpdesk team settings page emphasizing the automatic assignment features in Odoo\n"
"Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:95
msgid ""
"Select one of the following assignment methods, based on how the workload "
"should be allocated across the team:"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:98
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:101
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:105
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:109
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:112
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:117
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:122
msgid ":ref:`Manage users <users/add-individual>`"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:123
msgid ":doc:`Access rights <../general/users/access_rights>`"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:126
msgid "Merge tickets"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:128
msgid ""
"If duplicate tickets are found in **Helpdesk**, they can be combined into a "
"single ticket using the *merge* feature."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:132
msgid ""
"The *merge* feature is **only** accessible if the :doc:`Data Cleaning "
"<../productivity/data_cleaning>` application is installed on the database."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:135
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`."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:143
msgid "Convert tickets to opportunities"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:145
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:149
msgid ""
"This feature is **only** available if the :doc:`CRM <../sales/crm>` app is "
"installed."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:151
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:154
msgid ""
"At the top of the ticket, click the :guilabel:`Convert to Opportunity` "
"button."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:157
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`."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:160
msgid ""
"This opens the :guilabel:`Convert to Opportunity` pop-up. Fill in or select "
"the following information on the pop-up:"
msgstr ""

#: ../../content/applications/services/helpdesk.rst:163
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:167
msgid ""
":guilabel:`Sales Team`: Specify which :guilabel:`Sales Team` and "
":guilabel:`Salesperson` this created opportunity is assigned to."
msgstr ""

#: ../../content/applications/services/helpdesk.rst-1
msgid "The convert to opportunity pop-up window."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:173
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."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:178
msgid ""
"After the ticket is converted to an opportunity, the ticket is archived."
msgstr ""

#: ../../content/applications/services/helpdesk.rst:181
msgid "`Odoo Tutorials: Helpdesk <https://www.odoo.com/slides/helpdesk-51>`_"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced.rst:5
msgid "Advanced"
msgstr "Zaawansowane"

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:3
msgid "After-Sales services"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:5
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:11
msgid "Set up after-sales services"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:13
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:"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:18
msgid ""
":guilabel:`Refunds`: issues credit notes to refund a customer, or adjust the"
" remaining amount due."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:19
msgid ""
":guilabel:`Coupons`: offers discounts and free products through an existing "
"coupon program."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:20
msgid ""
":guilabel:`Returns`: initiates a product return from a customer through a "
"reverse transfer."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:21
msgid ""
":guilabel:`Repairs`: creates repair orders for broken or faulty products."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:22
msgid ""
":guilabel:`Field Service`: plans onsite intervention through the *Field "
"Service* application."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:27
msgid ""
"The services that are enabled can vary based on the type of support a team "
"provides."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:30
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:38
msgid "Issue refund with credit note"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:40
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:46
msgid "Invoices **must** be posted before a credit note can be generated."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:48
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of a refund creation page."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:56
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:216
msgid "Fill out the fields with the necessary information:"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:58
msgid ""
":guilabel:`Sales Order`: if a sales order was referenced on the original "
"ticket, it automatically populates in this field."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:60
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:62
msgid ""
":guilabel:`Lot/Serial Number`: this field is **only** visible if the "
":guilabel:`Product` selected has associated lot or serial numbers."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:64
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:67
msgid ""
":guilabel:`Reason displayed on Credit Note`: this field automatically "
"populates with the ticket number, though it can be edited with additional "
"information."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:69
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:72
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**."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:75
msgid ""
"After the necessary fields are filled in, click :guilabel:`Reverse` or "
":guilabel:`Reverse and Create Invoice`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:78
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:81
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:85
msgid ""
"Once the credit note has been posted, a :guilabel:`Credit Notes` smart "
"button is added to the *Helpdesk* ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of smart buttons on a ticket focusing on the credit note button."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:93
msgid ":doc:`../../../finance/accounting/customer_invoices/credit_notes`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:98
msgid "Generate coupons from a ticket"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:100
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:105
msgid ""
"The *eCommerce* module **must** be installed to create coupon codes from the"
" *Website*."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:107
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of a coupon generation window."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:116
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:121
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:125
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:128
msgid ""
"Click :guilabel:`Send by Email` to compose an email to send to the customer "
"with the coupon code."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:131
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:0
msgid "View of an email draft window with coupon code."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:140
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:145
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of the smart buttons on a ticket focusing on the coupon button."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:154
msgid "`Coupons <https://www.youtube.com/watch?v=KW5cZHg10jQ>`_"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:155
msgid ":doc:`../../../sales/sales/products_prices/loyalty_discount`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:160
msgid "Facilitate a product return with a reverse transfer"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:162
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of a Helpdesk ticket with the return button highlighted."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:171
msgid ""
"The :guilabel:`Return` button **only** appears on a ticket if the customer "
"has a recorded delivery in the database."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:174
msgid ""
"Select a :guilabel:`Sales Order` or :guilabel:`Delivery to Return` to "
"identify the products that need to be returned."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:177
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:181
msgid ""
"Select a :guilabel:`Return Location` where the items should be directed "
"after the return is completed."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of a reverse transfer creation page."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:188
msgid ""
"Click :guilabel:`Return` to confirm the return. This generates a new "
"warehouse operation for the incoming returned products."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:191
msgid ""
"Use the breadcrumbs to return to the helpdesk ticket. A new "
":guilabel:`Return` smart button can now be accessed at the top of the "
"ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of the return smart button on a helpdesk ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:199
msgid ":doc:`../../../sales/sales/products_prices/returns`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:204
msgid "Send products for repair from a ticket"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:206
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:209
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of a repair reference page."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:218
msgid ""
":guilabel:`Customer`: this field carries over from the ticket, though a new "
"contact can been selected from the drop-down menu."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:220
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:223
msgid ""
":guilabel:`Lot/Serial`: this field is **only** visible if the products being"
" repaired are tracked, via lot or serial numbers."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:225
msgid ""
":guilabel:`Return`: return order from which the product to be repaired comes"
" from."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:226
msgid ""
":guilabel:`Under Warranty`: if this box is checked, the sale price for all "
"products from the repair order are set to zero."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:228
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:230
msgid ""
":guilabel:`Responsible`: assign a user from the drop-down menu to manage the"
" repair."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:231
msgid ""
":guilabel:`Tags`: click into this field to assign an existing tag or create "
"a new one. Multiple tags can be assigned."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:234
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:237
msgid ""
"Once the form is complete, click :guilabel:`Confirm Repair`. To create, "
"edit, and send a quote for this repair, click :guilabel:`Create Quotation`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:240
msgid ""
"A :guilabel:`Repairs` smart button is then added to the ticket, linking to "
"the repair order."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of smart buttons focusing on repair button."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:247
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:254
msgid "Create field service task from a ticket"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:256
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:261
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:265
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of a Field Service task creation page."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:272
msgid "Confirm or update the task :guilabel:`Title`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:274
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:278
msgid ""
"If applicable, select a :guilabel:`Worksheet Template` from the drop-down "
"menu."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:281
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:285
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:290
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:293
msgid "Click :guilabel:`Create Task` or :guilabel:`Create & View Task`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:295
msgid ""
"After the task is created, a :guilabel:`Tasks` smart button is added to the "
"ticket, linking the :guilabel:`Field Service` task to the ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1
msgid "View of ticket smart buttons focused on task."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:303
msgid ""
"`Field Service  <https://www.odoo.com/slides/slide/advanced-"
"settings-862?fullscreen=1>`_"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
msgid "Closing tickets"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12
msgid "Manually close solved tickets"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
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*."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
msgid ""
"View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage"
" option."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
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*."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
msgid "Stage settings page."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41
msgid "Automatically close inactive tickets"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43
msgid ""
"Tickets that are inactive for a set period of time can be automatically "
"closed. At that point, they will be moved to a folded stage."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54
msgid ""
"The :guilabel:`After days of inactivity` field defaults to `7`, but can be "
"adjusted if necessary."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60
msgid ""
"If only certain stages should be used to track days of inactivity, they can "
"be added to the :guilabel:`In Stages` field."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64
msgid "A team's pipeline is created with the following stages:"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66
msgid "`New`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67
msgid "`In Progress`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68
msgid "`Customer Feedback`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69
msgid "`Closed`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
msgid ""
"Therefore, the :guilabel:`Automatic Closing` settings would be configured as"
" below\\:\\"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
msgid ":guilabel:`Automatic Closing`: *checked*"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
msgid ":guilabel:`Move to Stage`: `Solved`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
msgid ":guilabel:`In Stages`: `Customer Feedback`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
msgid "Example of Automatic Closing settings."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89
msgid "Allow customers to close their own tickets"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
msgid "Customer closing setting in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
msgid "Customer view of ticket closing in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
msgid ""
"Customers with access to the portal will be able to view their tickets under"
" :menuselection:`My Account --> Tickets`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:3
msgid "Track and bill time"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:5
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:11
msgid ""
"Since the *Track & Bill Time* features require integration with other "
"applications, enabling them may result in the installation of additional "
"modules or applications."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:14
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:19
msgid "Configure track and bill time features"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:21
msgid ""
"Before a customer can be invoiced for support services, the *Track & Bill "
"Time* features **must** be enabled on each *Helpdesk* team individually."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:25
msgid "Enable track and bill time on a helpdesk team"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:27
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:31
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:34
msgid ""
"Once the :guilabel:`Timesheets` box is checked, a new field appears, labeled"
" :guilabel:`Project`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:37
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:40
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:43
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1
msgid ""
"View of a helpdesk team settings page emphasizing the track and bill time "
"settings."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:54
msgid "Configure service products"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:56
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:62
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1
msgid ""
"View of a service product with the invoicing policy set to 'Based on "
"timesheets'."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:71
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:74
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:77
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1
msgid ""
"View of a service product with the invoicing policy set to 'prepaid/fixed'."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:86
msgid ""
"Finally, set the :guilabel:`Sales Price`, and confirm that the "
":guilabel:`Unit of Measure` is set to :guilabel:`Hours`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:90
msgid "Invoice prepaid support services"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:92
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>`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:98
msgid "Create a sales order with prepaid product"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:100
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:104
msgid "Then, fill out the quotation form with the customer information."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:106
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:110
msgid ""
"After updating any other necessary information, :guilabel:`Confirm` the "
"quotation. This converts the quotation into an :abbr:`SO (sales order)`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:114
msgid "Create and send an invoice for prepaid services"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:116
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:119
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)`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:124
msgid ""
"When the necessary information has been entered, click :guilabel:`Create "
"Draft Invoice`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:126
msgid "The invoice can then be sent to the customer for payment."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:129
msgid "Create helpdesk ticket for prepaid services"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:131
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:135
msgid ""
"On the blank ticket form, create a ticket :guilabel:`Title`, and enter the "
":guilabel:`Customer` information."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:138
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:142
msgid "Track hours on helpdesk ticket"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:144
msgid ""
"Time spent working on a *Helpdesk* ticket is tracked on the *Timesheets* tab"
" on the specific ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:146
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:150
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1
msgid ""
"View of the timesheets tab on a ticket with an emphasis on the remaining "
"hours on an SO."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:158
msgid ""
"If the number of hours on the :guilabel:`Timesheets` tab exceeds the number "
"of hours sold, the :guilabel:`Remaining Hours of SO` turns red."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:161
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:165
msgid "Invoice post-paid support services"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:167
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>`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:174
msgid "Create a sales order with a time-tracked product"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:176
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:180
msgid "Fill out the quotation with the customer information."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:182
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:187
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:192
msgid "Create a helpdesk ticket for time-tracked services"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:194
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:197
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:202
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:206
msgid "Track support hours on a ticket"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:208
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:212
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:215
msgid ""
"Repeat these steps as needed until all time spent on the issues has been "
"recorded."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1
msgid "View of the timesheets tab on a helpdesk ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:222
msgid "Create an invoice for hours tracked on a ticket"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:224
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:227
msgid ""
"To do this, return to the :abbr:`SO (sales order)` by clicking on the "
":guilabel:`Sales Order` smart button at the top of the ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:230
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1
msgid "View of a sales order with emphasis on the delivered column."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:237
msgid ""
"Then, click :guilabel:`Create Invoice`. This opens a :guilabel:`Create "
"invoice(s)` pop-up window."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:239
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)`."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:244
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1
msgid "View of create invoices pop up showing timesheets period fields."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:252
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."
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:256
msgid ""
":doc:`../../../inventory_and_mrp/inventory/product_management/configure/uom`"
msgstr ""

#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:257
msgid ":doc:`../../../sales/sales/invoicing/down_payment`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview.rst:5
#: ../../content/applications/services/timesheets/overview.rst:5
msgid "Overview"
msgstr "Przegląd"

#: ../../content/applications/services/helpdesk/overview/help_center.rst:3
msgid "Help Center"
msgstr "Centrum Pomocy"

#: ../../content/applications/services/helpdesk/overview/help_center.rst:7
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst-1
msgid ""
"Overview of the settings page of a team emphasizing the Help Center "
"features."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:17
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:22
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:27
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:30
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:35
msgid ":doc:`Helpdesk Overview <../../helpdesk>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:38
msgid "Knowledge"
msgstr "Wiedza"

#: ../../content/applications/services/helpdesk/overview/help_center.rst:40
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:45
msgid ""
"The **Knowledge** app is accessible throughout the database by clicking on "
"the :guilabel:`Knowledge (bookmark)` icon."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:51
msgid "View of a message in Helpdesk focusing on the Knowledge bookmark icon."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:51
msgid "The Knowledge app is represented by the bookmark icon."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:54
msgid "Enable Knowledge on a Helpdesk team"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:56
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>`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:59
msgid ""
"When a team has been selected or created, Odoo displays that team's detail "
"form."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:61
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:65
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:70
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|."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:74
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:78
msgid ""
"Once an article has been created and assigned to a **Helpdesk** team, "
"content can be added and organized through the **Knowledge** app."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:82
msgid ""
":doc:`Editing Knowledge articles "
"<../../../productivity/knowledge/articles_editing>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:85
msgid "Search articles from a Helpdesk ticket"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:87
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:90
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:94
msgid "When a ticket is selected, Odoo reveals that ticket's detail form."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:96
msgid ""
"Click the :guilabel:`Knowledge (bookmark)` icon, located at the top-right of"
" the page, to open a pop-up search window."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst-1
msgid "View of knowledge search window from a helpdesk ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:103
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:106
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:109
msgid "To open the article in a new tab, press :command:`Ctrl + Enter`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:112
msgid ""
"If a more in-depth search is required, press :command:`Alt + B`. That "
"reveals a separate page, in which a more detailed search can occur."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:116
msgid "Share an article to the Help Center"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:118
msgid ""
"To make a **Knowledge** article available to customers and website visitors,"
" it **must** be published."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:122
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:126
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst-1
msgid "View of a knowledge article focused on sharing and publishing options."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:134
msgid "Solve tickets with a clipboard box"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:136
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:141
msgid "Add clipboard boxes to articles"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:143
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*."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:146
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst-1
msgid "View of a clipboard in knowledge with focus on send and copy options."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:154
msgid ""
"Clipboard boxes only display the :guilabel:`Use as description` or "
":guilabel:`Send as Message` options if they are accessed directly from the "
"**Helpdesk**."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:158
msgid "Use clipboard boxes in tickets"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:160
msgid ""
"Clipboard boxes can be used to respond directly to a **Helpdesk** ticket as "
"a message, or to add information to the ticket's description."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:163
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:167
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:171
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:174
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:178
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:186
msgid "Community Forum"
msgstr "Forum społeczności"

#: ../../content/applications/services/helpdesk/overview/help_center.rst:188
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:193
msgid "Enable forums on a Helpdesk team"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:195
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>`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:199
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:202
msgid ""
"When activated, a new field labeled :guilabel:`Forums` appears beneath."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:204
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:209
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:213
msgid ":doc:`Forum documentation <../../../websites/forum>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:216
msgid "Create a forum post from a Helpdesk ticket"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:218
msgid ""
"When a **Helpdesk** team has a *Forum* enabled, tickets submitted to that "
"team can be converted to forum posts."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:221
msgid ""
"To do that, select a ticket, either from a team's pipeline or from "
":menuselection:`Tickets --> All Tickets` in the :guilabel:`Helpdesk` "
"application."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:224
msgid ""
"At the top of the ticket detail form, click the :guilabel:`Share on Forum` "
"button."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst-1
msgid ""
"Overview of the Forums page of a website to show the available ones in Odoo "
"Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:229
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:232
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:237
msgid "Create a Helpdesk ticket from a forum post"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:239
msgid ""
"Forum posts submitted by portal users can be converted to **Helpdesk** "
"tickets."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:241
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst-1
msgid "A forum post with the create ticket option visible."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:247
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:250
msgid "Click :guilabel:`Create & View Ticket` or :guilabel:`Create Ticket`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:253
msgid "The original forum post is linked in the chatter on the new ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:256
msgid "eLearning"
msgstr "eNauka"

#: ../../content/applications/services/helpdesk/overview/help_center.rst:258
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:264
msgid "Enable eLearning courses on a Helpdesk team"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:266
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>`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:269
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:272
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:278
msgid "Create an eLearning course"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:280
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:283
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:287
msgid ""
"On the course template page, add a :guilabel:`Course Title`, and below that,"
" :guilabel:`Tags`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:289
msgid "Click on the :guilabel:`Options` tab."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:291
msgid ""
"Under :guilabel:`Access Rights`, select which users are able to view and "
"enroll in the course."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:293
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:296
msgid ""
"Under :guilabel:`Display`, choose the preferred course :guilabel:`Type`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:299
msgid "Add content to an eLearning course"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:301
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst-1
msgid "View of a course being published for Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:310
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:315
msgid ""
"`Odoo Tutorials: eLearning <https://www.odoo.com/slides/elearning-56>`_"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:318
msgid "Publish an eLearning course"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:320
msgid ""
"To allow customers to enroll in a course, both the course and the contents "
"**must** be published."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:323
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:328
msgid ""
"To make the entire course available at once, each piece of course content "
"must be published first, then the course can be published."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:331
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:334
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:338
msgid "Publish eLearning course contents from the back-end"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:340
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:343
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:347
msgid ""
"Click the :icon:`oi-view-list` :guilabel:`(list)` icon to switch to list "
"view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:349
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst:353
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/help_center.rst-1
msgid "View of a course contents being published in Odoo Helpdesk back-end."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:3
msgid "Customer ratings"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:5
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:12
msgid "Enable customer ratings on Helpdesk teams"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:14
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst-1
msgid ""
"Overview of the settings page of a helpdesk team emphasizing the rating on ticket feature\n"
"in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:25
msgid "Set a ratings request email template on a stage"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:27
msgid ""
"To automatically request ratings from customers once their tickets have "
"closed, an email template should be added to the appropriate stage."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:30
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:35
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:39
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:43
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:46
msgid "*Green smiling face* - Satisfied"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:47
msgid "*Yellow neutral face* - Okay"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:48
msgid "*Red frowning face* - Dissatisfied"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:50
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:55
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:59
msgid ":doc:`../../../general/companies/email_template`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:62
msgid "Publish ratings on the customer portal"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:64
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:70
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:77
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:81
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst-1
#: ../../content/applications/services/helpdesk/overview/ratings.rst-1
msgid "View of the ratings performance overview from the customer portal."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:90
msgid ":doc:`Portal access <../../../general/users/portal>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:93
msgid "Manually hide individual ratings"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:95
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:98
msgid ""
"To make a rating visible only to internal users, navigate to the page for a "
"rating. This can be done in one of the following ways:"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:101
msgid ""
"Go to :menuselection:`Helpdesk app --> Reporting --> Customer Ratings` and "
"click on one of the Kanban cards for an individual rating."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:103
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:108
msgid ""
"Once on the rating details page, check the :guilabel:`Visible Internally "
"Only` box."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:115
msgid ":doc:`../advanced/close_tickets`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/ratings.rst:116
msgid ":doc:`reports`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:3
msgid "Receiving tickets"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:5
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:11
msgid "Enable channel options to submit tickets"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:13
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>`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:16
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:19
msgid ":ref:`Email Alias <helpdesk/receiving_tickets/email-alias>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:20
msgid ":ref:`Live Chat <helpdesk/receiving_tickets/live-chat>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:21
msgid ":ref:`Website Form <helpdesk/receiving_tickets/website-form>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:26
msgid "Email Alias"
msgstr "Alias e-mail"

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:28
msgid ""
"The *Email Alias* setting creates tickets from messages sent to that team's "
"specified email alias."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:31
msgid ""
"The following steps are for **Odoo Online** and **Odoo.sh** databases. For "
"**On-premise** databases, external servers are required for email aliases."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:34
msgid ""
"When a new **Helpdesk** team is created, an email alias is created for it. "
"This alias can be changed on the team's settings page."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:37
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:40
msgid ""
"Then, scroll to :menuselection:`Channels --> Email Alias`. In the "
":guilabel:`Alias` field, type the desired name for the team's email alias."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1
msgid ""
"View of the settings page of a Helpdesk team emphasizing the email alias feature in Odoo\n"
"Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:48
msgid ""
"Custom email domains are **not** required in order to use an email alias, "
"however, they can be configured through the **Settings** app."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:51
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:55
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:62
msgid "Live Chat"
msgstr "Czat na żywo"

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:64
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:68
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:73
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:77
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:82
msgid "Live Chat channel configuration"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:84
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:88
msgid ""
"If a **Helpdesk** team is named `Customer Care`, a **Live Chat** channel is "
"created called `Customer Care`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:0
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1
msgid "View of the Kanban cards for the available Live Chat channels."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:94
msgid "On the channel form, navigate through the tabs to complete the setup."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:97
msgid "Operators tab"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:99
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:102
msgid ""
"To add additional users, click on the :guilabel:`Operators` tab, then click "
":guilabel:`Add`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:104
msgid ""
"Click the checkbox next to the users to be added on the :guilabel:`Add: "
"Operators` pop-up window that appears, then click :guilabel:`Select`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:107
msgid "Click :guilabel:`New` to create new operators, if needed."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:109
msgid ""
"When the desired addition is complete, click :guilabel:`Save & Close`, or "
":guilabel:`Save & New` to add multiple new operators."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:113
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:118
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:123
msgid ""
"Users can add themselves as an operator by clicking the :guilabel:`Join "
"Channel` button on a **Live Chat** channel."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:0
msgid ""
"View of a live chat channel Kanban card with the join button emphasized."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:130
msgid "Options tab"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:132
msgid ""
"The :guilabel:`Options` tab contains the visual and text settings for the "
"live chat window."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1
msgid "View of the options tab of a Live Chat channel's settings."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:137
msgid ""
":guilabel:`Notification Text`: This field updates the greeting displayed in "
"the text bubble when the live chat button appears on the website."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:140
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:146
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:177
msgid ":guilabel:`Show`: The chat button displays on the selected page."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:147
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:179
msgid ""
":guilabel:`Show with notification`: The chat button is displayed, with the "
"addition of the :guilabel:`Notification text` from the :guilabel:`Options` "
"tab."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:149
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:182
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:152
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:186
msgid ""
":guilabel:`Hide`: The chat button is hidden from display on the webpage."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:155
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:159
msgid "Channel Rules tab"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:161
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)."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:165
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:169
msgid ""
"Edit existing rules by selecting them from the :guilabel:`Channel Rules` "
"tab, or create a new rule by clicking :guilabel:`Add a line`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:172
msgid ""
"Then, proceed to configure the details for how the rule should apply on the "
"pop-up form that appears."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:175
msgid "Choose how the *Live Chat Button* displays on the webpage."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:188
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:193
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*."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:197
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:201
msgid ""
"To create more steps in the script, click :guilabel:`Add a line`, and fill "
"out the script steps form, according to the desired logic."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:204
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:207
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:215
msgid "Widget tab"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:217
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:221
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:226
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:229
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:233
msgid "Create a support ticket from a live chat session"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:235
msgid ""
"Operators who have joined a live chat channel are able to communicate with "
"site visitors in real-time."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:238
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:244
msgid ""
"**Helpdesk** tickets can also be created through the :doc:`WhatsApp "
"</applications/productivity/whatsapp>` app using the same `/ticket` command."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:250
msgid "Website Form"
msgstr "Formularz na stronie"

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:252
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:255
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:258
msgid ""
"Then, locate the :guilabel:`Website Form` feature, under the :guilabel:`Help"
" Center` section, and check the box."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:264
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:269
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:272
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1
msgid ""
"View of the settings page of a helpdesk team emphasizing the Go to Website button in\n"
"Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:281
msgid "Website ticket form customization"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:283
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:287
msgid ""
"To add a new field, go to the :guilabel:`Field` section of the sidebar, and "
"click :guilabel:`+ Field`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:290
msgid ""
"Click the :guilabel:`🗑️ (trash can)` icon to delete the field, if necessary."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:292
msgid "Edit the other options for the new field in the sidebar, as desired:"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:294
msgid ""
":guilabel:`Type`: matches an Odoo model value to the field (e.g. `Customer "
"Name`)."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:295
msgid ""
":guilabel:`Input Type`: determine what type of input the field should be, "
"like `Text`, `Email`, `Telephone`, or `URL`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:297
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:299
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:301
msgid ":guilabel:`Placeholder`: add a sample input value."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:302
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:305
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:307
msgid ""
":guilabel:`Visibility`: allow for absolute or conditional visibility of the "
"field. Nested options, such as, device visibility, appear when certain "
"options are selected."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:309
msgid ""
":guilabel:`Animation`: choose whether or not the field should include "
"animation."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1
msgid ""
"View of the unpublished website form to submit a ticket for Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:315
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:320
msgid "Prioritizing tickets"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:322
msgid ""
"All tickets include a :guilabel:`Priority` field. The highest priority "
"tickets appear at the top of the Kanban and list views."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1
msgid ""
"View of a team's Kanban view and the prioritized tasks in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:328
msgid "The priority levels are represented by stars:"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:330
msgid "0 stars = *Low Priority*"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:331
msgid "1 star = *Medium Priority*"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:332
msgid "2 stars = *High Priority*"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:333
msgid "3 stars = *Urgent*"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:335
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:339
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:343
msgid ":doc:`/applications/services/helpdesk/advanced/close_tickets`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:344
msgid ":doc:`../../../general/email_communication`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:345
msgid ":doc:`/applications/websites/livechat`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:3
msgid "Reporting"
msgstr "Raportowanie"

#: ../../content/applications/services/helpdesk/overview/reports.rst:8
msgid ""
"Reports in Odoo *Helpdesk* provide the opportunity to manage employee "
"workloads, identify areas for improvement, and confirm if customer "
"expectations are being met."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:12
msgid "Available reports"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:14
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:19
msgid "Tickets Analysis"
msgstr "Analiza zgłoszeń"

#: ../../content/applications/services/helpdesk/overview/reports.rst:21
msgid ""
"The *Tickets Analysis* report (:menuselection:`Helpdesk app --> Reporting "
"--> Tickets Analysis`) provides an overview of every customer support ticket"
" in the database."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:24
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of Ticket Analysis report default view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:32
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:"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:37
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.*"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:40
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.**"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:43
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.*"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:46
msgid ""
":guilabel:`Hours to Assign`: number of working hours between the date the "
"ticket was created and when it was assigned to a team member."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:48
msgid ""
":guilabel:`Hours to Close`: number of working hours between the date the "
"ticket was created and the date it was closed."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:50
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.*"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:53
msgid ""
":guilabel:`Hours until SLA Deadline`: number of working hours remaining to "
"reach the last |SLA| deadline on a ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:55
msgid ""
":guilabel:`Rating (/5)`: number out of five to represent customer feedback "
"(Dissatisfied = 1, Okay/Neutral = 3, Satisfied = 5)."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:57
#: ../../content/applications/services/helpdesk/overview/reports.rst:85
msgid ""
":guilabel:`Remaining Hours on SO`: hours remaining on a linked sales order."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:58
#: ../../content/applications/services/helpdesk/overview/reports.rst:92
msgid ":guilabel:`Count`: number of tickets in total."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:61
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:66
msgid "SLA Status Analysis"
msgstr "Analiza statusu SLA"

#: ../../content/applications/services/helpdesk/overview/reports.rst:68
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:72
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of Group by options of Ticket Analysis report."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:79
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:"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:82
msgid ""
":guilabel:`Number of SLA Failed`: number of tickets that have failed at "
"least one |SLA|."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:83
msgid ""
":guilabel:`Rating (/5)`: number value representing customer feedback "
"(Dissatisfied = 1, Okay/Neutral = 3, Satisfied = 5)."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:86
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:88
msgid ""
":guilabel:`Working Hours to Close`: number of working hours between the date"
" the ticket was created and the date it was closed."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:90
msgid ""
":guilabel:`Working Hours to Reach SLA`: number of working hours between the "
"date the ticket was created and the date the |SLA| was satisfied."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:95
msgid ":doc:`Service Level Agreements (SLA) <sla>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:98
msgid "Customer Ratings"
msgstr "Oceny klienta"

#: ../../content/applications/services/helpdesk/overview/reports.rst:100
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of the Kanban display in the Customer Ratings report."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:108
msgid ""
"Click on an individual rating to see additional details about the rating "
"submitted by the customer, including a link to the original ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of the details of an individual customer rating."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:116
msgid ""
"On the rating's details page, tick the :guilabel:`Visible Internally Only` "
"checkbox to hide the rating from the customer portal."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:119
msgid ""
"The *Customer Ratings* report is displayed in a Kanban view by default, but "
"can also be displayed in graph, list, or pivot view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:123
msgid ":doc:`Ratings <ratings>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:126
msgid "View and filter options"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:128
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:133
msgid ""
"Only one measure may be selected at a time for graphs, but pivot tables can "
"include multiple measures."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:137
#: ../../content/applications/services/helpdesk/overview/sla.rst:135
msgid "Pivot view"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:139
msgid ""
"The *pivot* view presents data in an interactive manner. All three "
"*Helpdesk* reports are available in pivot view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:142
msgid ""
"The pivot view can be accessed on any report by selecting the :icon:`oi-"
"view-pivot` :guilabel:`(pivot)` icon at the top-right of the screen."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
#: ../../content/applications/services/helpdesk/overview/sla.rst:144
msgid "View of the SLA status analysis report in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:149
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:154
#: ../../content/applications/services/helpdesk/overview/sla.rst:164
msgid "Graph view"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:156
msgid ""
"The *graph* view presents data in either a *bar*, *line*, or *pie* chart."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:158
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:164
msgid "Bar chart"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:0
#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of the SLA status analysis report in bar view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:170
msgid "Line chart"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:0
msgid "View of the Customer Ratings report in line view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:176
msgid "Pie chart"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:0
msgid "View of the Ticket analysis report in pie chart view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:183
#: ../../content/applications/services/helpdesk/overview/sla.rst:194
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:189
msgid "Save and share a favorite search"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:191
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:194
msgid ""
"To create and save a new *Favorites* configuration on a report, follow the "
"steps below:"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:196
msgid ""
"Set the necessary parameters using the :guilabel:`Filters`, :guilabel:`Group"
" By` and :guilabel:`Measures` options."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:198
msgid ""
"Click the :icon:`fa-caret-down` :guilabel:`(down)` icon next to the "
":guilabel:`Search...` bar to open the drop-down menu."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:200
msgid ""
"Under the :guilabel:`Favorites` heading, click :guilabel:`Save current "
"search`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:201
msgid "If desired, enter a new name for the report."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:202
msgid ""
"Tick the :guilabel:`Default Filter` checkbox to have these filter settings "
"automatically displayed when the report is opened. Otherwise, leave it "
"blank."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:204
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:207
msgid "Click :guilabel:`Save` to preserve the configuration for future use."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of the save favorites option in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:214
msgid ":doc:`Start receiving tickets <receiving_tickets>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/reports.rst:215
msgid ":doc:`Odoo reporting <../../../essentials/reporting>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:3
msgid "Service level agreements (SLA)"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:8
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:13
msgid ""
"The *SLA Policies* feature is enabled by default on newly created "
"**Helpdesk** teams."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:15
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:18
msgid ""
"From here, scroll to the :guilabel:`Performance` section. To turn off the "
"|SLAs| feature for the team, clear the :guilabel:`SLA Policies` checkbox."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of a team page in Helpdesk focusing on the SLA Policies setting."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:25
msgid "Create a new SLA policy"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:27
msgid ""
"To create a new policy, go to :menuselection:`Helpdesk app --> Configuration"
" --> SLA Policies`, and click :guilabel:`New`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:30
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:34
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:38
msgid "Define the criteria for an SLA policy"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:40
msgid ""
"The :guilabel:`Criteria` section is used to identify which tickets this "
"policy is applied to."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:42
msgid "Fill out the following fields to adjust the selection criteria:"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:45
msgid ""
"Unless otherwise indicated, multiple selections can be made for each field."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:47
msgid ""
":guilabel:`Helpdesk Team`: A policy can only be applied to one team. *This "
"field is required.*"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:48
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:54
msgid ""
":guilabel:`Tags`: Tags are used to indicate what the ticket is about. "
"Multiple tags can be applied to a single ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:56
msgid ""
":guilabel:`Customers`: Individual contacts or companies may be selected in "
"this field."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:57
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:62
msgid ""
"A support team needs to address urgent issues for VIP customers within one "
"business day."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:64
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:68
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid ""
"View of a new SLA policy record with all the relevant information entered."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:75
msgid "Establish a target for an SLA policy"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:77
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:81
msgid ""
"Time spent in stages selected in the :guilabel:`Excluding Stages` field are "
"**not** included in the calculation of the |SLA| deadline."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:85
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:91
msgid "Meet SLA deadlines"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:93
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:98
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:102
msgid ""
"The deadline is then added to the ticket, as well as a tag indicating the "
"name of the |SLAs| applied."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid ""
"View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo"
" Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:108
msgid ""
"When a ticket satisfies an |SLA| policy, the |SLA| tag turns green, and the "
"deadline disappears from view on the ticket."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:115
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:118
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid ""
"View of a ticket's form with a failing and passing SLA in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:128
msgid "Analyze SLA performance"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:130
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:137
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:144
msgid ""
"The pivot view aggregates data, which can be manipulated by adding measures "
"and filters."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:146
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:149
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of the available measures in the SLA status analysis report."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:156
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid ""
"View of the available group by options in the SLA status analysis report."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:166
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:172
msgid "Bar Chart"
msgstr "Wykres słupkowy"

#: ../../content/applications/services/helpdesk/overview/sla.rst:177
msgid ""
"A bar chart can deal with larger data sets and compare data across several "
"categories."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:179
msgid "Line Chart"
msgstr "Wykres liniowy"

#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of the SLA status analysis report in line view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:184
msgid "A line chart can visualize data trends or changes over time."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:186
msgid "Pie Chart"
msgstr "Wykres kołowy"

#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of the SLA status analysis report in pie chart view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:191
msgid "A pie chart compares data among a small number of categories."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of the SLA status analysis report in bar view, stacked."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:203
msgid "Cohort view"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:205
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:212
msgid "View of the SLA status analysis report in cohort view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:212
msgid "The cohort view examines the life cycle of data over time."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:215
msgid ":ref:`Reporting views <reporting/views>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/sla.rst:216
msgid ""
":doc:`Allow customers to close their tickets "
"</applications/services/helpdesk/advanced/close_tickets>`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:3
msgid "Stages"
msgstr "Etapy"

#: ../../content/applications/services/helpdesk/overview/stages.rst:5
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:9
msgid "Create or modify stages"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:12
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`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:16
msgid ""
"To view or modify **Helpdesk** stages, go to :menuselection:`Helpdesk app "
"--> Configuration --> Stages`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:19
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:22
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst-1
msgid ""
"View of the stage list page emphasizing the buttons used to change the order the stages\n"
"appear in the list."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:30
msgid ""
"Change the stage order on the Kanban view of a **Helpdesk** team's pipeline "
"by dragging and dropping individual columns."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:33
msgid ""
"To create a new stage, click the :guilabel:`New` button at the top-left of "
"the stage list. Doing so reveals a blank stage form."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:36
msgid "Choose a :guilabel:`Name` for the new stage."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst-1
msgid "View of a stage's settings page in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:42
msgid "Add email and SMS templates to stages"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:44
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:49
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:53
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:57
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:61
msgid ""
"Follow the same steps to select, edit, or create an :guilabel:`SMS "
"Template`."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst-1
msgid "View of an SMS template setup page in Odoo Helpdesk."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:67
msgid ":doc:`/applications/general/companies/email_template`"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:70
msgid "Fold a stage"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:72
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`)."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:76
msgid ""
"Tickets in an unfolded stage are visible in the pipeline under the stage "
"name, and are considered *open*."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:79
msgid ""
"Stages can be configured to be folded in the Kanban view of a tickets page."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:81
msgid ""
"The name of the folded stages are still visible, but the tickets in the "
"stage are hidden from view."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:83
msgid ""
"To fold a stage, tick the :guilabel:`Folded in Kanban` checkbox on the "
":guilabel:`Stages` form."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:86
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:91
msgid "Temporarily fold a stage"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:93
msgid ""
"Stages can be temporarily folded in the Kanban view of the tickets pipeline,"
" as well."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:95
msgid ""
"View a specific team's pipeline by navigating to :menuselection:`Helpdesk "
"app`, and clicking the team's Kanban card."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:98
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."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst-1
msgid ""
"Kanban view of a Helpdesk stage, with the temporary fold option emphasized."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:105
msgid ""
"Manually folding a stage from the Kanban view is temporary and does **not** "
"close the tickets in the stage."
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:109
msgid "Assign stages to a team"
msgstr ""

#: ../../content/applications/services/helpdesk/overview/stages.rst:111
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."
msgstr ""

#: ../../content/applications/services/planning.rst:5
msgid "Planning"
msgstr "Planowanie"

#: ../../content/applications/services/planning.rst:7
msgid ""
"**Odoo Planning** allows you to plan your team's schedule and manage shifts "
"and resources."
msgstr ""

#: ../../content/applications/services/planning.rst:9
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:"
msgstr ""

#: ../../content/applications/services/planning.rst:12
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."
msgstr ""

#: ../../content/applications/services/planning.rst:16
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."
msgstr ""

#: ../../content/applications/services/planning.rst:19
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."
msgstr ""

#: ../../content/applications/services/planning.rst:24
msgid "`Odoo tutorials: Planning <https://www.odoo.com/slides/planning-60>`_"
msgstr ""

#: ../../content/applications/services/planning.rst:34
msgid "Roles"
msgstr "Role"

#: ../../content/applications/services/planning.rst:36
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>`."
msgstr ""

#: ../../content/applications/services/planning.rst:43
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."
msgstr ""

#: ../../content/applications/services/planning.rst:46
msgid ""
"Roles are taken into account when using the :ref:`Auto Plan feature "
"<planning/open-shifts>`."
msgstr ""

#: ../../content/applications/services/planning.rst:49
msgid "Property fields and roles"
msgstr ""

#: ../../content/applications/services/planning.rst:51
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."
msgstr ""

#: ../../content/applications/services/planning.rst:54
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."
msgstr ""

#: ../../content/applications/services/planning.rst-1
msgid "Creating a new property field in Planning."
msgstr ""

#: ../../content/applications/services/planning.rst:62
msgid ""
"The property field is linked to the role and is included in the shift form "
"of all shifts performed by this role."
msgstr ""

#: ../../content/applications/services/planning.rst:66
msgid "Some of the use cases of role property fields include:"
msgstr ""

#: ../../content/applications/services/planning.rst:68
msgid ""
"**Accreditation**: for roles that require a specific permit (e.g., driving "
"license)"
msgstr ""

#: ../../content/applications/services/planning.rst:69
msgid ""
"**Location**: in companies that operate in multiple locations (e.g., shops "
"or restaurants)"
msgstr ""

#: ../../content/applications/services/planning.rst:70
msgid ""
"**Language**: in a multi-lingual environment (e.g., consulting company)"
msgstr ""

#: ../../content/applications/services/planning.rst:75
msgid "Employees"
msgstr "Pracownicy"

#: ../../content/applications/services/planning.rst:77
msgid "All employees can be included in the planning and assigned shifts."
msgstr ""

#: ../../content/applications/services/planning.rst:79
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."
msgstr ""

#: ../../content/applications/services/planning.rst-1
msgid "Employee profile and the work information tab."
msgstr ""

#: ../../content/applications/services/planning.rst:87
msgid ""
"You can do the same from the **Employees** app, which is installed by "
"default along with Planning."
msgstr ""

#: ../../content/applications/services/planning.rst:90
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`."
msgstr ""

#: ../../content/applications/services/planning.rst:94
msgid "Working hours"
msgstr ""

#: ../../content/applications/services/planning.rst:96
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."
msgstr ""

#: ../../content/applications/services/planning.rst:100
msgid ""
"To create individual :guilabel:`Working Hours`, for example, for employees "
"working part-time, click :guilabel:`Search more...`, then :guilabel:`New`."
msgstr ""

#: ../../content/applications/services/planning.rst:104
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."
msgstr ""

#: ../../content/applications/services/planning.rst:108
msgid ""
":ref:`Payroll documentation on working schedules <payroll/working-times>`"
msgstr ""

#: ../../content/applications/services/planning.rst:111
msgid "Planning roles"
msgstr ""

#: ../../content/applications/services/planning.rst:113
msgid "Once an employee has one or more :guilabel:`Roles`:"
msgstr ""

#: ../../content/applications/services/planning.rst:115
msgid ""
"When creating a shift for this employee, only the shift templates from the "
"roles chosen in this field are displayed."
msgstr ""

#: ../../content/applications/services/planning.rst:117
msgid ""
"When a schedule is published, the employee is only notified of open shifts "
"for the roles that are assigned to them."
msgstr ""

#: ../../content/applications/services/planning.rst:119
msgid ""
"When auto-assigning open shifts or planning sales orders, the employee is "
"only assigned shifts for the roles assigned to them."
msgstr ""

#: ../../content/applications/services/planning.rst:122
msgid "Additionally, when a :guilabel:`Default role` is defined:"
msgstr ""

#: ../../content/applications/services/planning.rst:124
msgid ""
"When creating a shift for the employee, the default role is automatically "
"selected."
msgstr ""

#: ../../content/applications/services/planning.rst:125
msgid ""
"This role also has precedence over the other roles of the employee when "
"auto-assigning open shifts or planning sales orders."
msgstr ""

#: ../../content/applications/services/planning.rst:129
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."
msgstr ""

#: ../../content/applications/services/planning.rst:136
msgid "Materials"
msgstr "Materiały"

#: ../../content/applications/services/planning.rst:138
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)."
msgstr ""

#: ../../content/applications/services/planning.rst:142
msgid ""
"Similarly to employees, materials can be assigned roles and working time."
msgstr ""

#: ../../content/applications/services/planning.rst:147
msgid "Shift templates"
msgstr ""

#: ../../content/applications/services/planning.rst:149
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`."
msgstr ""

#: ../../content/applications/services/planning.rst-1
msgid "Shift form with the option `save template` ticked."
msgstr ""

#: ../../content/applications/services/planning.rst:156
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."
msgstr ""

#: ../../content/applications/services/planning.rst:162
msgid ""
"The employee's working hours are Monday to Friday, 8 am to 5 pm, with a "
"break between 12 and 1 pm."
msgstr ""

#: ../../content/applications/services/planning.rst:165
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."
msgstr ""

#: ../../content/applications/services/planning.rst:167
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."
msgstr ""

#: ../../content/applications/services/planning.rst:171
msgid "Additionally, for each shift template, you can also configure:"
msgstr ""

#: ../../content/applications/services/planning.rst:173
msgid ":guilabel:`Role`: to link the shift to this specific role."
msgstr ""

#: ../../content/applications/services/planning.rst:174
msgid ""
":guilabel:`Project`: to keep track of shifts that are dedicated to work on a"
" project."
msgstr ""

#: ../../content/applications/services/planning.rst:179
msgid "Planning shifts"
msgstr ""

#: ../../content/applications/services/planning.rst:181
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."
msgstr ""

#: ../../content/applications/services/planning.rst:186
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."
msgstr ""

#: ../../content/applications/services/planning.rst-1
msgid "A schedule displaying various visual elements."
msgstr ""

#: ../../content/applications/services/planning.rst:192
msgid "The following visual elements are used on the shifts in the schedules:"
msgstr ""

#: ../../content/applications/services/planning.rst:194
msgid "**Full color**: shifts that are planned and published."
msgstr ""

#: ../../content/applications/services/planning.rst:195
msgid ""
"**Diagonal stripes**: shifts that are planned but have yet to be published."
msgstr ""

#: ../../content/applications/services/planning.rst:196
msgid "**Grayed-out background**: employees that are on time off."
msgstr ""

#: ../../content/applications/services/planning.rst:197
msgid ""
"**Progress bar**: currently ongoing shifts with timesheets linked to them."
msgstr ""

#: ../../content/applications/services/planning.rst:198
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."
msgstr ""

#: ../../content/applications/services/planning.rst:205
msgid "Create a shift"
msgstr ""

#: ../../content/applications/services/planning.rst:207
msgid ""
"To create a shift, go to any schedule, then click :guilabel:`New`. In the "
"pop-up window that opens, fill in the following details:"
msgstr ""

#: ../../content/applications/services/planning.rst:210
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."
msgstr ""

#: ../../content/applications/services/planning.rst:213
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>`."
msgstr ""

#: ../../content/applications/services/planning.rst:215
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."
msgstr ""

#: ../../content/applications/services/planning.rst:218
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."
msgstr ""

#: ../../content/applications/services/planning.rst:221
msgid ""
":guilabel:`Sales Order Item`: If the Sales app is installed in your "
"database, this field allows you to link a sales order to the shift."
msgstr ""

#: ../../content/applications/services/planning.rst:223
msgid ""
":guilabel:`Repeat`: Tick the checkbox and configure the :guilabel:`Repeat "
"Every` field according to your needs. The following rules apply to recurring"
" shifts:"
msgstr ""

#: ../../content/applications/services/planning.rst:226
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."
msgstr ""

#: ../../content/applications/services/planning.rst:229
msgid "Recurrences are planned but not published."
msgstr ""

#: ../../content/applications/services/planning.rst:230
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`."
msgstr ""

#: ../../content/applications/services/planning.rst:235
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`."
msgstr ""

#: ../../content/applications/services/planning.rst:238
msgid ""
":guilabel:`Additional note sent to the employee`: Click on the field to add "
"a note."
msgstr ""

#: ../../content/applications/services/planning.rst:239
msgid ""
":guilabel:`Date`: Choose the date and time of your shift. This is the only "
"mandatory field when creating a shift."
msgstr ""

#: ../../content/applications/services/planning.rst:241
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>`."
msgstr ""

#: ../../content/applications/services/planning.rst:244
msgid ""
"Click :guilabel:`Publish & Save` to confirm the shift and send the assigned "
"employee their schedule by email."
msgstr ""

#: ../../content/applications/services/planning.rst:248
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."
msgstr ""

#: ../../content/applications/services/planning.rst:251
msgid ""
"Two kinds of notifications are sent to the employees depending on their "
"account configuration:"
msgstr ""

#: ../../content/applications/services/planning.rst:253
msgid ""
"Employees without user accounts are redirected to a dedicated **Planning "
"portal**."
msgstr ""

#: ../../content/applications/services/planning.rst:254
msgid ""
"Employees with a user account are redirected to the :guilabel:`My Planning` "
"view in the backend view of Odoo."
msgstr ""

#: ../../content/applications/services/planning.rst:260
msgid "Open shifts and auto planning"
msgstr ""

#: ../../content/applications/services/planning.rst:262
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."
msgstr ""

#: ../../content/applications/services/planning.rst:265
msgid "The following features have an impact on auto planning:"
msgstr ""

#: ../../content/applications/services/planning.rst:267
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."
msgstr ""

#: ../../content/applications/services/planning.rst:270
msgid ""
"**Default roles**: The default role assigned to a resource is given priority"
" over the other roles they have assigned to them."
msgstr ""

#: ../../content/applications/services/planning.rst:272
msgid ""
"**Conflicts**: Employees or materials cannot be assigned multiple shifts at "
"the same time."
msgstr ""

#: ../../content/applications/services/planning.rst:273
msgid ""
"**Time off**: The employees’ time off is taken into account, as well as "
"public holidays."
msgstr ""

#: ../../content/applications/services/planning.rst:274
msgid ""
"**Company working hours**: Are taken into account when assigning shifts to "
"employees or materials."
msgstr ""

#: ../../content/applications/services/planning.rst:275
msgid ""
"**Contracts**: Employees without an active contract cannot be assigned "
"shifts."
msgstr ""

#: ../../content/applications/services/planning.rst:277
msgid ""
"Click :guilabel:`Publish` to confirm the schedule and notify the employees "
"of their planning."
msgstr ""

#: ../../content/applications/services/planning.rst:282
msgid "Switching shifts and unassignment"
msgstr ""

#: ../../content/applications/services/planning.rst:284
msgid ""
"Two features are available to allow employees to make changes to their "
"schedule: **switching shifts** and **unassignment**."
msgstr ""

#: ../../content/applications/services/planning.rst:288
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."
msgstr ""

#: ../../content/applications/services/planning.rst:293
msgid "Switching shifts"
msgstr ""

#: ../../content/applications/services/planning.rst:295
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`."
msgstr ""

#: ../../content/applications/services/planning.rst:298
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."
msgstr ""

#: ../../content/applications/services/planning.rst:301
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."
msgstr ""

#: ../../content/applications/services/planning.rst:305
#: ../../content/applications/services/planning.rst:323
msgid "The following rules apply:"
msgstr ""

#: ../../content/applications/services/planning.rst:307
msgid ""
"Only the shifts matching the employee's roles are displayed as available to "
"them."
msgstr ""

#: ../../content/applications/services/planning.rst:308
#: ../../content/applications/services/planning.rst:326
msgid "Switching shifts is only available for shifts that are in the future."
msgstr ""

#: ../../content/applications/services/planning.rst:311
msgid "Unassignment"
msgstr ""

#: ../../content/applications/services/planning.rst:313
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."
msgstr ""

#: ../../content/applications/services/planning.rst:318
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."
msgstr ""

#: ../../content/applications/services/planning.rst:325
msgid ""
"Only the shifts matching the employee's roles are displayed in their "
"schedule."
msgstr ""

#: ../../content/applications/services/project.rst:8
msgid "Project"
msgstr "Projekt"

#: ../../content/applications/services/project.rst:10
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."
msgstr ""

#: ../../content/applications/services/project.rst:14
#: ../../content/applications/services/timesheets.rst:11
msgid ""
"`Odoo Tutorials: Project and Timesheets "
"<https://www.odoo.com/slides/project-and-timesheets-21>`_"
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:3
msgid "Project dashboard"
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:5
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:13
msgid "Using the project dashboard"
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:15
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>`."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:20
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>`."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:27
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:34
msgid "Totals smart buttons"
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:36
msgid ""
"The following smart buttons are displayed on the top right of the project "
"dashboard:"
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:38
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:41
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:44
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:47
msgid ""
":guilabel:`Documents`: number of :doc:`documents "
"<../../productivity/documents>` in the project’s workspace."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:49
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:51
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:54
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:58
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:65
msgid "Milestones"
msgstr "Kamienie milowe"

#: ../../content/applications/services/project/project_dashboard.rst:67
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:72
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>`)."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:79
msgid "Profitability"
msgstr "Rentowność"

#: ../../content/applications/services/project/project_dashboard.rst:81
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>`."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:85
msgid "The profitability report is only displayed for billable projects."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:90
msgid "Budgets"
msgstr "Budżety"

#: ../../content/applications/services/project/project_dashboard.rst:92
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:96
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:102
msgid "Project updates"
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:104
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:109
msgid ""
"To create a new project update, go to the project dashboard, click "
":guilabel:`New`, and fill in the following fields:"
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:112
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:116
msgid ""
":guilabel:`Progress`: Manually input the completion percentage based on the "
"project's progress."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:117
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."
msgstr ""

#: ../../content/applications/services/project/project_dashboard.rst:119
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."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:3
msgid "Project management"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:5
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."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:8
msgid "Did you know?"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:10
msgid ""
"The word **Kanban** comes from Japanese and refers to the \"visual board\" "
"management method."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:13
msgid ""
"`Odoo Tutorials: Kanban Project Management "
"<https://www.odoo.com/slides/slide/kanban-project-management-1664>`_"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:21
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`."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:24
msgid ""
"You can customize your existing **projects** from the dashboard by clicking "
"the drop-down toggle button (:guilabel:`⋮`) on your project's **card**."
msgstr ""

#: ../../content/applications/services/project/project_management.rst-1
msgid "Project card"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:31
msgid "This enables a new menu divided into four parts:"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:33
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`;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:37
msgid ""
":guilabel:`Reporting`: analyze your project's progress and profitability "
"through graphics and statistics;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:39
msgid ""
"**Color**: make a line of color appear on the left side of the card so that "
"your project is more recognizable;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:41
msgid ":guilabel:`Settings`: you can change the following:"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:43
msgid "the :guilabel:`Name` of the project;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:44
msgid "the :guilabel:`Name of the tasks` found under that project;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:45
msgid "the :guilabel:`Customer` for whom the project is intended;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:46
msgid "the :guilabel:`Tags` used for filtering;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:47
msgid "the :guilabel:`Company` responsible for the project;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:48
msgid "the employee designated as :guilabel:`Project Manager`;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:49
msgid "the :guilabel:`Planned Date` of the project;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:50
msgid "the total :guilabel:`Allocated Hours` for that project."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:52
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;"
msgstr ""

#: ../../content/applications/services/project/project_management.rst-1
msgid "Project settings"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:60
msgid ""
"`Odoo Tutorials: Customize projects "
"<https://www.odoo.com/slides/slide/customize-projects-3615?fullscreen=1>`_"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:63
msgid ""
"Further settings are available under the :guilabel:`Settings` tab. Most of "
"them are *only* available depending on the activated apps."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:67
msgid "Scheduling activities"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:69
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."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:77
msgid ""
"If an activity is **already** scheduled, the icon may change to a **phone**,"
" **group of people**, or other."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:83
msgid "Top bar"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:85
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."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:89
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."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:94
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."
msgstr ""

#: ../../content/applications/services/project/project_management.rst-1
msgid "Top bar selection menu"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:101
msgid "Custom top bar buttons"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:103
msgid "You can also create your own buttons to access more specific views:"
msgstr ""

#: ../../content/applications/services/project/project_management.rst:105
msgid "Click an existing top bar button to access the view."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:106
msgid ""
"Customize the view with keywords, filters, and grouping options using the "
"search bar."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:107
msgid ""
"Click the :icon:`fa-sliders` :guilabel:`(sliders)` button in the top bar and"
" select :guilabel:`Save View`."
msgstr ""

#: ../../content/applications/services/project/project_management.rst:109
msgid ""
"Edit the default button name if necessary, then enable :guilabel:`Shared` if"
" you want to share the button with other users."
msgstr ""

#: ../../content/applications/services/project/tasks.rst:5
msgid "Task management"
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:3
msgid "Recurring tasks"
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:5
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."
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:10
msgid ""
"`Odoo Tutorials: Recurring tasks "
"<https://www.odoo.com/slides/slide/recurring-tasks-1946>`_"
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:15
msgid ""
"To enable recurring tasks, go to :menuselection:`Project --> Configuration "
"--> Settings`, then activate :guilabel:`Recurring Tasks`, and press "
":guilabel:`Save`."
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:19
msgid "Set up task recurrence"
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:21
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."
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:25
msgid ""
"A new task in recurrence will be created once the status of the previous "
"task is set to :guilabel:`Done` or :guilabel:`Canceled`."
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:28
msgid ""
"The new task is created on the project dashboard with the following "
"configuration:"
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:30
msgid ""
":guilabel:`Stage`: is set to the first stage of the project dashboard "
"(:guilabel:`New` or equivalent);"
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:32
msgid ""
":guilabel:`Name`, :guilabel:`Description`, :guilabel:`Project`, "
":guilabel:`Assignees`, :guilabel:`Customer`, :guilabel:`Tags`: are copied "
"from the original task;"
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:34
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);"
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:36
msgid ""
":guilabel:`Milestones`, :guilabel:`Timesheets`, :guilabel:`Chatter`, "
":guilabel:`Activities`, :guilabel:`Subtasks`: are **not** copied from the "
"original task."
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:39
msgid ""
"Once a recurrence is configured, a **smart button** on the task displays the"
" total number of existing recurrences."
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:43
msgid "Edit or stop task recurrence"
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:45
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."
msgstr ""

#: ../../content/applications/services/project/tasks/recurring_tasks.rst:48
msgid ""
"**To stop** the recurrence, open the last task in recurrence and press the "
":guilabel:`Recurrent` button next to the :guilabel:`Planned date`."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:3
msgid "Sub-tasks"
msgstr "Podzadania"

#: ../../content/applications/services/project/tasks/sub-tasks.rst:5
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."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:8
msgid ""
"Odoo’s sub-task feature is particularly useful in some of the following "
"cases:"
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:10
msgid "The task workload is too big to handle in one record."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:11
msgid "There’s a clear sequence of steps to follow."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:12
msgid ""
"Some parts of the workload fall under the scope of different projects and/or"
" assignees."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:14
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**."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:18
msgid "Creating sub-tasks"
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:20
msgid "To create a sub-task:"
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:22
msgid "Open the Project app, then go into your desired project."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:23
msgid ""
"Click the task where you want to add the sub-task, then click the "
":guilabel:`Sub-tasks` tab."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:24
msgid "Click :guilabel:`Add a line`, then fill in the :guilabel:`Title`."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:25
msgid ""
"Click the :icon:`fa-cloud-upload` (:guilabel:`save`) icon to save the task "
"manually."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:28
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."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:33
msgid ""
"Once the new sub-task is created, the following changes occur in the parent "
"task:"
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:35
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."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:37
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."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:40
msgid ""
"The :guilabel:`Timesheets` tab includes a breakdown of time spent on the "
"parent task as well as sub-tasks."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:43
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>`."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:48
msgid ""
"A **smart button** allows to navigate back to the :guilabel:`Parent task`."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:49
msgid ""
"The :guilabel:`Sub-tasks` tab allows for further creation of sub-tasks."
msgstr ""

#: ../../content/applications/services/project/tasks/sub-tasks.rst:50
msgid ""
"Selecting a :guilabel:`Project` will trigger this sub-task to be displayed "
"in the Kanban view of the selected project."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:3
msgid "Task creation"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:5
msgid ""
"Tasks in Odoo Project can be created manually or automatically, including "
"from emails or website forms."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:11
msgid ""
"Open the Project app and choose the desired project. Create a new task by "
"doing one of the following:"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:14
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:16
msgid ""
"Pressing the :icon:`fa-plus` (:guilabel:`plus`) button next to the Kanban "
"stage name. This creates a new task in this Kanban stage."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:19
msgid ""
"Fill in the :guilabel:`Task Title` and add one or more "
":guilabel:`Assignees`, then click :guilabel:`Add`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:25
msgid "Task configuration"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:27
msgid ""
"Click the task to open it. The task form includes the following fields that "
"you can fill in:"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:29
msgid ":guilabel:`Task Title`: title of the task."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:30
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:32
msgid ":guilabel:`Project`: the project that this task belongs to."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:33
msgid ""
":guilabel:`Assignees`: the person(s) in charge of handling the work on this "
"task."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:34
msgid ""
":guilabel:`Tags`: custom labels allowing to categorize and filter your "
"tasks."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:35
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:37
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:40
msgid ""
":guilabel:`Allocated Time`: the amount of time that the work on this task is"
" expected to last, tracked by timesheets."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:42
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:47
msgid ""
"You can also create new tasks by switching to the list or Gantt view and "
"clicking :guilabel:`New`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:49
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**)."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:53
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):"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:56
msgid "**30h**: to allocate 30 hours to the task."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:57
msgid "**#tags**: to add tags to the task."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:58
msgid "**@user**: to assign the task to a user."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:59
msgid "**!**: to star the task as high priority."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:61
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:64
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 !"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:0
msgid "Using keyboard shortcuts to create a task in Project."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:74
msgid "Creating tasks from an email alias"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:76
msgid ""
"This feature allows for project tasks to be automatically created once an "
"email is delivered to a designated email address."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:79
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:83
msgid ""
"Fill in the :guilabel:`Create tasks by sending an email to` field as "
"follows:"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:85
msgid ""
"**Section of the alias before the @ symbol**: type the name of the email "
"alias, e.g. `contact`, `help`, `jobs`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:87
msgid ""
"**Domain**: in most cases, this is filled in by default with your "
":doc:`domain <../../../general/email_communication>`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:89
msgid ""
"**Accept Emails From**: refine the senders whose emails will create tasks in"
" the project."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst-1
msgid "View of the email alias chosen on the dashboard view in Odoo Project"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:94
msgid ""
"Once configured, the email alias can be seen under the name of your project "
"on the Kanban dashboard."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:96
msgid ""
"When an email is sent to the alias, the email is automatically converted "
"into a project task. The following rules apply:"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:99
msgid "The email sender is displayed in the :guilabel:`Customer` field."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:100
msgid "The email subject is displayed in the :guilabel:`Task Title` field."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:101
msgid "The email body is displayed in the :guilabel:`Description` field."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:102
msgid ""
"The whole content of the email is additionally displayed in the **chatter**."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:103
msgid ""
"All the recipients of the email (To/Cc/Bcc) that are Odoo users are "
"automatically added as **followers** of the task."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:107
msgid "Creating tasks from a website form"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:109
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:112
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>`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:114
msgid "In the website editor, edit the following fields:"
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:116
msgid ":guilabel:`Action`: select :guilabel:`Create a Task`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:117
msgid ""
":guilabel:`Project`: choose the project that you want the new tasks to be "
"created in."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:119
msgid ":ref:`Customize the form <website/dynamic_content/form>`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:121
msgid ""
"When the form is submitted, it automatically creates a project task. The "
"task's content is defined by the form's corresponding fields."
msgstr ""

#: ../../content/applications/services/project/tasks/task_creation.rst:125
msgid ""
":doc:`Dynamic website content "
"<../../../websites/website/web_design/building_blocks/dynamic_content>`"
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:3
msgid "Task dependencies"
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:5
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:9
msgid ""
"To enable task dependencies in projects, go to :menuselection:`Project --> "
"Configuration --> Settings`, enable :guilabel:`Task Dependencies`, and click"
" :guilabel:`Save`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:13
msgid "Set task dependencies"
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:15
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)."
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:19
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:24
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst-1
msgid "Task dependency"
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:32
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`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:37
msgid "Remove dependencies"
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:39
msgid "To remove a task dependency, proceed as follows:"
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:41
msgid ""
"From the task form, go to the **Blocked by** tab and click the :icon:`fa-"
"times` (:guilabel:`times`) button."
msgstr ""

#: ../../content/applications/services/project/tasks/task_dependencies.rst:43
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:3
msgid "Task stages and statuses"
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:6
msgid "Task stages"
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:8
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:12
msgid ""
"By default, task stages are project-specific but can be shared across "
"multiple projects that follow the same workflow."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:16
msgid "Creating task stages"
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:18
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>`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:22
msgid ""
"To create a stage, type its name into the :guilabel:`Stage...` field, then "
"click :guilabel:`Add`."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:25
msgid ""
"Click :guilabel:`See examples` to find ideas for stage names applicable to "
"your line of business."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:28
msgid "Editing task stages"
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:30
msgid ""
"To edit the task stage, click the :icon:`fa-cog` (:guilabel:`cog`) icon next"
" to its name. From there, click one of the following:"
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:33
msgid ""
":guilabel:`Fold`: to hide the task stage and all of the tasks in this stage "
"from the Kanban view."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:34
msgid ":guilabel:`Edit`:"
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:36
msgid ":guilabel:`Name`: to change the name of the stage."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:37
msgid ""
":guilabel:`SMS/Email Template`: to automatically send an email or SMS "
"notification to the customer when a task reaches this stage."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:39
msgid ""
":guilabel:`Folded in Kanban`: to hide the task stage and all of the tasks in"
" this stage from the Kanban view."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:41
msgid ""
":guilabel:`Projects`: to share this task stage between several projects."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:42
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:47
msgid ":guilabel:`Delete`: to delete this stage."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:48
msgid ""
":guilabel:`Archive/Unarchive all`: to archive or unarchive all of the tasks "
"in this stage."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:53
msgid "Task statuses"
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:55
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:"
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:59
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:61
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:63
msgid ""
":guilabel:`Approved`: to highlight that the task is ready to be moved to the"
" next stage."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:64
msgid ":guilabel:`Canceled`: to cancel the task."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:65
msgid ":guilabel:`Done`: to close the task once it's been completed."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:69
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."
msgstr ""

#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:73
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."
msgstr ""

#: ../../content/applications/services/timesheets.rst:8
msgid "Timesheets"
msgstr "Karty pracy"

#: ../../content/applications/services/timesheets/overview/time_off.rst:3
msgid "Create Timesheets upon Time Off Validation"
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst:5
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."
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst:9
msgid ""
"Activate the :ref:`developer mode <developer-mode>`, go to *Timesheets*, and"
" change the *Project* and *Task* set by default, if you like."
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst-1
msgid ""
"View of Timesheets setting enabling the feature record time off in Odoo "
"Timesheets"
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst:16
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."
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst-1
msgid ""
"View of a time off types form emphasizing the time off requests and timesheets section in\n"
"Odoo Time Off"
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst:26
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."
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst:27
msgid ""
"On the example below, the user requested *Paid Time off* from July 13th to "
"15th."
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst-1
msgid "View of the time off request form in Odoo Time Off"
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst:33
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."
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst-1
msgid ""
"Video of timesheets emphasizing the requested time off from the employee in "
"Odoo Timesheets"
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst:41
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."
msgstr ""

#: ../../content/applications/services/timesheets/overview/time_off.rst-1
msgid "View of the details of a project/task in Odoo Timeheets"
msgstr ""