NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[I18N] *: export latest terms

Browse Source 
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#10306

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
This commit is contained in:
Tiffany Chang (tic) 2024-07-23 15:48:14 +02:00
parent 32976cdd84
commit bf9bbff058
12 changed files with 9770 additions and 4868 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

78
locale/sources/administration.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-06-24 07:08+0000\n"
"POT-Creation-Date: 2024-07-23 13:30+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -507,7 +507,7 @@ msgstr ""
#: ../../content/administration/odoo_online.rst:3
#: ../../content/administration/supported_versions.rst:29
#: ../../content/administration/upgrade.rst:81
#: ../../content/administration/upgrade.rst:299
#: ../../content/administration/upgrade.rst:296
msgid "Odoo Online"
msgstr ""
@ -723,7 +723,7 @@ msgstr ""
#: ../../content/administration/odoo_sh.rst:5
#: ../../content/administration/supported_versions.rst:30
#: ../../content/administration/upgrade.rst:111
#: ../../content/administration/upgrade.rst:310
#: ../../content/administration/upgrade.rst:307
msgid "Odoo.sh"
msgstr ""
@ -3025,7 +3025,7 @@ msgstr ""
#: ../../content/administration/on_premise.rst:5
#: ../../content/administration/upgrade.rst:136
#: ../../content/administration/upgrade.rst:333
#: ../../content/administration/upgrade.rst:330
msgid "On-premise"
msgstr ""
@ -5467,46 +5467,46 @@ msgid "Upgrading the production database"
msgstr ""
#: ../../content/administration/upgrade.rst:273
msgid "Once the :ref:`tests <upgrade/test_your_db>` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day. It can be planned in coordination with Odoo's upgrade support analysts by `submitting a ticket for an issue related to my future upgrade (I am testing an upgrade) <https://odoo.com/help?stage=migration>`_."
msgid "Once the :ref:`tests <upgrade/test_your_db>` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day."
msgstr ""
#: ../../content/administration/upgrade.rst:279
#: ../../content/administration/upgrade.rst:276
msgid "Your production database will be unavailable during its upgrade. Therefore, we recommend planning the upgrade at a time when the use of the database is minimal."
msgstr ""
#: ../../content/administration/upgrade.rst:282
#: ../../content/administration/upgrade.rst:279
msgid "As the standard upgrade scripts and your database are constantly evolving, it is also recommended to frequently request another upgraded test database to ensure that the upgrade process is still successful, especially if it takes a long time to finish. **Fully rehearsing the upgrade process the day before upgrading the production database is also recommended.**"
msgstr ""
#: ../../content/administration/upgrade.rst:288
#: ../../content/administration/upgrade.rst:285
msgid "Going into production without first testing may lead to:"
msgstr ""
#: ../../content/administration/upgrade.rst:290
#: ../../content/administration/upgrade.rst:287
msgid "Users failing to adjust to the changes and new features"
msgstr ""
#: ../../content/administration/upgrade.rst:291
#: ../../content/administration/upgrade.rst:288
msgid "Business interruptions (e.g., no longer having the possibility to validate an action)"
msgstr ""
#: ../../content/administration/upgrade.rst:292
#: ../../content/administration/upgrade.rst:289
msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)"
msgstr ""
#: ../../content/administration/upgrade.rst:294
#: ../../content/administration/upgrade.rst:291
msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions."
msgstr ""
#: ../../content/administration/upgrade.rst:301
#: ../../content/administration/upgrade.rst:298
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade/request-test-database>`, except for the purpose option, which must be set to :guilabel:`Production` instead of :guilabel:`Test`."
msgstr ""
#: ../../content/administration/upgrade.rst:306
#: ../../content/administration/upgrade.rst:303
msgid "Once the upgrade is requested, the database will be unavailable until the upgrade is finished. Once the process is completed, it is impossible to revert to the previous version."
msgstr ""
#: ../../content/administration/upgrade.rst:312
#: ../../content/administration/upgrade.rst:309
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade/request-test-database>` on the :guilabel:`Production` branch."
msgstr ""
@ -5514,98 +5514,98 @@ msgstr ""
msgid "View from the upgrade tab"
msgstr ""
#: ../../content/administration/upgrade.rst:318
#: ../../content/administration/upgrade.rst:315
msgid "The process is **triggered as soon as a new commit is made** on the branch. This allows the upgrade process to be synchronized with the deployment of the custom modules' upgraded source code. If there are no custom modules, the upgrade process is triggered immediately."
msgstr ""
#: ../../content/administration/upgrade.rst:324
#: ../../content/administration/upgrade.rst:321
msgid "The database is unavailable throughout the process. If anything goes wrong, the platform automatically reverts the upgrade, as it would be for a regular update. In case of success, a backup of the database before the upgrade is created."
msgstr ""
#: ../../content/administration/upgrade.rst:328
#: ../../content/administration/upgrade.rst:325
msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production. More information on how to upgrade your custom modules can be found on :doc:`/developer/howtos/upgrade_custom_db`."
msgstr ""
#: ../../content/administration/upgrade.rst:335
#: ../../content/administration/upgrade.rst:332
msgid "The command to upgrade a database to production is similar to the one of upgrading a test database except for the argument `test`, which must be replaced by `production`:"
msgstr ""
#: ../../content/administration/upgrade.rst:342
#: ../../content/administration/upgrade.rst:339
msgid "An upgraded production database can also be requested via the `Upgrade page <https://upgrade.odoo.com/>`_. Once the database is uploaded, any modification to your production database will **not** be present on your upgraded database. This is why we recommend not using it during the upgrade process."
msgstr ""
#: ../../content/administration/upgrade.rst:349
#: ../../content/administration/upgrade.rst:346
msgid "When requesting an upgraded database for production purposes, the copy is submitted without a filestore. Therefore, the upgraded database filestore must be merged with the production filestore before deploying the new version."
msgstr ""
#: ../../content/administration/upgrade.rst:353
#: ../../content/administration/upgrade.rst:350
msgid "In case of an issue with your production database, you can request the assistance of Odoo by `submitting a ticket for an issue related to my upgrade (production) <https://odoo.com/help?stage=post_upgrade>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:360
#: ../../content/administration/upgrade.rst:357
msgid "Service-level agreement (SLA)"
msgstr ""
#: ../../content/administration/upgrade.rst:362
#: ../../content/administration/upgrade.rst:359
msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database."
msgstr ""
#: ../../content/administration/upgrade.rst:365
#: ../../content/administration/upgrade.rst:362
msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement <upgrade>`. However, this section clarifies what upgrade services you can expect."
msgstr ""
#: ../../content/administration/upgrade.rst:370
#: ../../content/administration/upgrade.rst:367
msgid "Upgrade services covered by the SLA"
msgstr ""
#: ../../content/administration/upgrade.rst:372
#: ../../content/administration/upgrade.rst:369
msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:"
msgstr ""
#: ../../content/administration/upgrade.rst:375
#: ../../content/administration/upgrade.rst:372
msgid "the upgrade of all **standard applications**;"
msgstr ""
#: ../../content/administration/upgrade.rst:376
#: ../../content/administration/upgrade.rst:373
msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and"
msgstr ""
#: ../../content/administration/upgrade.rst:378
#: ../../content/administration/upgrade.rst:375
msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**."
msgstr ""
#: ../../content/administration/upgrade.rst:381
#: ../../content/administration/upgrade.rst:378
msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade."
msgstr ""
#: ../../content/administration/upgrade.rst:385
#: ../../content/administration/upgrade.rst:382
msgid "Upgrade services not covered by the SLA"
msgstr ""
#: ../../content/administration/upgrade.rst:387
#: ../../content/administration/upgrade.rst:384
msgid "The following upgrade-related services are **not** included:"
msgstr ""
#: ../../content/administration/upgrade.rst:389
#: ../../content/administration/upgrade.rst:386
msgid "the **cleaning** of pre-existing data and configurations while upgrading;"
msgstr ""
#: ../../content/administration/upgrade.rst:390
#: ../../content/administration/upgrade.rst:387
msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;"
msgstr ""
#: ../../content/administration/upgrade.rst:391
#: ../../content/administration/upgrade.rst:388
msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code <studio/automated-actions/action>`; and"
msgstr ""
#: ../../content/administration/upgrade.rst:394
#: ../../content/administration/upgrade.rst:391
msgid "**training** on using the upgraded version's features and workflows."
msgstr ""
#: ../../content/administration/upgrade.rst:397
#: ../../content/administration/upgrade.rst:394
msgid ":doc:`Odoo.sh documentation <odoo_sh>`"
msgstr ""
#: ../../content/administration/upgrade.rst:398
#: ../../content/administration/upgrade.rst:395
msgid ":doc:`Supported Odoo versions <supported_versions>`"
msgstr ""

