[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
File diff suppressed because it is too large Load Diff
+6 -502
View File
@@ -6,8 +6,8 @@
# Translators:
# Marcio Nunes, 2023
# Éder Brito <britoederr@gmail.com>, 2023
# Luis Gustavo Almeida <luis.gustavo@kmee.com.br>, 2023
# Luis Felipe Miléo <mileo@kmee.com.br>, 2023
# Luis Gustavo Almeida <luis.gustavo@kmee.com.br>, 2023
# Marcel Savegnago <marcel.savegnago@gmail.com>, 2023
# Martin Trigaux, 2023
# Marcos Rodrigues, 2023
@@ -18,7 +18,7 @@ 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:53+0000\n"
"Last-Translator: Kevilyn Rosa, 2023\n"
"Language-Team: Portuguese (Brazil) (https://app.transifex.com/odoo/teams/41243/pt_BR/)\n"
@@ -386,11 +386,10 @@ msgstr ""
"momento."
#: ../../content/applications/general/auth/azure.rst:9
msgid ":doc:`/applications/general/calendars/outlook/outlook_calendar`"
msgid ":doc:`../../productivity/calendar/outlook`"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:10
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:10
#: ../../content/applications/general/email_communication/email_servers.rst:67
msgid ":doc:`/administration/maintain/azure_oauth`"
msgstr ""
@@ -413,12 +412,10 @@ msgid ""
msgstr ""
#: ../../content/applications/general/auth/google.rst:12
msgid ""
":doc:`/applications/general/calendars/google/google_calendar_credentials`"
msgid ":doc:`../../productivity/calendar/google`"
msgstr ""
#: ../../content/applications/general/auth/google.rst:13
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
#: ../../content/applications/general/email_communication/email_servers.rst:66
msgid ":doc:`/administration/maintain/google_oauth`"
msgstr ""
@@ -664,499 +661,6 @@ msgstr ""
"Em **Modelo de Usuário**, indique um modelo para os novos perfis criados. Se"
" deixado em branco, o perfil de administrador será usado como modelo."
#: ../../content/applications/general/calendars.rst:5
msgid "Calendars"
msgstr "Calendários"
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:3
msgid "Synchronize Google Calendar with Odoo"
msgstr "Sincronizar o Google Calendar com o Odoo"
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5
msgid ""
"Synchronize Google Calendar with Odoo to see and manage meetings from both "
"platforms (updates go in both directions). This integration helps organize "
"your schedule so you never miss a meeting."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9
msgid ":doc:`/applications/general/auth/google`"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:13
msgid "Setup in Google"
msgstr "Configuração no Google"
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:16
msgid "Enable Google Calendar API"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18
msgid ""
"Begin by creating a new Google API project and enabling the Google Calendar "
"API. Then, go to the `Google API Console "
"<https://console.developers.google.com>`_ and log into your Google account."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22
msgid ""
"If this is your first time visiting this page, Google will prompt you to "
"enter a country and agree to the Terms of Service. Select a country from the"
" drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:26
msgid ""
"Next, click :guilabel:`Select a project` and select or create an API project"
" to store credentials."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
msgid "Create a new API project to store credentials."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:33
msgid ""
"Give the API Project a clear name like \"Odoo Sync\" so you can easily find "
"it."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
msgid ""
"Then, open the API Project and click :guilabel:`Enable APIs and Services`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
msgid "Enable APIs and Services on the API Project."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:41
msgid ""
"After that, search for *Google Calendar API* using the search bar and select"
" :guilabel:`Google Calendar API` from the search results. Click "
":guilabel:`Enable`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
msgid "Enable the Google Calendar API."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:49
msgid "Create credentials"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51
msgid ""
"Now that you have created your API project and enabled the Google Calendar "
"API, you need to create credentials. Begin by clicking :guilabel:`Create "
"Credentials`. Google will then guide you through four steps to create your "
"API credentials."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
msgid ""
"In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google"
" Calendar API` and :guilabel:`User Data` options. Then, click "
":guilabel:`Next`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
msgid "Select Google Calendar API and User Data for the Credential Type."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:62
msgid ""
"In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the "
":guilabel:`App name` field, select your email address for the "
":guilabel:`User support email` field, and type your email address for the "
":guilabel:`Developer contact information` section. Then, click "
":guilabel:`Save and Continue`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
msgid ""
"Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and "
"Continue`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
msgid ""
"In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website "
"application` for the :guilabel:`Application Type` field and type *My Odoo "
"Database* for the :guilabel:`Name`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:72
msgid ""
"Under the :guilabel:`Authorized JavaScript Origins` section, click "
":guilabel:`+ Add URI` and type your company's Odoo URL address."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
msgid ""
"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ "
"Add URI` and type your company's Odoo URL address followed by "
"*/google_account/authentication*. Finally, click :guilabel:`Create` and "
":guilabel:`Done`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
msgid ""
"Add the authorized JavaScript origins and the authorized redirect URIs."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83
msgid ""
"After successfully creating a new API project, enabling the Google Calendar "
"API, and generating the Google Calendar API credentials, you should now have"
" a Client ID and Client Secret."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:87
msgid "Client ID & Client Secret"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
msgid ""
"The **Client ID** and the **Client Secret** are both needed to connect "
"Google Calendar to Odoo. Find the Client ID and the Client Secret by opening"
" the Google Cloud Platform navigation menu and going to :menuselection:`API "
"& Services --> Credentials --> OAuth 2.0 Client IDs`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:93
msgid ""
"Next, locate the credentials you just created for the Google Calendar API. "
"Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page "
"will redirect to the edit page, where you can view the Client ID and the "
"Client Secret."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
msgid "Click Edit OAuth Client to view the credential details."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:102
msgid "Setup in Odoo"
msgstr "Configuração em Odoo"
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:104
msgid ""
"Once the Client ID and the Client Secret are located, open the Odoo database"
" and go to :menuselection:`Settings --> General Settings --> Integrations "
"--> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
msgid "The Google Calendar checkbox in General Settings."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
msgid ""
"Next, copy and paste the Client ID and the Client Secret from the Google "
"Calendar API Credentials page into their respective fields below the "
":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:116
msgid ""
"Finally, open the Calendar module in Odoo and click on the "
":guilabel:`Google` sync button to sync Google Calendar with Odoo."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
msgid ""
"Click the Google sync button in Odoo Calendar to sync Google Calendar with "
"Odoo."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:124
msgid ""
"The first time you sync your Google Calendar with Odoo, the page will "
"redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` "
"to authorize Odoo to access Google Calendar."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
msgid "Give Odoo permission to access Google Calendar."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:131
msgid "Now, Odoo Calendar is successfully synced with Google Calendar!"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
msgid "Successfully sync between Odoo and Google Calendar."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
msgid "Synchronize Outlook Calendar with Odoo"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5
msgid ""
"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping "
"track of their tasks and appointments across all related applications."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9
msgid ":doc:`/applications/general/auth/azure`"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:13
msgid "Register the application with Microsoft Azure"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:15
msgid ""
"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account"
" is needed. Creating an account is free for users who have never tried or "
"paid for Azure. For more information, `click here "
"<https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:19
msgid ""
"Refer to `Microsoft's documentation <https://docs.microsoft.com/en-"
"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to"
" set up an Azure AD Tenant (also called an *environment*), which is a "
"representation of an organization to manage and register apps."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:23
msgid ""
"Then, `Register an Application <https://docs.microsoft.com/en-"
"us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the "
"appropriate :guilabel:`Supported account type`. Users who wish to connect "
"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any "
"organizational directory (Any Azure AD directory - Multitenant) and personal"
" Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported "
"account types`."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:29
msgid ""
"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and "
"copy the Odoo database URI (URL) followed by "
"`/microsoft_account/authentication`."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:33
msgid ""
"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` "
"for the :guilabel:`Redirect URI`."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
msgid ""
"The \"Supported account type\" and \"Redirect URI\" settings in the "
"Microsoft Azure AD portal."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:40
msgid ""
"For more information on the restrictions and limitations of URIs, `check "
"this page <https://docs. microsoft.com/en-us/azure/active-"
"directory/develop/reply-url>`_."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:43
msgid ""
"Regarding the application credentials, the user *must* add a client secret, "
"which allows Odoo to authenticate itself, requiring no interaction from the "
"user's side. :guilabel:`Certificates` are optional."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:47
msgid ""
"To do add a client secret, click :guilabel:`Add a certificate or secret` and"
" then click :guilabel:`New client secret`. Next, type a "
":guilabel:`Description` and select when the client secret "
":guilabel:`Expires`."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:51
msgid ""
"Since resetting the synchronization can be tricky, Odoo recommends setting "
"the maximum allowed expiration date for the client secret (24 months), so "
"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to "
"generate the client secret (:guilabel:`Secret ID`)."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:56
msgid "Configuration in Odoo"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:58
msgid ""
"In the Odoo database, go to :menuselection:`Settings --> General Settings "
"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
msgid "The \"Outlook Calendar\" setting activated in Odoo."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:65
msgid ""
"From the Microsoft Azure portal, under the :guilabel:`Overview` section of "
"the application, copy the :guilabel:`Application (Client) ID`, and paste it "
"into the :guilabel:`Client ID` field in Odoo."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
msgid "The \"Client ID\" in the Microsoft Azure portal."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:72
msgid ""
"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` "
"section, copy the :guilabel:`Client Secret Value` and paste it into the "
":guilabel:`Client Secret` field in Odoo."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:79
msgid ""
"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, "
"click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:84
msgid "Sync with Outlook"
msgstr "Sincronizar com Outlook"
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:88
msgid ""
"Odoo highly recommends testing the Outlook calendar synchronization on a "
"test database and a test email address (that is not used for any other "
"purpose) before attempting to sync the desired Outlook Calendar with the "
"user's production database."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:92
msgid ""
"If the user has any past, present, or future events on their Odoo calendar "
"before syncing their Outlook calendar, Outlook will treat the events pulled "
"from Odoo's calendar during the sync as new events, causing an email "
"notification to be sent from Outlook to all the event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:96
msgid ""
"To avoid unwanted emails being sent to all past, present, and future event "
"attendees, the user must add the events from the Odoo calendar to the "
"Outlook calendar before the first ever sync, delete the events from Odoo, "
"and then start the sync."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:100
msgid ""
"Even after synchronizing the Odoo Calendar with the Outlook calendar, "
"Outlook will still send a notification to all event participants every time "
"an event is edited (created, deleted, unarchived, or event date/time "
"changed), with no exceptions. This is a limitation that cannot be fixed from"
" Odoo's side."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:105
msgid ""
"After one user syncs their Outlook calendar to the Odoo database, unwanted "
"email notifications are unavoidable because the first synchronized user's "
"events will be in the Odoo Calendar. If the Odoo database is shared amongst "
"multiple users, and another user wants to sync their Outlook calendar with "
"Odoo Calendar, Outlook will again pull the existing Odoo Calendar events "
"during the sync and treat them as new events, causing Outlook to send email "
"invitations to all event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:112
msgid ""
"In summary, once a user synchronizes their Outlook calendar with the Odoo "
"calendar:"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:114
msgid ""
"Creating an event in Odoo causes Outlook to send an invitation to all event "
"attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:115
msgid ""
"Deleting an event in Odoo causes Outlook to send a cancellation to all event"
" attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:116
msgid ""
"Unarchiving an event in Odoo causes Outlook to send an invitation to all "
"event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:117
msgid ""
"Archiving an event in Odoo causes Outlook to send a cancellation to all "
"event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:118
msgid ""
"Adding a contact to an event causes Outlook to send an invitation to all "
"event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:119
msgid ""
"Removing a contact from an event causes Outlook to send a cancellation to "
"all event attendees."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:122
msgid "Sync Odoo Calendar and Outlook"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:124
msgid ""
"In the Odoo database, go to the :guilabel:`Calendar` module and click the "
":guilabel:`Outlook` sync button. The page will redirect to a Microsoft login"
" page, and the user is asked to log in to their account, if they are not "
"already, and grant the required permissions."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
msgid "The \"Outlook\" sync button in Odoo Calendar."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:132
msgid ""
"The synchronization is a two-way process, meaning that events are reconciled"
" in both accounts (Outlook and Odoo)."
msgstr ""
"A sincronização é um processo bidirecional, o que significa que os eventos "
"são reconciliados em ambas as contas (Outlook e Odoo)."
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:136
msgid ""
"All users that want to use the synchronization simply need to :ref:`sync "
"their calendar with Outlook <outlook_calendar/sync_with_outlook>`. The "
"configuration of Microsoft's Azure account is only done once, as Azure AD "
"tenants' Client IDs and Client Secrets are unique, and represent an "
"organization that helps the user to manage a specific instance of Microsoft "
"cloud services for their internal and external users."
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:143
msgid ":doc:`../../../productivity/mail_plugins/outlook`"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:144
msgid ":doc:`../google/google_calendar_credentials`"
msgstr ":doc:`../google/google_calendar_credentials`"
#: ../../content/applications/general/developer_mode.rst:5
msgid "Developer Mode (debug mode)"
msgstr ""
@@ -4889,8 +4393,8 @@ msgstr ""
"instalado anteriormente e clicar em **SALVAR.**"
#: ../../content/applications/general/users/language.rst:61
msgid ":doc:`../../websites/website/publish/translate`"
msgstr ":doc:`../../websites/website/publish/translate`"
msgid ":doc:`../../websites/website/configuration/translate`"
msgstr ""
#: ../../content/applications/general/users/manage_users.rst:3
msgid "Manage users"
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
+450 -112
View File
@@ -14,7 +14,7 @@ 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: Martin Trigaux, 2023\n"
"Language-Team: Portuguese (Brazil) (https://app.transifex.com/odoo/teams/41243/pt_BR/)\n"
@@ -365,80 +365,215 @@ msgstr ""
"programs-640?fullscreen=1>`_"
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
msgid "Allow customers to close their tickets"
msgstr "Permitir aos clientes a fechar seus tickets"
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
@@ -981,7 +1116,6 @@ msgid ""
msgstr ""
#: ../../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`"
@@ -1221,7 +1355,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
@@ -1472,10 +1606,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
@@ -1536,7 +1669,7 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
msgstr ""
#: ../../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
@@ -1674,97 +1807,302 @@ msgstr "Acordos de Nível de Serviço (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 ""
"Acordos de Nível de Serviço (SLA) são compromissos que você assume com seus "
"clientes para delinear como um serviço é fornecido. Ele reforça a confiança "
"entre você e seus clientes, pois deixa claro o que precisa ser feito, em que"
" padrão e quando."
#: ../../content/applications/services/helpdesk/overview/sla.rst:10
msgid "Create your policies"
msgstr "Crie suas políticas"
#: ../../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 ""
"Primeiro, habilite o recurso sobre as configurações da equipe que você "
"gostaria que as políticas fossem aplicadas, indo para "
":menuselection:`Helpdesk --> Configuration --> Helpdesk Teams'."
#: ../../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 ""
"Crie suas políticas através da página de configurações da equipe ou vá para "
":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of an SLA form in Odoo Helpdesk"
msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:23
#: ../../content/applications/services/helpdesk/overview/sla.rst:22
msgid ""
"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
" a ticket needs to have for the policy to be applied."
"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 ""
"Escolha para qual **equipa** a apólice é relevante e a **Prioridade Mínima**"
" um ingresso necessário para que a apólice seja aplicada."
#: ../../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 ""
"**Target** é o estágio que um bilhete precisa alcançar dentro do período "
"definido para satisfazer o SLA. O período é baseado na data de criação do "
"ingresso, e um prazo é estabelecido no formulário do ingresso uma vez que "
"ele corresponda a uma regra da política do SLA. Se um ingresso tem mais de "
"uma política aplicada a ele, o prazo mais próximo de todos os SLAs é o prazo"
" considerado."
#: ../../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."
msgstr ""
"Quando um bilhete tiver satisfeito uma política SLA, a etiqueta SLA aparece "
"em verde e o campo de prazo não é mais exibido."
#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of a tickets form emphasizing a satisfied SLA in Odoo Helpdesk"
"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 ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:37
msgid "SLA Analysis"
msgstr "Análise de SLA"
#: ../../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 ""
#: ../../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 ""
"Ir para :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis'. "
"Aplique *Filtros* e *Grupos por* para identificar os bilhetes que devem ser "
"priorizados e acompanhar os próximos prazos."
#: ../../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 ""
#: ../../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 "Gráfico de Barras"
#: ../../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 "Gráfico de linha"
#: ../../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 "Gráfico de Pizza"
#: ../../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"
msgstr "Folha de horas de trabalho e fatura"
File diff suppressed because it is too large Load Diff