[I18N] Update translation terms from Transifex

This commit is contained in:
Odoo Translation Bot
2023-04-16 00:40:28 +02:00
parent b00b9b3f2e
commit e12e482f62
47 changed files with 32531 additions and 26455 deletions
+454 -120
View File
@@ -5,17 +5,17 @@
#
# Translators:
# Dragos Vasile, 2023
# Cozmin Candea <office@terrabit.ro>, 2023
# Dorin Hongu <dhongu@gmail.com>, 2023
# Cozmin Candea <office@terrabit.ro>, 2023
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-04-06 08:12+0000\n"
"POT-Creation-Date: 2023-04-13 05:55+0000\n"
"PO-Revision-Date: 2022-10-04 12:54+0000\n"
"Last-Translator: Dorin Hongu <dhongu@gmail.com>, 2023\n"
"Last-Translator: Cozmin Candea <office@terrabit.ro>, 2023\n"
"Language-Team: Romanian (https://app.transifex.com/odoo/teams/41243/ro/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -363,80 +363,215 @@ msgstr ""
"programs-640?fullscreen=1>`_"
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
msgid "Allow customers to close their tickets"
msgstr "Permiteți clienților să își închidă tichetele"
msgid "Closing tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
msgid ""
"Allowing customers to close their own tickets gives them autonomy and "
"minimizes misunderstandings around when an issue is considered solved or "
"not. This results in operational capacity for support teams, and higher "
"satisfaction for the customer."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:10
msgid "Enable ticket closing"
"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 ""
"Start by navigating to :menuselection:`Helpdesk --> Configuration --> "
"Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit`"
" and enable :guilabel:`Ticket closing` by checking the field box."
"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 "Ticket closing feature in Odoo Helpdesk."
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:19
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
msgid ""
"To designate which stage the ticket migrates to once it is closed, navigate "
"to the ticket pipeline by going to :menuselection:`Helpdesk --> Overview` "
"and clicking :guilabel:`Tickets` on the team's card."
"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:23
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
msgid ""
"There are two options: create a new Kanban stage or work with an existing "
"one. For both scenarios, click the :guilabel:`Settings (gear)` icon next to "
"the stage name, select :guilabel:`Edit Stage`, and enable :guilabel:`Closing"
" Stage`. After checking the field box, click :guilabel:`Save` to finish."
"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:29
msgid ""
"If a closing stage is not specified, by default, the ticket is moved to the "
"last stage in the kanban. If more than one stage is set as a closing stage, "
"the ticket is placed in the first closing stage column."
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
msgid "Stage settings page."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:33
#: ../../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 ""
"With the ticket closing settings now complete, customers can now view the "
"option to :guilabel:`Close this ticket` when they log into their portal."
"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:40
msgid "Get reports on tickets closed by customers"
#: ../../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:42
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
msgid ""
"To analyze the tickets that have been closed by customers, go to "
":menuselection:`Helpdesk --> Reporting --> Tickets`. Then, click on the "
":guilabel:`Filters` menu and choose :guilabel:`Add Custom filter`. Next, set"
" the custom filter parameters to :guilabel:`Closed by partner` and "
":guilabel:`is true`. Finally, click :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
msgid ""
"Filter for tickets closed by customers on Odoo Helpdesk's reporting page."
"Customers with access to the portal will be able to view their tickets under"
" :menuselection:`My Account --> Tickets`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview.rst:5
@@ -996,7 +1131,6 @@ msgstr ""
"echipei de helpdesk în Odoo Helpdesk"
#: ../../content/applications/services/helpdesk/overview/ratings.rst:51
#: ../../content/applications/services/helpdesk/overview/sla.rst:47
msgid ":doc:`../advanced/close_tickets`"
msgstr ":doc:`../advanced/close_tickets`"
@@ -1236,7 +1370,7 @@ msgid ""
"The *Live Chat* feature allows website visitors to connect directly with a "
"support agent or chatbot. During these conversations, *Helpdesk* tickets can"
" be instantly created by using the :doc:`response command "
"</applications/websites/livechat/overview/responses>` `/helpdesk`."
"</applications/websites/livechat/responses>` `/helpdesk`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125
@@ -1487,10 +1621,9 @@ msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261
msgid ""
"During the conversation, an operator can use the shortcut :doc:`command "
"</applications/websites/livechat/overview/responses>` `/helpdesk` to create "
"a ticket without leaving the chat window. The transcript from the "
"conversation will be added to the new ticket, under the "
":guilabel:`Description` tab."
"</applications/websites/livechat/responses>` `/helpdesk` to create a ticket "
"without leaving the chat window. The transcript from the conversation will "
"be added to the new ticket, under the :guilabel:`Description` tab."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267
@@ -1551,7 +1684,7 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
msgstr ":doc:`/applications/general/email_communication/email_servers`"
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293
msgid ":doc:`/applications/websites/livechat/overview/get_started`"
msgid ":doc:`/applications/websites/livechat`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:3
@@ -1698,100 +1831,301 @@ msgstr "Acord privind nivelul de serviciilor (SLA)"
#: ../../content/applications/services/helpdesk/overview/sla.rst:5
msgid ""
"Service Level Agreements (SLA) are commitments you make with your customers "
"to outline how a service is delivered. It bolsters trust between you and "
"your customers as it makes clear what needs to be done, to what standard, "
"and when."
"A Service Level Agreement (SLA) defines the level of service a customer can "
"expect from a supplier. SLAs provide a timeline that tells customers when "
"they can expect results, and keeps the support team on target."
msgstr ""
"Acordurile privind nivelul de servicii (SLA) sunt angajamente pe care vi le "
"asumați față de clienții dvs. pentru a sublinia cum se livrează un serviciu."
" Îmbunătățește încrederea dintre dvs. și clienții dvs. deoarece clarifică ce"
" trebuie făcut, la ce standard și când."
#: ../../content/applications/services/helpdesk/overview/sla.rst:10
msgid "Create your policies"
msgstr "Crează politica ta"
#: ../../content/applications/services/helpdesk/overview/sla.rst:13
msgid ""
"First, enable the feature on the settings of the team you would like "
"policies to be applied, going to :menuselection:`Helpdesk --> Configuration "
"--> Helpdesk Teams`."
msgid "Create a new SLA policy"
msgstr ""
"În primul rând, activați funcția în setările echipei pe care doriți să se "
"aplice politicile, mergând la :menuselection:`Helpdesk --> Configurare --> "
"Echipe de asistenta`."
#: ../../content/applications/services/helpdesk/overview/sla.rst:15
#: ../../content/applications/services/helpdesk/overview/sla.rst:12
msgid ""
"Create your policies through the teams settings page or go to "
":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
"To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to "
"the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`."
" Select a team, scroll to the :guilabel:`Performance` section, and then "
"check the selection box next to :guilabel:`SLA Policies` to enable it for "
"that specific team."
msgstr ""
"Creați politica dvs. prin intermediul paginii de setări a echipei sau "
"mergeți la :menuselection:`Helpdesk --> Configurare --> Politici SLA`."
#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of an SLA form in Odoo Helpdesk"
msgstr "Vizualizarea a unui formular SLA în Odoo Helpdesk"
#: ../../content/applications/services/helpdesk/overview/sla.rst:23
msgid ""
"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
" a ticket needs to have for the policy to be applied."
msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:22
msgid ""
"The value indicated next to the :guilabel:`Working Hours` field is used to "
"determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. "
"By default, this is determined by the value set in the :guilabel:`Company "
"Working Hours` field under :menuselection:`Settings app --> Employees --> "
"Work Organization`."
msgstr ""
"Alegeți pentru **Echipă** este relevantă politica și **Prioritatea minimă** "
"necesară unui tichet, pentru ca politica să fie aplicată."
#: ../../content/applications/services/helpdesk/overview/sla.rst:27
msgid ""
"**Target** is the stage a ticket needs to reach within the period defined to"
" satisfy the SLA. The period is based on the tickets creation date, and a "
"deadline is set on the tickets form once it matches an SLA policy rule. If "
"a ticket has more than one policy applied to it, the closest deadline of all"
" SLAs is the one considered."
"To create a new policy, click the smart button on the team`s settings page "
"or go to :menuselection:`Helpdesk --> Configuration --> SLA Policies`, and "
"click :guilabel:`New`. Start by entering a :guilabel:`Title` and a "
":guilabel:`Description` for the new policy, and proceed to fill out the form"
" using the steps below."
msgstr ""
"**Țintă** este stadiul în care un tichet trebuie să ajungă în perioada "
"definită pentru a satisface SLA. Perioada este bazată pe data creării "
"tichetului, iar o dată limită este setată pe formularul tichetului odată ce "
"se potrivește cu o regulă a politicii SLA. Dacă un tichet are mai multe "
"politici aplicate, atunci cea mai apropiată dată limită dintre toate SLA "
"este cea luată în considerare."
#: ../../content/applications/services/helpdesk/overview/sla.rst:29
#: ../../content/applications/services/helpdesk/overview/sla.rst:33
msgid "Define the criteria for an SLA policy"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:35
msgid ""
"When a ticket has satisfied an SLA policy, the SLA tag appears in green and "
"the deadline field is not shown anymore."
"The :guilabel:`Criteria` section is used to identify what tickets this "
"policy will be applied to. Fill out the following fields to adjust the "
"selection criteria:"
msgstr ""
"Când un tichet a satisfăcut o politică SLA, eticheta SLA apare în verde și "
"nu mai este afișat câmpul limită."
#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of a tickets form emphasizing a satisfied SLA in Odoo Helpdesk"
#: ../../content/applications/services/helpdesk/overview/sla.rst:38
msgid ""
":guilabel:`Team`: a policy can only be applied to one team. *This field is "
"required.*"
msgstr ""
"Vizualizarea unui formular de tichet care evidențiază SLA satisfăcută în "
"Odoo Helpdesk"
#: ../../content/applications/services/helpdesk/overview/sla.rst:37
msgid "SLA Analysis"
msgstr "Analiza SLA"
#: ../../content/applications/services/helpdesk/overview/sla.rst:39
msgid ""
"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply"
" *Filters* and *Group by* to identify tickets that should be prioritized and"
" keep track of upcoming deadlines."
":guilabel:`Priority`: the priority level for a ticket is identified by "
"selecting the number of stars representing the priority level on the kanban "
"card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will "
"only be applied once the priority level has been updated on the ticket to "
"match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is"
" made in this field, this policy will only apply to tickets marked as `Low "
"Priority` (zero stars)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:44
msgid ""
":guilabel:`Types`: ticket types can be helpful when indicating when a ticket"
" is a customer question, that can be solved with a quick response, or an "
"issue, that may require additional investigation. Multiple ticket types can "
"be selected for this field. If no selection is made, this policy will apply "
"to all ticket types."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:48
msgid ""
":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is "
"about. Multiple tags can be applied to a single ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:50
msgid ""
":guilabel:`Customers`: individual contacts or companies may be selected in "
"this field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:51
msgid ""
":guilabel:`Sales Order Items`: this field is available only if a team has "
"the *Timesheets* app enabled. This allows the ticket to tie directly to a "
"specific line on a sales order, which must be indicated on the ticket in the"
" :guilabel:`Sales Order Item` field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:56
msgid ""
"Unless otherwise indicated, multiple selections can be made for each field. "
"(i.e. multiple :guilabel:`Tags` can be included in a policy, but only one "
":guilabel:`Priority` level)"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of a blank SLA policy record"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:64
msgid "Establish a target for an SLA policy"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:66
msgid ""
"The :guilabel:`Target` is the stage a ticket needs to reach, and the time "
"alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service "
"Level Agreement)` policy. Any stage assigned to a team may be selected for "
"the :guilabel:`Reach Stage` field. Time spent in stages selected in "
":guilabel:`Excluding Stages` will not be included in the calculation of the "
":abbr:`SLA (Service Level Agreement)` deadline."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:73
msgid ""
"An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks "
"the working time before a ticket is completed, and would have `Solved` as "
"the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level "
"Agreement)` was titled `2 Days to Start`, it 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:79
msgid "Meeting SLA deadlines"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:81
msgid ""
"Once it is determined that a ticket fits the criteria of an :abbr:`SLA "
"(Service Level Agreement)` policy, a deadline is calculated. The deadline is"
" based on the creation date of the ticket, and the targeted working hours. "
"The deadline is then added to the ticket, as well as a white tag indicating "
"the name of the :abbr:`SLA (Service Level Agreement)` applied."
msgstr ""
"Mergi la :menuselection:`Helpdesk --> Raportare --> Analiza stării SLA`. "
"Aplică *Filtre* și *Grupare după* pentru a identifica tichetele care ar "
"trebui să fie prioritizate și urmărește termenele limită care se apropie."
#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid ""
"View of the SLA status analysis page emphasizing the group by option in Odoo"
"View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo"
" Helpdesk"
msgstr ""
"Vizualizarea paginii de analiză a stării SLA care evidențiază opțiunea de "
"grupare după în Odoo Helpdesk"
#: ../../content/applications/services/helpdesk/overview/sla.rst:91
msgid ""
"If a ticket fits the criteria for more than one :abbr:`SLA (Service Level "
"Agreement)`, the earliest occurring deadline will be displayed on the "
"ticket. Once that deadline has passed, the next deadline will be displayed."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:95
msgid ""
"Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the"
" :abbr:`SLA (Service Level Agreement)` tag turns green, and the "
":guilabel:`Deadline` field disappears from view on the."
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:102
msgid ""
"If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket "
"has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level "
"Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level "
"Agreement)` has failed, the red tag will stay 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:112
msgid "Analyzing SLA performance"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:114
msgid ""
"The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA "
"(Service Level Agreement)` is fulfilled, as well as the success rate of "
"individual policies. Navigate to the report and corresponding pivot table by"
" going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:120
msgid "Using the Pivot view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:122
msgid ""
"By default, the report is displayed in a :guilabel:`Pivot` view, and is "
"filtered to show the number of SLAs failed and the failure rate over the "
"last 30 days, grouped by team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of the SLA status analysis report in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:129
msgid ""
"To add the number of SLAs passed or in progress, click the "
":guilabel:`Measures` button to reveal a drop-down menu of reporting "
"criteria, and choose from the options available based on the measurements "
"preferred. Whenever a measurement is picked, a check mark will appear in the"
" drop-down menu to indicate that that measurement is included, and a "
"corresponding new column will emerge in the pivot table to show the relevant"
" calculations."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:135
msgid ""
"To add a group to a row or column, click the plus :guilabel:` + ` button "
"next to :guilabel:`Total`, and then select one of the groups. To remove one,"
" click the minus :guilabel:` - ` button and deselect."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:140
msgid "Using the Graph view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:142
msgid ""
"The :guilabel:`Status Analysis` report can also be viewed as a "
":guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between "
"these views by selecting the appropriate icon at the top of the chart."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:148
msgid "Bar Chart"
msgstr "Grafic bare"
#: ../../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/sla.rst:154
msgid "Line Chart"
msgstr "Grafic liniar"
#: ../../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:160
msgid "Pie Chart"
msgstr "Grafic tip pie"
#: ../../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:167
msgid ""
"Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed "
":guilabel:`Stacked`. This presents two or more groups to appear on top of "
"each other instead of next to each other, making it easier to compare data."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:172
msgid "Using the Cohort view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:174
msgid ""
"The :guilabel:`Cohort` view is used to track the changes in data over a "
"period of time. To display the :guilabel:`Status Analysis` report in a "
":guilabel:`Cohort` view, click the icon in the top right corner above the "
"chart."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of the SLA status analysis report in cohort view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:183
msgid ":ref:`Reporting views <reporting/views>`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:184
msgid ""
":doc:`Allow customers to close their tickets "
"</applications/services/helpdesk/advanced/close_tickets>`"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5
msgid "Timesheet and Invoice"