286
locale/sources/essentials.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-06-24 07:08+0000\n"
"POT-Creation-Date: 2024-07-23 13:30+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -467,107 +467,107 @@ msgstr ""
msgid ":doc:`../sales/crm/optimize/utilize_activities`"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:3
#: ../../content/applications/essentials/contacts.rst:5
msgid "Contacts"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:5
#: ../../content/applications/essentials/contacts.rst:7
msgid "The *Contacts* application comes installed on all Odoo databases. Contacts are created for customers the company does business with through Odoo. A contact is a repository of vital business information, facilitating communication and business transactions."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:10
#: ../../content/applications/essentials/contacts.rst:12
msgid "Contact form"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:12
#: ../../content/applications/essentials/contacts.rst:14
msgid "To create a new contact, navigate to the :menuselection:`Contacts app`, and click :guilabel:`Create`. A new form appears where various contact information can be added."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:16
#: ../../content/applications/essentials/contacts.rst:18
msgid "Contact type"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:18
#: ../../content/applications/essentials/contacts.rst:20
msgid "Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, depending on the type of contact that is being added."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:22
#: ../../content/applications/essentials/contacts.rst:24
msgid "Name"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:24
#: ../../content/applications/essentials/contacts.rst:26
msgid "First, fill in the name of the :guilabel:`Individual` or :guilabel:`Company`. This is how the name appears throughout the database. This field is **mandatory**."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:28
#: ../../content/applications/essentials/contacts.rst:30
msgid ":guilabel:`Individual` contacts can have a :guilabel:`Company` contact linked to it. After selecting :guilabel:`Individual`, a new :guilabel:`Company Name...` field appears below the first name field."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:33
#: ../../content/applications/essentials/contacts.rst:35
msgid "Address"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:35
#: ../../content/applications/essentials/contacts.rst:37
msgid "Next, enter the :guilabel:`Address` of the :guilabel:`Company` or :guilabel:`Individual`."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:38
#: ../../content/applications/essentials/contacts.rst:40
msgid "If the :guilabel:`Individual` option is chosen, then the *type of address* can be chosen from a drop-down menu. Options for this drop-down menu include: :guilabel:`Contact`, :guilabel:`Invoice Address`, :guilabel:`Delivery Address`, :guilabel:`Other Address`, and :guilabel:`Private Address`."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:44
#: ../../content/applications/essentials/contacts.rst:46
msgid "Additional fields"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:46
#: ../../content/applications/essentials/contacts.rst:48
msgid "Additional details are included on the initial form. The following fields are available:"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:48
#: ../../content/applications/essentials/contacts.rst:50
msgid ":guilabel:`VAT`: Value Added Tax number."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:49
#: ../../content/applications/essentials/contacts.rst:51
msgid ":guilabel:`Citizen Identification`: citizen or government identification number (only available on :guilabel:`Individual`)."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:51
#: ../../content/applications/essentials/contacts.rst:53
msgid ":guilabel:`Job Position`: list the job position of the :guilabel:`Individual` (only available on :guilabel:`Individual`)."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:53
#: ../../content/applications/essentials/contacts.rst:55
msgid ":guilabel:`Phone`: list phone number (with country code). Make a call, send an SMS, or WhatsApp message by hovering over the field on the saved form, and clicking the desired option."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:55
#: ../../content/applications/essentials/contacts.rst:57
msgid ":guilabel:`Mobile`: list mobile phone number (with country code). Make a call, send an SMS, or WhatsApp message by hovering over the field on the saved form, and clicking on the desired option."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:57
#: ../../content/applications/essentials/contacts.rst:59
msgid ":guilabel:`Email`: enter the email address with the domain."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:58
#: ../../content/applications/essentials/contacts.rst:60
msgid ":guilabel:`Website`: enter the full website address, starting with `http` or `https`."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:59
#: ../../content/applications/essentials/contacts.rst:61
msgid ":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, :guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new one directly from this field."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:61
#: ../../content/applications/essentials/contacts.rst:63
msgid ":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or clicking the drop-down menu, and selecting one. To create a new one, type the new tag in the field, and click :guilabel:`Create` from the resulting drop-down menu."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:66
#: ../../content/applications/essentials/contacts.rst:68
msgid "Contacts & Addresses tab"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:68
#: ../../content/applications/essentials/contacts.rst:70
msgid "At the bottom of the contact form are several tabs. On the :guilabel:`Contacts & Addresses` tab, contacts can be added that are associated with a :guilabel:`Company` and related addresses. For example, a specific contact person for the company can be listed here."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:72
#: ../../content/applications/essentials/contacts.rst:74
msgid "Multiple addresses can be added on both :guilabel:`Individual` and :guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the :guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create Contact` pop-up form, in which additional addresses can be configured."
msgstr ""
@ -575,31 +575,31 @@ msgstr ""
msgid "Add a contact/address to the contact form."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:80
#: ../../content/applications/essentials/contacts.rst:82
msgid "On the :guilabel:`Create Contact` pop-up form, start by clicking the default :guilabel:`Other Address` field at the top to reveal a drop-down menu of address-related options."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:83
#: ../../content/applications/essentials/contacts.rst:85
msgid "Select any of the following options:"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:85
#: ../../content/applications/essentials/contacts.rst:87
msgid ":guilabel:`Contact`: adds another contact to the existing contact form."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:86
#: ../../content/applications/essentials/contacts.rst:88
msgid ":guilabel:`Invoice Address`: adds a specific invoice address to the existing contact form."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:87
#: ../../content/applications/essentials/contacts.rst:89
msgid ":guilabel:`Delivery Address`: adds a specific delivery address to the existing contact form."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:88
#: ../../content/applications/essentials/contacts.rst:90
msgid ":guilabel:`Other Address`: adds an alternate address to the existing contact form."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:89
#: ../../content/applications/essentials/contacts.rst:91
msgid ":guilabel:`Private Address`: adds a private address to the existing contact form."
msgstr ""
@ -607,214 +607,298 @@ msgstr ""
msgid "Create a new contact/address on a contact form."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:95
#: ../../content/applications/essentials/contacts.rst:97
msgid "Once an option is selected, enter the corresponding contact information that should be used for the specified address type."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:98
#: ../../content/applications/essentials/contacts.rst:100
msgid "Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:101
#: ../../content/applications/essentials/contacts.rst:103
msgid "Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` address type has been selected. This is similar to the :guilabel:`Individual` contact."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:104
#: ../../content/applications/essentials/contacts.rst:106
msgid "To add a note, click on the text field next to :guilabel:`Notes`, and write anything that is applicable to the customer or contact."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:107
#: ../../content/applications/essentials/contacts.rst:109
msgid "Then, click :guilabel:`Save & Close` to save the address, and close the :guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save the address, and immediately input another one."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:111
#: ../../content/applications/essentials/contacts.rst:113
msgid "Sales & Purchase tab"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:113
#: ../../content/applications/essentials/contacts.rst:115
msgid "Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the *Sales*, *Purchase*, **or** *Point of Sale* applications are installed."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:116
#: ../../content/applications/essentials/contacts.rst:118
msgid "The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down menu."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:120
#: ../../content/applications/essentials/contacts.rst:122
msgid "Sales section"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:122
#: ../../content/applications/essentials/contacts.rst:124
msgid "Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can be assigned to a contact. To do that, click the :guilabel:`Salesperson` drop-down field, and select one. Create a new :guilabel:`Salesperson` by typing the user's name, and making the appropriate selection."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:126
#: ../../content/applications/essentials/contacts.rst:128
msgid "Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can also be set, if needed. Click the drop-down menu next to :guilabel:`Payment Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down menu to choose the appropriate :guilabel:`Pricelist`."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:131
#: ../../content/applications/essentials/contacts.rst:133
msgid "Click into the :guilabel:`Delivery Method` field to select an option from the drop-down menu."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:134
#: ../../content/applications/essentials/contacts.rst:136
msgid "Point Of Sale section"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:136
#: ../../content/applications/essentials/contacts.rst:138
msgid "Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` that can be used to identify the contact. Use the :guilabel:`Loyalty Points` field to track points the user won as part of a *Loyalty Program*."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:141
#: ../../content/applications/essentials/contacts.rst:143
msgid "Purchase section"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:143
#: ../../content/applications/essentials/contacts.rst:145
msgid "Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` can be set here, as well."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:147
#: ../../content/applications/essentials/contacts.rst:149
msgid "Misc section"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:149
#: ../../content/applications/essentials/contacts.rst:151
msgid "Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add any additional information for this contact. If this contact should only be accessible for one company in a multi-company database, select it from the :guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-down menu to restrict the publishing of this contact to one website (if working on a database with multiple websites). Select one or more :guilabel:`Website Tags` to assist in filtering published customers on the `/customers` website page. Select an :guilabel:`Industry` for this contact from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a *Helpdesk* SLA policy to this contact."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:159
#: ../../content/applications/essentials/contacts.rst:161
msgid "Accounting tab"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:161
#: ../../content/applications/essentials/contacts.rst:163
msgid "The :guilabel:`Accounting` tab appears when the *Accounting* application is installed. Here, a user can add any related :guilabel:`Bank Accounts`, or set default :guilabel:`Accounting entries`."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:164
#: ../../content/applications/essentials/contacts.rst:166
msgid "Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field to enter a Legal Entity Identifier, if necessary."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:168
#: ../../content/applications/essentials/contacts.rst:170
msgid "Internal Notes tab"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:170
#: ../../content/applications/essentials/contacts.rst:172
msgid "Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` tab, where notes can be left on this contact form, just like on the contact form noted above."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:174
#: ../../content/applications/essentials/contacts.rst:176
msgid "Partner Assignment tab"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:176
#: ../../content/applications/essentials/contacts.rst:178
msgid "Next is the :guilabel:`Partner Assignment` tab, which by default, includes a :guilabel:`Geolocation` section, and other partner options, including :guilabel:`Partner Activation` and :guilabel:`Partner Review` configurations. These are **only** present when the *Resellers* module is installed."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:181
#: ../../content/applications/essentials/contacts.rst:183
msgid "Follow the :doc:`Resellers documentation <../sales/crm/track_leads/resellers>` for more information on publishing partners on the website."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:185
#: ../../content/applications/essentials/contacts.rst:187
msgid "Membership tab"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:187
#: ../../content/applications/essentials/contacts.rst:189
msgid "Finally, there is the :guilabel:`Membership` tab on contact forms, which can help users manage any memberships that are being offered to this specific contact. It should be noted that this tab **only** appears when the *Members* application is installed."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:192
#: ../../content/applications/essentials/contacts.rst:194
msgid "Activate membership"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:194
#: ../../content/applications/essentials/contacts.rst:196
msgid "To activate a contact's membership, click :guilabel:`Buy Membership` in the :guilabel:`Membership` tab of a contact form. On the pop-up window that appears, select a :guilabel:`Membership` from the drop-down menu. Then, configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` when both fields are filled in."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:199
#: ../../content/applications/essentials/contacts.rst:201
msgid "Alternatively, to offer a free membership, tick the :guilabel:`Free Member` checkbox, in the :guilabel:`Membership` tab of a contact form."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:203
msgid "Publish members directory"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:205
msgid "To publish a list of active members on the website, the *Online Members Directory* application must first be :ref:`installed <general/install>`. After installing the module, add the `/members` page to the website's menu by :doc:`editing the website menu <../websites/website/pages/menus>`."
msgid "Follow the :doc:`Members documentation <../sales/members>` for more information on publishing members on the website."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:210
msgid "Publish individual members"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:212
msgid "Return to :menuselection:`CRM app --> Sales --> Customers`, and click the Kanban card for a member. Click the :guilabel:`Go to Website` smart button at the top of the page to open the member's webpage."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:216
msgid "After making any necessary changes to the page, click :guilabel:`Save`. At the top of the page, slide the :guilabel:`Unpublished` toggle to the active, :guilabel:`Published` position."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:219
msgid "Repeat these steps for all members."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:222
#: ../../content/applications/essentials/contacts.rst:209
msgid "Smart buttons"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:224
#: ../../content/applications/essentials/contacts.rst:211
msgid "At the top of the contact form, there are some additional options available, known as *smart buttons*."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:227
#: ../../content/applications/essentials/contacts.rst:214
msgid "Here, Odoo displays a variety of records, related to this contact, that were created on other apps. Odoo integrates information from every single app, so there are many smart buttons."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:231
#: ../../content/applications/essentials/contacts.rst:218
msgid "For example, there is an :guilabel:`Opportunities` smart button, where all the opportunities related to this customer from the *CRM* app are accessible."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:235
#: ../../content/applications/essentials/contacts.rst:222
msgid "If the corresponding applications are installed, their related smart buttons appear automatically on a contact form."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:238
#: ../../content/applications/essentials/contacts.rst:225
msgid "A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the :guilabel:`More` smart button reveals additional options, via a drop-down menu. A user can even quickly access :guilabel:`Purchases`, :guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, :guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the :guilabel:`Partner Ledger` connected to this contact."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:244
#: ../../content/applications/essentials/contacts.rst:231
msgid "Deliveries, documents, loyalty cards, and direct debits are *also* linked to smart buttons, like this, should there be any outstanding/on-file for this contact."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:247
#: ../../content/applications/essentials/contacts.rst:234
msgid "If the contact is a partner, the user can visit their partner page on the Odoo-built website by clicking the :guilabel:`Go to Website` smart button."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:251
#: ../../content/applications/essentials/contacts.rst:238
msgid "Archive contacts"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:253
#: ../../content/applications/essentials/contacts.rst:240
msgid "If a user decides they no longer want to have this contact active, the record can be archived. To do that, go to the :icon:`fa-cog` :guilabel:`Action` menu at the top of the contact form, and click :guilabel:`Archive`."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:257
#: ../../content/applications/essentials/contacts.rst:244
msgid "Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-up window."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:259
#: ../../content/applications/essentials/contacts.rst:246
msgid "With this contact successfully archived, as indicated by a banner at the top, they do not show up in the main contacts page, but they can still be searched for with the :guilabel:`Archived` filter."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:263
#: ../../content/applications/essentials/contacts.rst:250
msgid "A contact can be *unarchived*, if the user decides to work with them again. To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at the top of the archived contact form, and click :guilabel:`Unarchive`. Upon doing so, the :guilabel:`Archived` banner is removed, and the contact is restored."
msgstr ""
#: ../../content/applications/essentials/contacts.rst:269
#: ../../content/applications/essentials/contacts.rst:256
msgid ":doc:`Add different addresses in CRM <../sales/sales/send_quotations/different_addresses>`"
msgstr ""
#: ../../content/applications/essentials/contacts.rst:270
#: ../../content/applications/essentials/contacts.rst:257
msgid "`Odoo's eLearning Contacts tutorial <https://www.odoo.com/slides/slide/contacts-2527?fullscreen=1>`_"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:3
msgid "Merge contacts"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:5
msgid "Odoo's *Contacts* application allows user's to merge duplicate contacts, without losing any information in the process. This keeps the database organized, and prevents contacts from being contacted by more than one salesperson."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:12
msgid "Merge duplicate contacts"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:15
msgid "Merging is an irreversible action. Do **not** merge contacts unless absolutely certain they should be combined."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:18
msgid "Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts from the list, and tick the checkbox (on the far-left) for the contacts that should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, and select :guilabel:`Merge` from the resulting drop-down menu."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:-1
msgid "The merge contacts option in the Contacts application."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:27
msgid "This opens the :guilabel:`Merge` pop-up window. From here, review the details of the contacts before confirming they should be merged. If any contacts in the list should **not** be merged, click the :icon:`fa-times` :guilabel:`(delete)` icon at the far right of the contact."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:32
msgid "Click the individual contact to open the record for that contact, and view additional information."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:-1
msgid "The merge pop-up window in the Contacts application."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:39
msgid "Click the :guilabel:`Destination Contact` field, and select an option from the drop-down list. This field defaults to the contact record that was created first in the system."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:42
msgid "After confirming the information on the pop-up window, click :guilabel:`Merge Contacts`."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:45
msgid "Deduplicate contacts"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:47
msgid "After the merge is finished, a pop-up window appears confirming it is complete. This pop-up window also contains a :guilabel:`Deduplicate the other Contacts` button. This feature searches for duplicated records, based on selected criteria, and merges them automatically, or after manual approval."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:52
msgid "Click the :guilabel:`Deduplicate the other Contacts` button to open the :guilabel:`Deduplicate Contacts` pop-up window."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:55
msgid "Select one or more fields to be used in the search for duplicated records. Duplicated contacts can be searched, based on the following criteria:"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:58
msgid ":guilabel:`Email`"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:59
msgid ":guilabel:`Name`"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:60
msgid ":guilabel:`Is Company`"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:61
msgid ":guilabel:`VAT`"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:62
msgid ":guilabel:`Parent Company`"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:65
msgid "If more than one field is selected, only records that have **all** fields in common are suggested as duplicates."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:68
msgid "If necessary, select criteria to be used to exclude potential duplicates from the search. Potential duplicates can be excluded from the search, based on the following criteria:"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:71
msgid ":guilabel:`A user associated to the contact`"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:72
msgid ":guilabel:`Journal Items associated to the contact`"
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:74
msgid "After confirming the search criteria, click either :guilabel:`Merge with Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge Automatically all process`."
msgstr ""
#: ../../content/applications/essentials/contacts/merge.rst:77
msgid "If :guilabel:`Merge with Manual Check` is selected, complete the merge by following the :ref:`steps above <contacts/merge-duplicate>`."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:3
msgid "Export and import data"
msgstr ""

844
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

735
locale/sources/general.pot
View File

File diff suppressed because it is too large Load Diff

4114
locale/sources/hr.pot
View File

File diff suppressed because it is too large Load Diff

2241
locale/sources/inventory_and_mrp.pot
View File

File diff suppressed because it is too large Load Diff

961
locale/sources/marketing.pot
View File

File diff suppressed because it is too large Load Diff

1575
locale/sources/productivity.pot
View File

File diff suppressed because it is too large Load Diff

1194
locale/sources/sales.pot
View File

File diff suppressed because it is too large Load Diff

623
locale/sources/services.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-06-24 07:08+0000\n"
"POT-Creation-Date: 2024-07-23 13:30+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -45,15 +45,16 @@ msgid ":doc:`../../inventory_and_mrp/inventory`"
msgstr ""
#: ../../content/applications/services/field_service/default_warehouse.rst:16
#: ../../content/applications/services/field_service/worksheets.rst:15
#: ../../content/applications/services/helpdesk/overview/help_center.rst:14
#: ../../content/applications/services/planning.rst:29
#: ../../content/applications/services/project/project_management.rst:17
#: ../../content/applications/services/project/project_management.rst:19
#: ../../content/applications/services/project/tasks/recurring_tasks.rst:13
msgid "Configuration"
msgstr ""
#: ../../content/applications/services/field_service/default_warehouse.rst:18
msgid "To set up a user default warehouse, the :doc:`storage locations </applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations>` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database."
msgid "To set up a 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/default_warehouse.rst:23
@ -61,7 +62,7 @@ msgid "You can either set it up :ref:`for your profile <default-warehouse/my-pro
msgstr ""
#: ../../content/applications/services/field_service/default_warehouse.rst:27
msgid ":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations`"
msgid ":doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations`"
msgstr ""
#: ../../content/applications/services/field_service/default_warehouse.rst:32
@ -201,46 +202,114 @@ 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, it needs:"
msgstr ""
#: ../../content/applications/services/field_service/planning_itinerary.rst:23
msgid "a :guilabel:`Planned Date`;"
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 "a valid address linked to the customer’s profile."
msgstr ""
#: ../../content/applications/services/field_service/planning_itinerary.rst:26
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:30
#: ../../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:34
#: ../../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:36
#: ../../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/helpdesk.rst:7
#: ../../content/applications/services/field_service/worksheets.rst:3
msgid "Worksheets"
msgstr ""
#: ../../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 ""
#: ../../content/applications/services/helpdesk.rst:9
#: ../../content/applications/services/helpdesk.rst:8
msgid "Odoo *Helpdesk* is a ticketing-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:15
#: ../../content/applications/services/helpdesk.rst:14
msgid "Create a Helpdesk team"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:17
#: ../../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 in the top-left of the dashboard."
msgstr ""
@ -248,11 +317,11 @@ msgstr ""
msgid "View of the Helpdesk teams page in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:25
#: ../../content/applications/services/helpdesk.rst:24
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:30
#: ../../content/applications/services/helpdesk.rst:29
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 ""
@ -260,63 +329,63 @@ msgstr ""
msgid "View of a Helpdesk team's website form displaying the team description."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:40
#: ../../content/applications/services/helpdesk.rst:39
msgid "Visibility & Assignment"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:42
#: ../../content/applications/services/helpdesk.rst:41
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:46
#: ../../content/applications/services/helpdesk.rst:45
msgid "Determine team visibility"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:48
#: ../../content/applications/services/helpdesk.rst:47
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:51
#: ../../content/applications/services/helpdesk.rst:50
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:55
#: ../../content/applications/services/helpdesk.rst:54
msgid ":guilabel:`All internal users (company)`: all internal users can access the team and all of its tickets."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:57
#: ../../content/applications/services/helpdesk.rst:56
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:61
#: ../../content/applications/services/helpdesk.rst:60
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:64
#: ../../content/applications/services/helpdesk.rst:63
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:68
#: ../../content/applications/services/helpdesk.rst:67
msgid "A team's visibility can be altered after the initial configuration. However, if the team changes from public access to either private or company-only access, portal users are removed as followers from both the team, and from individual tickets."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:75
#: ../../content/applications/services/helpdesk.rst:74
msgid "Follow all team's tickets"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:77
#: ../../content/applications/services/helpdesk.rst:76
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:82
#: ../../content/applications/services/helpdesk.rst:81
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:87
#: ../../content/applications/services/helpdesk.rst:86
msgid "Automatically assign new tickets"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:89
#: ../../content/applications/services/helpdesk.rst:88
msgid "When tickets are received, they need to be assigned to a member of the team. This is done either manually on each ticket individually, or through :guilabel:`Automatic Assignment`. Check the :guilabel:`Automatic Assignment` checkbox to enable this feature for the team."
msgstr ""
@ -325,68 +394,68 @@ msgid "View of a Helpdesk team settings page emphasizing the automatic assignmen
"Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:98
#: ../../content/applications/services/helpdesk.rst:97
msgid "As soon as :guilabel:`Automatic Assignment` has been enabled, additional fields appear."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:100
#: ../../content/applications/services/helpdesk.rst:99
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:103
#: ../../content/applications/services/helpdesk.rst:102
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:106
#: ../../content/applications/services/helpdesk.rst:105
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:110
#: ../../content/applications/services/helpdesk.rst:109
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:114
#: ../../content/applications/services/helpdesk.rst:113
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:117
#: ../../content/applications/services/helpdesk.rst:116
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:122
#: ../../content/applications/services/helpdesk.rst:121
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:127
#: ../../content/applications/services/helpdesk.rst:126
msgid ":ref:`Manage users <users/add-individual>`"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:128
#: ../../content/applications/services/helpdesk.rst:127
msgid ":doc:`Access rights <../general/users/access_rights>`"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:131
#: ../../content/applications/services/helpdesk.rst:130
msgid "Create or modify stages"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:133
#: ../../content/applications/services/helpdesk.rst:132
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.rst:137
#: ../../content/applications/services/helpdesk.rst:136
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.rst:141
#: ../../content/applications/services/helpdesk.rst:140
msgid "To view or modify *Helpdesk* stages, go to :menuselection:`Helpdesk app --> Configuration --> Stages`."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:144
#: ../../content/applications/services/helpdesk.rst:143
msgid "The default list view on the :guilabel:`Stages` page displays the stages currently available in *Helpdesk*. They are listed in the order they appear in the pipeline."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:147
msgid "To change the order of the stages, click the :guilabel:`(six square)` icon, to the left of the stage name, and drag it to the desired place on the list."
#: ../../content/applications/services/helpdesk.rst:146
msgid "To change the order of the stages, click the :icon:`oi-draggable` :guilabel:`(drag)` icon, to the left of the stage name, and drag it to the desired place on the list."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:-1
@ -394,15 +463,15 @@ msgid "View of the stage list page emphasizing the buttons used to change the or
"appear in the list."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:156
#: ../../content/applications/services/helpdesk.rst:155
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.rst:159
#: ../../content/applications/services/helpdesk.rst:158
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.rst:162
#: ../../content/applications/services/helpdesk.rst:161
msgid "Choose a :guilabel:`Name` for the new stage, and add a description, if desired. Then, proceed to fill out the remaining fields following the steps below."
msgstr ""
@ -410,20 +479,20 @@ msgstr ""
msgid "View of a stage's settings page in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:170
#: ../../content/applications/services/helpdesk.rst:169
msgid "Add email and SMS templates to stages"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:172
#: ../../content/applications/services/helpdesk.rst:171
msgid "When an :guilabel:`Email Template` is added to a stage, an email is automatically sent to the customer when a ticket reaches that specific stage in the pipeline. Likewise, adding an :guilabel:`SMS Template` triggers an SMS text message to send to the customer."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:177
#: ../../content/applications/services/helpdesk.rst:176
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.rst:181
msgid "To select an existing email template, select it from the :guilabel:`Email Template` field. Click on the :guilabel:`→ (Internal Link)` icon to the right of the field to edit the chosen template."
#: ../../content/applications/services/helpdesk.rst:180
msgid "To select an existing email template, select it from the :guilabel:`Email Template` field. 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.rst:184
@ -487,7 +556,7 @@ msgid "View a specific team's pipeline by navigating to :menuselection:`Helpdesk
msgstr ""
#: ../../content/applications/services/helpdesk.rst:230
msgid "Select a stage to fold temporarily, then click the :guilabel:`⚙️ (gear)` icon, and select :guilabel:`Fold`."
msgid "Select a stage to fold temporarily, then click the :icon:`fa-gear` :guilabel:`(gear)` icon, and select :guilabel:`Fold` from the drop-down menu."
msgstr ""
#: ../../content/applications/services/helpdesk.rst:-1
@ -499,6 +568,22 @@ msgid "Manually folding a stage from the Kanban view is temporary and does **not
msgstr ""
#: ../../content/applications/services/helpdesk.rst:242
msgid "Merge tickets"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:244
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:248
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:251
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:259
msgid "`Odoo Tutorials: Helpdesk <https://www.odoo.com/slides/helpdesk-51>`_"
msgstr ""
@ -3302,11 +3387,11 @@ msgstr ""
msgid "`Odoo Tutorials: Kanban Project Management <https://www.odoo.com/slides/slide/kanban-project-management-1664>`_"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:19
#: ../../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:22
#: ../../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 ""
@ -3314,59 +3399,59 @@ msgstr ""
msgid "Project card"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:29
#: ../../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:31
#: ../../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:35
#: ../../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:37
#: ../../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:39
#: ../../content/applications/services/project/project_management.rst:41
msgid ":guilabel:`Settings`: you can change the following:"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:41
#: ../../content/applications/services/project/project_management.rst:43
msgid "the :guilabel:`Name` of the project;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:42
#: ../../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:43
#: ../../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:44
#: ../../content/applications/services/project/project_management.rst:46
msgid "the :guilabel:`Tags` used for filtering;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:45
#: ../../content/applications/services/project/project_management.rst:47
msgid "the :guilabel:`Company` responsible for the project;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:46
#: ../../content/applications/services/project/project_management.rst:48
msgid "the employee designated as :guilabel:`Project Manager`;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:47
#: ../../content/applications/services/project/project_management.rst:49
msgid "the :guilabel:`Planned Date` of the project;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:48
#: ../../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:50
#: ../../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 ""
@ -3374,76 +3459,28 @@ msgstr ""
msgid "Project settings"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:58
#: ../../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:61
#: ../../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:65
#: ../../content/applications/services/project/project_management.rst:67
msgid "Scheduling activities"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:67
#: ../../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:75
#: ../../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/tasks.rst:5
msgid "Tasks"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:3
msgid "Create Project's Tasks from an Email Alias"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:5
msgid "When you already have an email address that customers know from the top of their heads, changing it is the last thing you want to do. Instead, link that address to your project and transform those conversations into structured work. It automatically creates a task in the first stage of a project."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:11
msgid "Set up an incoming email server"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:14
msgid "On the *Settings* application, enable *External Email Servers* and define the incoming email alias you would like to use."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:15
msgid "**For more information**: :doc:`/applications/general/email_communication/email_servers`"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:18
msgid "Configure the email alias in your project"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:22
msgid "Now that you have the incoming email server set up, go to :menuselection:`Project --> Configuration --> Projects --> Edit`. Under the *Emails* tab, define the wanted email alias and choose the policy to receive a message."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:23
msgid "In addition, you can now directly set it when creating a new project."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:-1
msgid "In the settings of your project, define the emails alias under the tab email in Odoo Project"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:30
msgid "All the recipients of the email (To/Cc/Bcc) are automatically added as followers of the task."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:32
msgid "The email can be seen under the name of your project on the dashboard."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:-1
msgid "View of the email alias chosen on the dashboard view in Odoo Project"
msgid "Task management"
msgstr ""
#: ../../content/applications/services/project/tasks/recurring_tasks.rst:3
@ -3506,6 +3543,326 @@ msgstr ""
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/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:9
msgid "Manual task creation"
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:23
msgid "Task configuration"
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:25
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:27
msgid ":guilabel:`Task Title`: title of the task."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:28
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:30
msgid ":guilabel:`Project`: the project that this task belongs to."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:31
msgid ":guilabel:`Assignees`: the person(s) in charge of handling the work on this task."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:32
msgid ":guilabel:`Tags`: custom labels allowing to categorize and filter your tasks."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:33
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:35
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:38
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:40
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:45
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:47
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:51
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:54
msgid "**30h**: to allocate 30 hours to the task."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:55
msgid "**#tags**: to add tags to the task."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:56
msgid "**@user**: to assign the task to a user."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:57
msgid "**!**: to star the task as high priority."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:59
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:62
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:70
msgid "Creating tasks from an email alias"
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:72
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:75
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:79
msgid "Fill in the :guilabel:`Create tasks by sending an email to` field as follows:"
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:81
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:83
msgid "**Domain**: in most cases, this is filled in by default with your :doc:`domain <../../../general/email_communication/email_servers>`."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:85
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:90
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:92
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:95
msgid "The email sender is displayed in the :guilabel:`Customer` field."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:96
msgid "The email subject is displayed in the :guilabel:`Task Title` field."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:97
msgid "The email body is displayed in the :guilabel:`Description` field."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:98
msgid "The whole content of the email is additionally displayed in the **chatter**."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:99
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:103
msgid "Creating tasks from a website form"
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:105
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:108
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:110
msgid "In the website editor, edit the following fields:"
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:112
msgid ":guilabel:`Action`: select :guilabel:`Create a Task`."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:113
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:115
msgid ":ref:`Customize the form <dynamic_content/form>`."
msgstr ""
#: ../../content/applications/services/project/tasks/task_creation.rst:117
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:121
msgid ":doc:`Dynamic website content <../../../websites/website/web_design/building_blocks/dynamic_content>`"
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:51
msgid "Task statuses"
msgstr ""
#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:53
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:57
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:59
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:61
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:62
msgid ":guilabel:`Canceled`: to cancel the task."
msgstr ""
#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:63
msgid ":guilabel:`Done`: to close the task once it's been completed."
msgstr ""
#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:67
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:71
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 ""

158
locale/sources/studio.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-05-31 09:59+0000\n"
"POT-Creation-Date: 2024-07-23 13:30+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -20,46 +20,174 @@ msgstr ""
msgid "Studio"
msgstr ""
#: ../../content/applications/studio.rst:17
msgid "Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you can, on any app, add or modify:"
msgstr ""
#: ../../content/applications/studio.rst:20
msgid ":doc:`Fields <studio/fields>`"
#: ../../content/applications/studio.rst:18
msgid "Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you can, in any app, add or modify:"
msgstr ""
#: ../../content/applications/studio.rst:21
msgid ":doc:`Views <studio/views>`"
msgid ":doc:`Fields <studio/fields>`"
msgstr ""
#: ../../content/applications/studio.rst:22
msgid ":doc:`Models <studio/models_modules_apps>`"
msgid ":doc:`Views <studio/views>`"
msgstr ""
#: ../../content/applications/studio.rst:23
msgid ":doc:`Automated actions <studio/automated_actions>`"
msgid ":doc:`Models <studio/models_modules_apps>`"
msgstr ""
#: ../../content/applications/studio.rst:24
msgid ":doc:`PDF reports <studio/pdf_reports>`"
msgid ":doc:`Automated actions <studio/automated_actions>`"
msgstr ""
#: ../../content/applications/studio.rst:25
msgid "Approval rules"
msgid ":doc:`PDF reports <studio/pdf_reports>`"
msgstr ""
#: ../../content/applications/studio.rst:26
msgid ":doc:`Approval rules <studio/approval_rules>`"
msgstr ""
#: ../../content/applications/studio.rst:27
msgid "Security rules"
msgstr ""
#: ../../content/applications/studio.rst:28
msgid "Or you can :doc:`build an app from scratch <studio/models_modules_apps>`."
#: ../../content/applications/studio.rst:29
msgid "You can also :doc:`build an app from scratch <studio/models_modules_apps>`."
msgstr ""
#: ../../content/applications/studio.rst:31
#: ../../content/applications/studio.rst:33
msgid "To access Studio, navigate to the app and model you want to modify, then click the **Toggle Studio** button, or vice versa."
msgstr ""
#: ../../content/applications/studio.rst:36
msgid "To close Studio, click :guilabel:`Close` in the upper right corner."
msgstr ""
#: ../../content/applications/studio.rst:39
msgid "`Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:3
msgid "Approval rules"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:5
msgid "Studio approval rules are used to automate approval processes for actions. They allow you to define the criteria for when an approval is required before an action can be performed using a button."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:9
msgid "Configuration"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:11
msgid "To add approval rules, proceed as follows:"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:13
msgid ":ref:`Open Studio <studio/access>` and switch to the required :doc:`view <views>`."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:14
msgid "Select the button for which you want to add approval rules."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:15
msgid "In the :guilabel:`Properties` tab on the left, enable the :guilabel:`Set approval rules` feature."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:17
msgid "Specify the :guilabel:`Allowed Group` to limit the approval permission to a specific user group."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:19
msgid "Select the :guilabel:`Responsible` user to create an activity for a specific user when approval is requested from them."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:21
msgid "Select the :guilabel:`Users to notify` via internal note."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:22
msgid "Add a :guilabel:`Description` to be displayed in the :ref:`Approval dialog <approval-rules/use>`."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:24
msgid "Optionally, you can also add conditions for the approval rule to be applied by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the :guilabel:`Allowed Group` field."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:27
msgid "To add another rule, click :guilabel:`Add an approval rule`. When there are multiple approval rules, you can:"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:30
msgid "enable :guilabel:`Exclusive Approval` to require approvers to be different users;"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:31
msgid "change the :guilabel:`Notification Order` of the approval rule so that the :guilabel:`Responsible` and :guilabel:`Users to notify` are only notified when the previous rule has been approved, and their approval is required. If the approval rules have the same :guilabel:`Notification Order`, all users are notified at the same time when the first approval is requested."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:36
msgid "Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the :guilabel:`Allowed Group` field to delete the approval rule."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:40
msgid "You can create :ref:`user groups <access-rights/groups>` specifically for approvals."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:45
msgid "Use"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:47
msgid "Once approval rules have been defined for a button:"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:49
msgid "A **user avatar** icon is displayed next to the button's label for each approval rule that has been defined."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:0
msgid "Confirm button with approval for purchase orders"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:55
msgid "When an unauthorized user clicks the button, an error message is displayed in the top-right corner and an activity is created for the user specified in the :guilabel:`Responsible` field."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:57
msgid "Only users from the group defined in the :guilabel:`Allowed Group` field are authorized to approve or reject the action."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:60
msgid "Authorized users can:"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:62
msgid "approve and perform the action by clicking the button;"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:63
msgid "approve the action and allow another user to perform it by clicking the **user avatar** icon next to the button's label, then clicking the :icon:`fa-check` (:guilabel:`Approve`) button in the dialog that opens;"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:66
msgid "reject the action by clicking the **user avatar** icon next to the button's label, then clicking the :icon:`fa-times` (:guilabel:`Reject`) button in the dialog that opens."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:-1
msgid "Approval dialog"
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:73
msgid "The user who approved/rejected the action can revoke their decision by clicking the **user avatar** icon next to the button's label, then clicking the :icon:`fa-undo` (:guilabel:`Revoke`) button."
msgstr ""
#: ../../content/applications/studio/approval_rules.rst:76
msgid "Approvals are tracked in the record's chatter. An approval entry is also created every time a Studio approval-related action is performed. To access the approval entries, :doc:`activate the developer mode </applications/general/developer_mode>` and go to :menuselection:`Settings --> Technical --> Studio Approval Entries`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:3
msgid "Automation rules"
msgstr ""

1829
locale/sources/websites.pot
View File

File diff suppressed because it is too large Load Diff