From 4f4c8001d2988b1142353ae2cf1a9e314beac403 Mon Sep 17 00:00:00 2001 From: Weblate Date: Sat, 25 Nov 2023 03:09:44 +0100 Subject: [PATCH] Maintenance: Translations update from translations.zammad.org. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Special thanks to the amazing translation team. You rock! 💪 Co-authored-by: Weblate Translate-URL: https://translations.zammad.org/projects/documentations/admin-documentation-pre-release/ Translation: Documentation/Admin Documentation (pre-release) --- locale/cs/LC_MESSAGES/admin-docs.po | 440 ++++++++-------- locale/da/LC_MESSAGES/admin-docs.po | 440 ++++++++-------- locale/de/LC_MESSAGES/admin-docs.po | 641 +++++++++++++++-------- locale/es/LC_MESSAGES/admin-docs.po | 449 ++++++++-------- locale/es_CO/LC_MESSAGES/admin-docs.po | 440 ++++++++-------- locale/es_MX/LC_MESSAGES/admin-docs.po | 440 ++++++++-------- locale/fa/LC_MESSAGES/admin-docs.po | 440 ++++++++-------- locale/fr/LC_MESSAGES/admin-docs.po | 453 ++++++++-------- locale/fr_CA/LC_MESSAGES/admin-docs.po | 451 ++++++++-------- locale/hr/LC_MESSAGES/admin-docs.po | 449 ++++++++-------- locale/hu/LC_MESSAGES/admin-docs.po | 440 ++++++++-------- locale/it/LC_MESSAGES/admin-docs.po | 443 ++++++++-------- locale/nl/LC_MESSAGES/admin-docs.po | 440 ++++++++-------- locale/pl/LC_MESSAGES/admin-docs.po | 444 ++++++++-------- locale/pt_BR/LC_MESSAGES/admin-docs.po | 468 +++++++++-------- locale/ru/LC_MESSAGES/admin-docs.po | 443 ++++++++-------- locale/sr/LC_MESSAGES/admin-docs.po | 636 ++++++++++++++-------- locale/sv/LC_MESSAGES/admin-docs.po | 440 ++++++++-------- locale/th/LC_MESSAGES/admin-docs.po | 440 ++++++++-------- locale/tr/LC_MESSAGES/admin-docs.po | 506 ++++++++++-------- locale/zh_Hans/LC_MESSAGES/admin-docs.po | 446 ++++++++-------- 21 files changed, 5310 insertions(+), 4479 deletions(-) diff --git a/locale/cs/LC_MESSAGES/admin-docs.po b/locale/cs/LC_MESSAGES/admin-docs.po index a7bba6d6..2fe30be3 100644 --- a/locale/cs/LC_MESSAGES/admin-docs.po +++ b/locale/cs/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2023-09-23 01:11+0000\n" "Last-Translator: Tomáš Kovařík \n" "Language-Team: Czech determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5653,8 +5653,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6132,7 +6132,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6173,14 +6173,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6195,7 +6192,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6208,35 +6205,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6244,53 +6241,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6301,7 +6295,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6342,14 +6336,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6368,15 +6362,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6386,54 +6380,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6441,68 +6434,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6514,16 +6507,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6531,39 +6524,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6572,52 +6565,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6625,10 +6618,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7064,7 +7057,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8114,7 +8107,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8135,21 +8128,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8158,8 +8151,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8212,15 +8205,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8699,6 +8692,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9022,6 +9019,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9031,9 +9032,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9062,7 +9063,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9988,12 +9989,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10067,7 +10072,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10171,6 +10176,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10179,7 +10188,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10191,7 +10200,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10206,7 +10215,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10341,92 +10350,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10448,38 +10452,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10487,48 +10491,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10540,39 +10544,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10580,20 +10584,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10607,18 +10611,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10835,15 +10839,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10868,7 +10871,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10906,7 +10909,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11020,34 +11023,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11058,17 +11061,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11079,32 +11082,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16293,6 +16296,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16662,6 +16669,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17262,6 +17273,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/da/LC_MESSAGES/admin-docs.po b/locale/da/LC_MESSAGES/admin-docs.po index 8b2add16..c49a8dc0 100644 --- a/locale/da/LC_MESSAGES/admin-docs.po +++ b/locale/da/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -553,7 +553,7 @@ msgstr "" #: ../channels/email/accounts/account-setup.rst:156 #: ../channels/email/accounts/account-setup.rst:281 -#: ../manage/webhook/add.rst:72 ../settings/security/third-party/saml.rst:170 +#: ../manage/webhook/add.rst:74 ../settings/security/third-party/saml.rst:170 #: ../system/integrations/i-doit.rst:77 msgid "SSL verification" msgstr "" @@ -1114,7 +1114,7 @@ msgstr "" #: ../channels/email/accounts/secondary-addresses.rst:42 #: ../manage/groups/settings.rst:96 ../manage/macros/how-do-they-work.rst:0 #: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:91 -#: ../manage/webhook/add.rst:118 +#: ../manage/webhook/add.rst:120 #: ../system/integrations/cti/includes/inbound-calls.include.rst:10 #: ../system/integrations/cti/includes/outbound-calls.include.rst:20 #: ../system/integrations/cti/includes/inbound-calls.include.rst:9 @@ -2455,7 +2455,7 @@ msgstr "" msgid "" "Feedback or contact forms are used on websites quite often. Usually they " "will generate an email which will be sent to somebody who forwards it and so " -"on. With Zammad it’s quite easy to integrate these forms into your website " +"on. With Zammad it's quite easy to integrate these forms into your website " "and directly generate tickets with them. In just 2 minutes." msgstr "" @@ -2513,7 +2513,7 @@ msgstr "" #: ../channels/form.rst:39 ../manage/groups/settings.rst:112 #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:94 ../manage/templates.rst:43 -#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:43 +#: ../manage/webhook/add.rst:129 ../system/integrations/i-doit.rst:43 msgid "Active" msgstr "" @@ -2567,7 +2567,7 @@ msgstr "" msgid "So let's talk about the options the designer provides." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:70 msgid "Title of the form" msgstr "" @@ -2581,7 +2581,7 @@ msgstr "" msgid "Default: ``Feedback Form``" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:75 msgid "Name of form submit button" msgstr "" @@ -2592,7 +2592,7 @@ msgid "" "form is shown." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:86 msgid "Message after sending form" msgstr "" @@ -2606,7 +2606,7 @@ msgstr "" msgid "Default *after* sending a form will look like so:" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:146 msgid "Options" msgstr "" @@ -2771,7 +2771,7 @@ msgid "" "apply Zammad's web form to your website. It basically consists of two parts." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:186 msgid "Header section" msgstr "" @@ -2793,7 +2793,7 @@ msgstr "" msgid "Do not mix jQuery versions - it's likely to break something." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:207 msgid "Body section" msgstr "" @@ -5217,13 +5217,13 @@ msgstr "" #: ../manage/calendars.rst:40 msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5623,8 +5623,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6102,7 +6102,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6143,14 +6143,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6165,7 +6162,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6178,35 +6175,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6214,53 +6211,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6271,7 +6265,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6312,14 +6306,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6338,15 +6332,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6356,54 +6350,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6411,68 +6404,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6484,16 +6477,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6501,39 +6494,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6542,52 +6535,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6595,10 +6588,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7034,7 +7027,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8084,7 +8077,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8105,21 +8098,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8128,8 +8121,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8182,15 +8175,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8669,6 +8662,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -8992,6 +8989,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9001,9 +9002,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9032,7 +9033,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9958,12 +9959,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10037,7 +10042,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10141,6 +10146,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10149,7 +10158,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10161,7 +10170,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10176,7 +10185,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10311,92 +10320,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10418,38 +10422,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10457,48 +10461,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10510,39 +10514,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10550,20 +10554,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10577,18 +10581,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10805,15 +10809,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10838,7 +10841,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10876,7 +10879,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -10990,34 +10993,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11028,17 +11031,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11049,32 +11052,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16263,6 +16266,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16632,6 +16639,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17232,6 +17243,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/de/LC_MESSAGES/admin-docs.po b/locale/de/LC_MESSAGES/admin-docs.po index 8ae732b2..157eb264 100644 --- a/locale/de/LC_MESSAGES/admin-docs.po +++ b/locale/de/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2023-11-24 08:00+0000\n" "Last-Translator: Ralf Schmid \n" "Language-Team: German determine a name, a time-zone, the business hours to be used for this " +#| "calendar and special holidays. In addition, you can subscribe to the " +#| "iCalendar, which will automatically load all holidays from Google " +#| "(updated once a day) ... and you can add a note." msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." @@ -6507,7 +6519,7 @@ msgstr "" "Google lädt (einmal täglich aktualisiert) ... und Sie können eine Notiz " "hinzufügen." -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "Gruppenberechtigungen" @@ -7026,9 +7038,13 @@ msgstr "" "den Besitzer zurücksetzen soll." #: ../manage/groups/settings.rst:62 +#, fuzzy +#| msgid "" +#| "The ticket will remain to the last agent who owned it. This is the " +#| "default value" msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" "Das Ticket verbleibt beim letzten Agenten, dem es gehört hat. Dies ist der " "Standardwert" @@ -7607,7 +7623,10 @@ msgid "Macros" msgstr "Makros" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +#, fuzzy +#| msgid "" +#| "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" "Makros sind **🖱️ ein-Klick-Aktionen** zum Anwenden von Änderungen an einem " "Ticket." @@ -7659,14 +7678,15 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "Sie können \"Makros\" im Admin-Panel erstellen oder bearbeiten:" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +#, fuzzy +#| msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "Screenshot \"Makros“ im Admin-Bereich" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#, fuzzy +#| msgid "How do they work?" +msgid "How do macros work" msgstr "Wie funktionieren sie?" #: ../manage/macros/how-do-they-work.rst:4 @@ -7685,7 +7705,7 @@ msgstr "" "Es gibt zusätzliche Einstellungen, die beeinflussen, wer ein Makro verwenden " "kann oder wie es sich verhält." -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "Makros erstellen" @@ -7698,27 +7718,27 @@ msgstr "Screenshot zeigt verschiedene Aktionen für Makros." msgid "Actions" msgstr "Aktionen" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "Sie können Aktionen erstellen, um:" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "Ticketattribute festzulegen (Priorität, Status, Gruppe, usw.)" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "Notizen zu Tickets hinzuzufügen" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "Es gibt **keine** Aktionen für:" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "Eine Antwort an Ihren Kunden zu senden" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." @@ -7727,9 +7747,13 @@ msgstr "" "Aktionen in Makros **keine** Verwendung von :doc:`Variablen `." -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 +#, fuzzy +#| msgid "" +#| "If the ticket is missing a required attribute and the macro doesn’t set " +#| "it, then **no actions will be applied**." msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" "Wenn dem Ticket ein erforderliches Attribut fehlt und das Makro es nicht " @@ -7739,40 +7763,51 @@ msgstr "" msgid "Once completed..." msgstr "Nach Abschluss..." -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 +#, fuzzy +#| msgid "" +#| "After running this macro, should Zammad remain on the current tab, close " +#| "it, or automatically switch to the next ticket? (Does not apply when " +#| "running macros “in bulk”.)" msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" "Soll Zammad nach der Ausführung dieses Makros auf der aktuellen " "Registerkarte bleiben, diese schließen oder automatisch zum nächsten Ticket " "wechseln? (Gilt nicht, wenn Makros auf mehrere Tickets angewandt werden.)" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 +#, fuzzy +#| msgid "" +#| "What should other Zammad admins know about this macro? (Visible only via " +#| "the “Edit: Macro” dialog, Rails console, and API.)" msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" "Was sollten andere Zammad-Administratoren über dieses Makro wissen? (Nur " "sichtbar über das Dialogfeld \"Bearbeiten: Makro“, die Rails-Konsole und die " "API.)" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" "Welche :doc:`/manage/groups/index` dürfen das Makro sehen und verwenden?" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +#, fuzzy +#| msgid "Choose “inactive” to disable this macro without deleting it." +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" "Wählen Sie \"inaktiv“, um dieses Makro zu deaktivieren, ohne es zu löschen." -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "Verwaltung von Makros" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." @@ -7780,27 +7815,30 @@ msgstr "" "Sie können vorhandene Makros im Admin-Panel unter **Verwalten > Makros** " "löschen oder sogar klonen." -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" "Screencast zeigt die Erstellung eines neuen Makros durch Klonen und dessen " "Entfernung" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 +#, fuzzy +#| msgid "" +#| "When cloning a macro, you *must* click “Submit” for the duplicate to be " +#| "created." msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" "Beim Klonen eines Makros *müssen* Sie auf \"Übermitteln“ klicken, damit das " "Duplikat erstellt wird." #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" -msgstr "Lernen Sie anhand eines Beispiels" +#, fuzzy +#| msgid "Example" +msgid "Macro Example" +msgstr "Beispiel" #: ../manage/macros/learn-by-example.rst:4 msgid "" @@ -7811,8 +7849,13 @@ msgstr "" "Klick-Aktionen, die Sie mithilfe von Makros einrichten können." #: ../manage/macros/learn-by-example.rst:9 +#, fuzzy +#| msgid "" +#| "If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +#| "manage/macros/how-do-they-work` to learn about all the options in detail, " +#| "then come back here to see them in action." msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -7860,11 +7903,17 @@ msgstr "" "regelmäßig unerwünschte Tickets zu bereinigen." #: ../manage/macros/learn-by-example.rst:29 +#, fuzzy +#| msgid "" +#| "If you want to set a ticket’s state to *pending reminder*, it’s usually a " +#| "two-step process—first select the state, then select a date. To always " +#| "set a reminder for the same, fixed amount of time (say, seven days " +#| "later), you can bundle the whole change into a macro:" msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" "Wenn Sie den Status eines Tickets auf \"warten auf Erinnerung“ setzen " "möchten, erfolgt dies normalerweise in zwei Schritten: Wählen Sie zunächst " @@ -7873,7 +7922,9 @@ msgstr "" "die gesamte Änderung in einem Makro bündeln:" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +#, fuzzy +#| msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "\"In 7 Tagen erinnern.“ (🔒 nur interne Sichtbarkeit)" #: ../manage/macros/learn-by-example.rst:35 @@ -7894,15 +7945,15 @@ msgstr "" "Screencast zeigt die Konfiguration und das Verhalten eines Makros, das den " "Status \"Warten auf Erinnerung\" setzt" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "über das Admin-Panel" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "über einen CSV-Import" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "über die REST-API" @@ -7912,31 +7963,28 @@ msgstr "Organisationen" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -"Abhängig von den IT-Fähigkeiten Ihrer Firma können Organisationen einzeln " -"oder in großen Mengen verwaltet werden." -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "Erstellen und Bearbeiten von Benutzern direkt im Admin-Panel" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" "Der einfachste Weg, Organisationen zu verwalten, ist direkt im Admin-Panel." -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "Erfahren Sie mehr über die Verwaltung von Organisationen..." -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "😲 **Technische Einschränkungen**" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." @@ -7944,7 +7992,7 @@ msgstr "" "Organisationen können derzeit nicht entfernt werden. Die einzige Ausnahme " "ist die Funktion :doc:`/system/data-privacy` in Zammad." -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." @@ -7953,7 +8001,7 @@ msgstr "" "erstellen. Weitere Informationen finden Sie unter :doc:`Berechtigungen `." -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." @@ -7962,16 +8010,16 @@ msgstr "" "funktionieren, unterstützen externe Verwaltungsdienste wie LDAP oder " "Exchange *keine* Synchronisierung von Organisationen." -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" "Ist das für Sie relevant? Ziehen Sie Domainbasierte Zuweisungen in Betracht." -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "🥵 **GROSSE Organisationen können Leistungsprobleme verursachen**" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -7984,43 +8032,47 @@ msgstr "" "oder häufige Kommunikation. Viele Synchronisierungen verknüpfter Daten " "können einen Overhead verursachen." -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "Mit Vorsicht fortfahren." -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "Dokumentation: Details zur Organisation" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 +#, fuzzy +#| msgid "" +#| "Most of the attributes you can set on organizations are self-explanatory. " +#| "The ones that aren’t are described below." msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" "Die meisten Attribute, die Sie für Organisationen festlegen können, sind " "selbsterklärend. Diejenigen, bei denen dies nicht der Fall ist, werden unten " "beschrieben." -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" "Das Dialogfeld \"Organisation bearbeiten“ zeigt die verschiedenen " "Detailfelder an" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" "Details können im Dialogfeld **Neu/Bearbeiten Organisation** festgelegt " "werden." -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" "🕵️ **Administratoren sind nicht die einzigen, die diese Einstellungen ändern " "können.**" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." @@ -8029,11 +8081,11 @@ msgstr "" "`die Ticket-Ansicht ` oder die " "Organisationsdetails)." -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "📢 Geteilte Organisation" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " @@ -8043,7 +8095,7 @@ msgstr "" "zusätzlich zu ihren eigenen Tickets auch die Tickets ihrer " "Organisationsmitglieder **ansehen** und **aktualisieren**." -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." @@ -8052,11 +8104,11 @@ msgstr "" "Übersichten, die nur für gemeinsam genutzte Organisationen verfügbar sind. " "Erfahren Sie mehr unter :doc:`/manage/overviews`." -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "Der Standardwert dafür ist ``Ja``." -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " @@ -8067,7 +8119,7 @@ msgstr "" "Regel für Supportunternehmen mit relativ großen Kunden und " "Supportkontingenten relevant." -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -8084,18 +8136,18 @@ msgstr "" "Screenshot mit der Übersicht \"Meine Organisationstickets“ mit Tickets von " "allen Organisationsmitgliedern" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" "Mitglieder einer teilenden Organisation haben Zugriff auf " "organisationsbasierte Übersichten" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "🗄️ Domainbasierte Zuweisung" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -8107,11 +8159,11 @@ msgstr "" "Ihren Arbeitsaufwand erheblich reduzieren und dient als Workaround, da " "Organisationen nicht über LDAP abgebildet werden können." -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "Der Standardwert für Erstellungsdialoge ist ``nein``" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." @@ -8119,11 +8171,11 @@ msgstr "" "Die Domainbasierte Zuweisung funktioniert nur für *neu erstellte* Benutzer " "und hat keine Auswirkungen auf bestehende Benutzer." -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "🌐 Domain" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " @@ -8134,7 +8186,7 @@ msgstr "" "Diese Option gehört zur Domainbasierten Zuweisung und ist erforderlich, wenn " "sie auf ``Ja`` gesetzt ist." -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " @@ -8144,11 +8196,11 @@ msgstr "" "darauf, keine Domains von kostenlosen E-Mail-Providern wie ``gmail.com`` " "einzutragen." -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "👑 VIP" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -8161,56 +8213,69 @@ msgstr "" "slas/index` und :doc:`/manage/overviews` für VIPs einrichten." #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +#, fuzzy +#| msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" "Ticketansicht mit dem Avatar einer VIP-Organisation mit einer Krone darauf" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" "VIP-Organisationen werden mit einer Krone über ihren Avataren angezeigt." -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "📑 Notiz" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" "Notizen sind für alle Mitarbeiter sichtbar, **einschließlich Agenten**." -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 +#, fuzzy +#| msgid "" +#| "😵 **Are you using the Note field to keep track of your own “custom” " +#| "organization attributes?**" msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" "😵 **Verwenden Sie das Notizfeld, um den Überblick über Ihre eigenen " "\"benutzerdefinierten“ Organisationsattribute zu behalten?**" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +#, fuzzy +#| msgid "" +#| "Wish you could add your own fields to the New/Edit Organization dialog?" +msgid "Wish you could add your own fields Organizations?" msgstr "" "Möchten Sie Ihre eigenen Felder zum Dialogfeld \"Neu/Bearbeiten Organisation" "\" hinzufügen?" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" "Sie können! Weitere Informationen finden Sie unter :doc:`/system/objects`." -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "▶️ Aktiv" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 +#, fuzzy +#| msgid "" +#| "Disabling this flag is a soft alternative to deleting an organization. So " +#| "what’s the difference?" msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" "Das Deaktivieren ist eine Alternative zum Löschen einer Organisation. Was " "ist denn der Unterschied?" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." @@ -8218,7 +8283,7 @@ msgstr "" "Es gibt keine Möglichkeit, eine gelöschte Organisation wiederherzustellen. " "Inaktive Organisationen können jederzeit reaktiviert werden." -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" "Inaktive Organisationen werden weiterhin in den Suchergebnissen angezeigt:" @@ -8227,10 +8292,14 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "Eine inaktive Organisation wird in der Suche angezeigt" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 +#, fuzzy +#| msgid "" +#| "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +#| "inactive organizations are greyed out." msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" "Ein durchgestrichenes 🏢-Symbol zeigt eine inaktive Organisation. In anderen " "Fällen werden inaktive Organisationen ausgegraut." @@ -8798,8 +8867,8 @@ msgid "" msgstr "Screenshot zeigt Einstellungen für öffentliche Links" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." -msgstr "Lernen Sie ..." +msgid "See here:" +msgstr "" #: ../manage/public-links.rst:14 msgid ":ref:`public_links_add_new`" @@ -10039,7 +10108,7 @@ msgstr "" "Damit das funktioniert, brauchen Sie zwei getrennte Rollen: eine mit " "``ticket.agent`` und die andere mit ``ticket.customer``." -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "Rollen" @@ -10065,16 +10134,25 @@ msgstr "" "Vergeben Sie Benutzerrechte im Admin Panel unter **Verwalten > Rollen**." #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +#, fuzzy +#| msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" "👀 Benutzer können gleichzeitig die Rollen \"Agent\" und \"Kunde\" haben!" #: ../manage/roles/index.rst:18 +#, fuzzy +#| msgid "" +#| "Why would you want this? Agents get :doc:`overviews ` " +#| "of all the tickets they're *assigned to* (among other things), while " +#| "customers get an overview of all the tickets they've *opened*. But some " +#| "teams use Zammad for both internal and public communication, so their " +#| "agents need both." msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" "Warum sollten Sie das wollen? Agenten erhalten :doc:`Übersichten ` über alle Tickets, denen sie *zugewiesen* sind (neben anderen " @@ -10084,9 +10162,13 @@ msgstr "" "Mitarbeiter beides benötigen." #: ../manage/roles/index.rst:25 +#, fuzzy +#| msgid "" +#| "Having both roles also changes what you see in the ticket view, depending " +#| "on whether you're the “customer” or not." msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" "Wenn Sie beide Rollen haben, ändert sich auch die Darstellung in der " "Ticketansicht, je nachdem, ob Sie der \"Kunde\" sind oder nicht." @@ -10096,9 +10178,13 @@ msgid "💡 **LDAP/Active Directory users:**" msgstr "💡 **LDAP/Active Directory-Benutzer:**" #: ../manage/roles/index.rst:30 +#, fuzzy +#| msgid "" +#| "Syncing your LDAP “groups” to Zammad roles can make access management " +#| "*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" "Die Synchronisierung Ihrer LDAP-\"Gruppen\" mit Zammad-Rollen kann die " "Zugriffsverwaltung *sehr* vereinfachen. Um mehr zu erfahren, siehe :doc:`/" @@ -10160,10 +10246,15 @@ msgid "create/edit knowledge base articles" msgstr "Anlegen/Bearbeiten von Knowledge Base Artikeln" #: ../manage/roles/index.rst:61 +#, fuzzy +#| msgid "" +#| "Zammad has dozens of these permissions, which is a lot to keep track of. " +#| "So instead of saying “This user has permissions A, B, and C”, Zammad says " +#| "“The *agent role* has permissions A, B, and C, and this user is an agent.”" msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" "Zammad hat Dutzende dieser Berechtigungen, und das ist eine Menge, die man " "im Auge behalten muss. Anstatt also zu sagen \"Dieser Benutzer hat die " @@ -10171,10 +10262,15 @@ msgstr "" "Berechtigungen A, B und C, und dieser Benutzer ist ein Agent.\"" #: ../manage/roles/index.rst:67 +#, fuzzy +#| msgid "" +#| "This makes creating user accounts for new agents a whole lot simpler, and " +#| "it also makes it easier to invent a new permission D and say “All " +#| "existing agents can do *that* now, too.”" msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" "Das macht das Anlegen von Benutzerkonten für neue Agenten viel einfacher, " "und es macht es auch einfacher, eine neue Berechtigung D zu erfinden und zu " @@ -10773,6 +10869,12 @@ msgstr "" "Emma erhält keine Benachrichtigung, wenn ihr die Tickets per Automatisierung " "zugewiesen werden." +#: ../manage/slas/how-do-they-work.rst:2 +#, fuzzy +#| msgid "How do they work?" +msgid "How do SLAs work" +msgstr "Wie funktionieren sie?" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -11180,6 +11282,12 @@ msgid "A ticket after the agents initial response and a customer response." msgstr "" "Ein Ticket nach der ersten Antwort des Agenten und einer Antwort des Kunden." +#: ../manage/slas/learn-by-example.rst:2 +#, fuzzy +#| msgid "example" +msgid "SLA example" +msgstr "Beispiel" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -11192,10 +11300,15 @@ msgstr "" "Bedürfnissen an!" #: ../manage/slas/learn-by-example.rst:10 +#, fuzzy +#| msgid "" +#| "If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-" +#| "do-they-work` to learn about all the options in detail, then come back " +#| "here to see them in action." msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" "Wenn sie für Sie keinen Sinn ergeben, machen Sie sich keine Sorgen – " "springen Sie einfach zu :doc:`how-do-they-work`, um mehr über alle Optionen " @@ -11230,7 +11343,9 @@ msgid "2nd Level" msgstr "2nd Level" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +#, fuzzy +#| msgid "**Attribtues**" +msgid "**Attributes**" msgstr "**Attribute**" #: ../manage/slas/learn-by-example.rst:22 @@ -12349,12 +12464,24 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "Screenshot der \"Trigger\" in den Einstellungen" +#: ../manage/trigger/how-do-they-work.rst:2 +#, fuzzy +#| msgid "How do they work?" +msgid "How do trigger work" +msgstr "Wie funktionieren sie?" + #: ../manage/trigger/how-do-they-work.rst:4 +#, fuzzy +#| msgid "" +#| "Triggers consist of three parts: **activators**, **conditions** and " +#| "**changes**. Activator defines “when the question is asked?”. Conditions " +#| "answer the question, “when should this trigger fire?” Changes answer the " +#| "question, “what should happen when it does?”" msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" "Trigger bestehen aus drei Teilen: **Aktivierungen**, **Bedingungen** und " "**Änderungen**. Die Aktivierung definiert \"wann wird die Ausführung geprüft?" @@ -12452,9 +12579,13 @@ msgstr "" "wurde, während die Priorität **1 niedrig** gesetzt war." #: ../manage/trigger/how-do-they-work.rst:47 +#, fuzzy +#| msgid "" +#| "**Time event** activator simply checks if **Conditions** match. This is " +#| "the same behavior as Action-based activator's „Always“ mode." msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" "Die Aktivierung mittels **Time event** prüft, ob die **Bedingungen** " "übereinstimmen. Dies ist das gleiche Verhalten wie der \"Immer\"-Modus der " @@ -12587,6 +12718,12 @@ msgstr "" "system/variables`, die zur Erstellung individueller Nachrichten verwendet " "werden können." +#: ../manage/trigger/learn-by-example.rst:2 +#, fuzzy +#| msgid "Triggers" +msgid "Trigger examples" +msgstr "Trigger" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -12596,8 +12733,13 @@ msgstr "" "Automatisierungen, die Sie mithilfe von Triggern einrichten können." #: ../manage/trigger/learn-by-example.rst:7 +#, fuzzy +#| msgid "" +#| "If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +#| "manage/trigger/how-do-they-work` to learn about all the options in " +#| "detail, then come back here to see them in action." msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -12613,9 +12755,14 @@ msgstr "" "\" zugewiesen werden:" #: ../manage/trigger/learn-by-example.rst:16 +#, fuzzy +#| msgid "" +#| "Emma Taylor is responsible for all sales internally, so if a new ticket " +#| "has the word “order” in the subject, assign it to her and make sure it’s " +#| "set with a high priority:" msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" "Emma Taylor ist intern für alle Verkäufe zuständig. Wenn also ein neues " @@ -12633,9 +12780,15 @@ msgid "📨 **Not all automated messages come from triggers!**" msgstr "📨 **Nicht alle automatischen Emails kommen von Triggern!**" #: ../manage/trigger/learn-by-example.rst:28 +#, fuzzy +#| msgid "" +#| "For instance, when *agents* receive a system email about a newly created " +#| "ticket, that’s built into the system itself. If you need to customize " +#| "those, you will have to :doc:`manually edit files on your server `." msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -12806,32 +12959,36 @@ msgid "Users" msgstr "Benutzer" #: ../manage/users/index.rst:4 +#, fuzzy +#| msgid "" +#| "Depending on your organization's IT capabilities, users can be managed " +#| "individually or in bulk, or even synchronized with third-party directory " +#| "services." msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" "Abhängig von den IT-Möglichkeiten Ihres Unternehmens können Benutzer einzeln " "oder mehrere gleichzeitig verwaltet oder sogar mit Verzeichnisdiensten von " "Drittanbietern synchronisiert werden." -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "Der einfachste Weg, Benutzer zu verwalten, ist direkt im Admin-Panel." -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "Erfahren Sie mehr über die Verwaltung von Benutzern..." -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr ":doc:`über das Admin-Panel `" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr ":doc: \"über einen CSV-Import " -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" @@ -12839,19 +12996,19 @@ msgstr "" ":doc:`über LDAP/Active Directory Integration `" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr ":doc:`über die Exchange-Integration `" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr ":docs:`über die REST API `" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "😲 **Kunden erhalten auch ihre eigenen Benutzerkonten?**" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." @@ -12859,23 +13016,28 @@ msgstr "" "Ja! Anders als z.B. OTRS speichert Zammad Konten für *alle*, die über das " "System kommunizieren." -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" "Warum? Es dient Dingen wie der Anzeige aller Tickets eines bestimmten Kunden." -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 +#, fuzzy +#| msgid "" +#| "How? Zammad checks the sender of every incoming message at every inbox it " +#| "monitors, and if it doesn't recognize the address, ✨ **poof**—new " +#| "customer account!" msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" "Und wie? Zammad überprüft den Absender jeder eingehenden Nachricht in allen " "Postfächern, die es überwacht, und wenn es die Adresse nicht erkennt: ✨ " "**puff** - neues Kundenkonto!" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" @@ -12884,11 +13046,11 @@ msgstr "" "sie es wollen, aber das Konto bleibt existieren, auch wenn sie es nie " "benutzen.)" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "Anleitung: Benutzerdetails" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." @@ -12897,24 +13059,18 @@ msgstr "" "selbsterklärend. Diejenigen, bei denen dies nicht der Fall ist, werden unten " "beschrieben." -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" "Der Dialog \"Benutzer bearbeiten\", der die verschiedenen Felder für " "Benutzerdetails anzeigt" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" "Details können im Dialogfeld **Neu/Bearbeiten Benutzer** festgelegt werden." -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" -"🕵️ **Administratoren sind nicht die einzigen, die diese Einstellungen ändern " -"können.**" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar ` oder der :user-docs:" "`Ticketansicht `)." -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "👤 Anmeldung" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -12942,7 +13098,7 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "Die Benutzerübersicht mit den Logins in der ersten Spalte" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." @@ -12950,7 +13106,7 @@ msgstr "" "Logins werden **nicht** im Dialogfeld \"Neu/Bearbeiten Benutzer\" angezeigt, " "aber sie sind in der Benutzerübersicht sichtbar." -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, oder den :doc:`CSV Import `." -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "🔑 Passwort" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." @@ -12973,15 +13129,15 @@ msgstr "" "Ja, Administratoren haben tatsächlich die Möglichkeit, die Kennwörter " "anderer Benutzer zu ändern." -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "(Die Agenten allerdings nicht.)" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "🏢 Organisation" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -12993,24 +13149,24 @@ msgstr "" "für dieses Unternehmen anzeigen oder spezielle :doc:`/manage/trigger` " "einrichten, die nur für diese Kunden ausgelöst werden." -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" "🚫 **Sie können einen Kunden nicht einer Organisation zuordnen, die noch " "nicht existiert.**" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" "Um eine Organisation hinzuzufügen, gehen Sie in den Einstellungen zu " "**Verwalten > Organisationen**." -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "🏤 Sekundäre Organisationen" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." @@ -13018,7 +13174,7 @@ msgstr "" "Mit dieser Option können Sie neben einer Hauptorganisation des Benutzers " "noch weitere Organisationen zuweisen." -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." @@ -13027,7 +13183,7 @@ msgstr "" "der Ausnahme, dass die Sekundärorganisation nicht so hervorgehoben wird wie " "die Primärorganisation." -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." @@ -13036,7 +13192,7 @@ msgstr "" "Zammad mischt Tickets mit gleicher Primär- oder Sekundärorganisation " "zusammen." -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." @@ -13044,11 +13200,11 @@ msgstr "" "Obwohl die Anzahl der sekundären Organisationen nicht begrenzt ist, sollten " "Sie die Anzahl der Organisationen auf ein vernünftiges Maß beschränken." -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "Maximal 30-40 Organisationen *sollten ausreichend* sein." -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -13065,25 +13221,29 @@ msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" "Ticketansicht, die den Avatar eines VIP-Benutzers mit einer Krone zeigt" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "VIPs werden mit einer Krone über ihren Avataren angezeigt." -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 +#, fuzzy +#| msgid "" +#| "😵 **Are you using the Note field to keep track of your own “custom” user " +#| "attributes?**" msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" "😵 **Nutzen Sie das Notizfeld, um Ihre eigenen \"benutzerdefinierten\" " "Benutzerattribute zu erfassen?**" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" "Möchten Sie Ihre eigenen Felder zum Dialogfeld \"Neu/Bearbeiten Benutzer\" " "hinzufügen?" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" @@ -13091,7 +13251,7 @@ msgstr "" "Das Deaktivieren ist eine Alternative zum Löschen eines Benutzers. Was ist " "genau der Unterschied?" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." @@ -13099,7 +13259,7 @@ msgstr "" "Es gibt keine Möglichkeit, einen gelöschten Benutzer wiederherzustellen. " "Inaktive Benutzer können jederzeit reaktiviert werden." -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." @@ -13108,7 +13268,7 @@ msgstr "" "verloren; bei der Deaktivierung eines Benutzers bleiben alle zugehörigen " "Tickets erhalten." -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "Inaktive Benutzer erscheinen weiterhin in den Suchergebnissen:" @@ -13116,15 +13276,19 @@ msgstr "Inaktive Benutzer erscheinen weiterhin in den Suchergebnissen:" msgid "An inactive user displayed in a customer search list" msgstr "Ein inaktiver Benutzer wird in einer Suche nach Kunden angezeigt" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 +#, fuzzy +#| msgid "" +#| "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +#| "users are greyed out." msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" "Ein durchgestrichenes 👤-Symbol weist auf einen inaktiven Benutzer hin. In " "anderen Fällen sind inaktive Benutzer ausgegraut." -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " @@ -13135,7 +13299,7 @@ msgstr "" "bearbeiten oder auf einen Teil des Admin-Bereichs zuzugreifen, sind Rollen " "die Lösung." -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -13156,7 +13320,7 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "Berechtigungen im Dialog \"Bearbeiten: Benutzer\"" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " @@ -13167,11 +13331,11 @@ msgstr "" "gehört. **Unten:** Die Gruppenzuordnung kann alternativ auch pro Benutzer " "festgelegt werden." -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "**🤔 Huh? Ich sehe die Tabelle mit den Gruppenberechtigungen nicht...**" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -13456,15 +13620,22 @@ msgstr "" "Webhooks sind für :doc:`/manage/trigger` und :doc:`/manage/scheduler` " "verfügbar." -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" -msgstr "Wie funktioniert das?" +#: ../manage/webhook.rst:20 +#, fuzzy +#| msgid "How do they work?" +msgid "How do Webhooks work" +msgstr "Wie funktionieren sie?" #: ../manage/webhook.rst:22 +#, fuzzy +#| msgid "" +#| "Under the hood, Zammad sends a POST request to a third-party URL (“API " +#| "endpoint”) you specify in the New Webhook dialog. The application server " +#| "behind this URL/endpoint must be configured to receive messages from " +#| "Zammad and handle the provided payload accordingly." msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -13499,7 +13670,9 @@ msgid "*all* associated articles" msgstr "*alle* zugehörigen Artikel" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +#, fuzzy +#| msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "jeweilige Benutzer (*z.B.* Absender von Artikeln, Besitzer usw.)" #: ../manage/webhook.rst:35 @@ -13544,7 +13717,9 @@ msgstr "" "für mehrere Trigger oder Automatisierungen verwenden." #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +#, fuzzy +#| msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "**🦻 Die Standard Zammad-Webhook-Payloads sind individuell**" #: ../manage/webhook/add.rst:9 @@ -13686,30 +13861,30 @@ msgstr "" "Standard is ``ja`` - wenn Sie unsichere selbstsignierte Zertifikate " "verwenden, setzen Sie diese Option auf ``nein``." -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "_`HTTP Basic Authentication Username`" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" "Legen Sie dies fest, wenn der Endpunkt HTTP basic authentication " "Zugangsdaten erfordert." -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "_`HTTP Basic Authentication Password`" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "Vordefinierter Webhook" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "Diese Funktion ist nur in **selbst gehosteten** Instanzen verfügbar!" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." @@ -13718,7 +13893,7 @@ msgstr "" "als Verweis auf einen vordefinierten Webhook. Es ist nicht möglich, dies für " "bestehende Webhooks zu ändern." -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -13732,11 +13907,11 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "Zusätzliche vordefinierte Webhook-Felder" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "_`Custom Payload`" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." @@ -13744,7 +13919,7 @@ msgstr "" "Standardmäßig ist diese Option ausgeschaltet - der Webhook sendet immer :ref:" "`webhook-payload-default` an den Endpunkt." -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -13759,7 +13934,7 @@ msgstr "" msgid "Custom payload code editor" msgstr "Editor Benutzerdefinierter Payload" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " @@ -13769,7 +13944,7 @@ msgstr "" "Editor wird Sie darauf hinweisen, wenn es ein Problem mit dem Code gibt. " "Außerdem ist es nicht möglich, eine ungültige JSON-Struktur zu speichern." -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." @@ -13777,7 +13952,7 @@ msgstr "" "Vordefinierte Webhooks bieten immer einen vordefinierten Payload, der für " "den zugehörigen Dienst spezifisch ist." -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." @@ -13786,7 +13961,7 @@ msgstr "" "Administratoren hinterlegen, damit der betreffende Webhook besser verstanden " "wird." -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." @@ -13794,7 +13969,7 @@ msgstr "" "Bei der Einstellung ``nicht aktiv`` kann der Webhook nicht mehr in Triggern " "oder Automatisierungen ausgewählt werden." -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -20266,6 +20441,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "Dialog zum Hinzufügen eines neuen Workflows" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "Wie funktionieren sie?" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -20725,6 +20904,10 @@ msgstr "" "ausgeführt. Das heißt, niedrigere Werte (z.B. ``100``) werden vor höheren (z." "B. ``999``) ausgeführt." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "Lernen Sie anhand eines Beispiels" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -21480,6 +21663,11 @@ msgstr "" "automatisch auf **hohe Priorität** und **weist sie charlie@chrispresso.com** " "zu." +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "Wie funktioniert das?" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" @@ -30256,6 +30444,21 @@ msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" "Zeigt an, welche Version derzeit auf Ihrer Zammad-Instanz verwendet wird." +#~ msgid "" +#~ "Depending on your organization’s IT capabilities, organizations can be " +#~ "managed individually or in bulk." +#~ msgstr "" +#~ "Abhängig von den IT-Fähigkeiten Ihrer Firma können Organisationen einzeln " +#~ "oder in großen Mengen verwaltet werden." + +#~ msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#~ msgstr "" +#~ "🕵️ **Administratoren sind nicht die einzigen, die diese Einstellungen " +#~ "ändern können.**" + +#~ msgid "Learn how to ..." +#~ msgstr "Lernen Sie ..." + #~ msgid "" #~ "The filters can be combined with each other as desired. The filters build " #~ "on each other, which means that they are further restricted per " diff --git a/locale/es/LC_MESSAGES/admin-docs.po b/locale/es/LC_MESSAGES/admin-docs.po index a10c433d..2bd8699e 100644 --- a/locale/es/LC_MESSAGES/admin-docs.po +++ b/locale/es/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2023-07-25 12:18+0000\n" "Last-Translator: ERICK HERNANDEZ HERNANDEZ Ñ " "\n" @@ -665,7 +665,7 @@ msgstr "" #: ../channels/email/accounts/account-setup.rst:156 #: ../channels/email/accounts/account-setup.rst:281 -#: ../manage/webhook/add.rst:72 ../settings/security/third-party/saml.rst:170 +#: ../manage/webhook/add.rst:74 ../settings/security/third-party/saml.rst:170 #: ../system/integrations/i-doit.rst:77 #, fuzzy msgid "SSL verification" @@ -1235,7 +1235,7 @@ msgstr "" #: ../channels/email/accounts/secondary-addresses.rst:42 #: ../manage/groups/settings.rst:96 ../manage/macros/how-do-they-work.rst:0 #: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:91 -#: ../manage/webhook/add.rst:118 +#: ../manage/webhook/add.rst:120 #: ../system/integrations/cti/includes/inbound-calls.include.rst:10 #: ../system/integrations/cti/includes/outbound-calls.include.rst:20 #: ../system/integrations/cti/includes/inbound-calls.include.rst:9 @@ -2576,7 +2576,7 @@ msgstr "" msgid "" "Feedback or contact forms are used on websites quite often. Usually they " "will generate an email which will be sent to somebody who forwards it and so " -"on. With Zammad it’s quite easy to integrate these forms into your website " +"on. With Zammad it's quite easy to integrate these forms into your website " "and directly generate tickets with them. In just 2 minutes." msgstr "" @@ -2634,7 +2634,7 @@ msgstr "" #: ../channels/form.rst:39 ../manage/groups/settings.rst:112 #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:94 ../manage/templates.rst:43 -#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:43 +#: ../manage/webhook/add.rst:129 ../system/integrations/i-doit.rst:43 msgid "Active" msgstr "" @@ -2688,7 +2688,7 @@ msgstr "" msgid "So let's talk about the options the designer provides." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:70 msgid "Title of the form" msgstr "" @@ -2702,7 +2702,7 @@ msgstr "" msgid "Default: ``Feedback Form``" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:75 msgid "Name of form submit button" msgstr "" @@ -2713,7 +2713,7 @@ msgid "" "form is shown." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:86 msgid "Message after sending form" msgstr "" @@ -2727,7 +2727,7 @@ msgstr "" msgid "Default *after* sending a form will look like so:" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:146 msgid "Options" msgstr "" @@ -2892,7 +2892,7 @@ msgid "" "apply Zammad's web form to your website. It basically consists of two parts." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:186 msgid "Header section" msgstr "" @@ -2914,7 +2914,7 @@ msgstr "" msgid "Do not mix jQuery versions - it's likely to break something." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:207 msgid "Body section" msgstr "" @@ -5341,13 +5341,13 @@ msgstr "" #: ../manage/calendars.rst:40 msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5747,8 +5747,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6233,7 +6233,10 @@ msgid "Macros" msgstr "Macros" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +#, fuzzy +#| msgid "" +#| "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" "Los macros son **🖱️ atajos de un clic** para aplicar cambios a un ticket." @@ -6275,14 +6278,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6297,7 +6297,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6310,35 +6310,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6346,54 +6346,53 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" -msgstr "" +#, fuzzy +#| msgid "Example" +msgid "Macro Example" +msgstr "Ejemplo" #: ../manage/macros/learn-by-example.rst:4 msgid "" @@ -6403,7 +6402,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6444,14 +6443,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6470,15 +6469,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6488,54 +6487,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6543,68 +6541,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6616,16 +6614,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6633,39 +6631,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6674,52 +6672,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6727,10 +6725,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7166,7 +7164,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8218,7 +8216,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8239,21 +8237,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8262,8 +8260,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8316,15 +8314,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8805,6 +8803,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9128,6 +9130,12 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +#, fuzzy +#| msgid "Example" +msgid "SLA example" +msgstr "Ejemplo" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9137,9 +9145,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9168,7 +9176,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -10095,12 +10103,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10174,7 +10186,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10278,6 +10290,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10286,7 +10302,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10298,7 +10314,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10313,7 +10329,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10448,92 +10464,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10555,38 +10566,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10594,48 +10605,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10647,39 +10658,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10687,20 +10698,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10714,18 +10725,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10942,15 +10953,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10975,7 +10985,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -11013,7 +11023,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11127,34 +11137,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11165,17 +11175,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11186,32 +11196,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16419,6 +16429,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16788,6 +16802,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17389,6 +17407,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/es_CO/LC_MESSAGES/admin-docs.po b/locale/es_CO/LC_MESSAGES/admin-docs.po index 9b04da19..6f46a7a8 100644 --- a/locale/es_CO/LC_MESSAGES/admin-docs.po +++ b/locale/es_CO/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -553,7 +553,7 @@ msgstr "" #: ../channels/email/accounts/account-setup.rst:156 #: ../channels/email/accounts/account-setup.rst:281 -#: ../manage/webhook/add.rst:72 ../settings/security/third-party/saml.rst:170 +#: ../manage/webhook/add.rst:74 ../settings/security/third-party/saml.rst:170 #: ../system/integrations/i-doit.rst:77 msgid "SSL verification" msgstr "" @@ -1114,7 +1114,7 @@ msgstr "" #: ../channels/email/accounts/secondary-addresses.rst:42 #: ../manage/groups/settings.rst:96 ../manage/macros/how-do-they-work.rst:0 #: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:91 -#: ../manage/webhook/add.rst:118 +#: ../manage/webhook/add.rst:120 #: ../system/integrations/cti/includes/inbound-calls.include.rst:10 #: ../system/integrations/cti/includes/outbound-calls.include.rst:20 #: ../system/integrations/cti/includes/inbound-calls.include.rst:9 @@ -2455,7 +2455,7 @@ msgstr "" msgid "" "Feedback or contact forms are used on websites quite often. Usually they " "will generate an email which will be sent to somebody who forwards it and so " -"on. With Zammad it’s quite easy to integrate these forms into your website " +"on. With Zammad it's quite easy to integrate these forms into your website " "and directly generate tickets with them. In just 2 minutes." msgstr "" @@ -2513,7 +2513,7 @@ msgstr "" #: ../channels/form.rst:39 ../manage/groups/settings.rst:112 #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:94 ../manage/templates.rst:43 -#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:43 +#: ../manage/webhook/add.rst:129 ../system/integrations/i-doit.rst:43 msgid "Active" msgstr "" @@ -2567,7 +2567,7 @@ msgstr "" msgid "So let's talk about the options the designer provides." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:70 msgid "Title of the form" msgstr "" @@ -2581,7 +2581,7 @@ msgstr "" msgid "Default: ``Feedback Form``" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:75 msgid "Name of form submit button" msgstr "" @@ -2592,7 +2592,7 @@ msgid "" "form is shown." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:86 msgid "Message after sending form" msgstr "" @@ -2606,7 +2606,7 @@ msgstr "" msgid "Default *after* sending a form will look like so:" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:146 msgid "Options" msgstr "" @@ -2771,7 +2771,7 @@ msgid "" "apply Zammad's web form to your website. It basically consists of two parts." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:186 msgid "Header section" msgstr "" @@ -2793,7 +2793,7 @@ msgstr "" msgid "Do not mix jQuery versions - it's likely to break something." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:207 msgid "Body section" msgstr "" @@ -5217,13 +5217,13 @@ msgstr "" #: ../manage/calendars.rst:40 msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5623,8 +5623,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6102,7 +6102,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6143,14 +6143,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6165,7 +6162,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6178,35 +6175,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6214,53 +6211,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6271,7 +6265,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6312,14 +6306,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6338,15 +6332,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6356,54 +6350,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6411,68 +6404,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6484,16 +6477,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6501,39 +6494,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6542,52 +6535,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6595,10 +6588,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7034,7 +7027,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8084,7 +8077,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8105,21 +8098,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8128,8 +8121,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8182,15 +8175,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8669,6 +8662,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -8992,6 +8989,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9001,9 +9002,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9032,7 +9033,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9958,12 +9959,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10037,7 +10042,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10141,6 +10146,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10149,7 +10158,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10161,7 +10170,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10176,7 +10185,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10311,92 +10320,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10418,38 +10422,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10457,48 +10461,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10510,39 +10514,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10550,20 +10554,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10577,18 +10581,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10805,15 +10809,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10838,7 +10841,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10876,7 +10879,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -10990,34 +10993,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11028,17 +11031,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11049,32 +11052,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16263,6 +16266,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16632,6 +16639,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17232,6 +17243,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/es_MX/LC_MESSAGES/admin-docs.po b/locale/es_MX/LC_MESSAGES/admin-docs.po index 15f737dc..21049d36 100644 --- a/locale/es_MX/LC_MESSAGES/admin-docs.po +++ b/locale/es_MX/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2023-10-11 14:18+0000\n" "Last-Translator: morealedgar \n" "Language-Team: Spanish (Mexico) determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5626,8 +5626,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6105,7 +6105,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6146,14 +6146,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6168,7 +6165,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6181,35 +6178,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6217,53 +6214,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6274,7 +6268,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6315,14 +6309,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6341,15 +6335,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6359,54 +6353,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6414,68 +6407,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6487,16 +6480,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6504,39 +6497,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6545,52 +6538,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6598,10 +6591,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7037,7 +7030,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8087,7 +8080,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8108,21 +8101,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8131,8 +8124,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8185,15 +8178,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8672,6 +8665,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -8995,6 +8992,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9004,9 +9005,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9035,7 +9036,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9961,12 +9962,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10040,7 +10045,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10144,6 +10149,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10152,7 +10161,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10164,7 +10173,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10179,7 +10188,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10314,92 +10323,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10421,38 +10425,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10460,48 +10464,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10513,39 +10517,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10553,20 +10557,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10580,18 +10584,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10808,15 +10812,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10841,7 +10844,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10879,7 +10882,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -10993,34 +10996,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11031,17 +11034,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11052,32 +11055,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16266,6 +16269,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16635,6 +16642,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17235,6 +17246,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/fa/LC_MESSAGES/admin-docs.po b/locale/fa/LC_MESSAGES/admin-docs.po index 45fc7f9f..f0396868 100644 --- a/locale/fa/LC_MESSAGES/admin-docs.po +++ b/locale/fa/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -553,7 +553,7 @@ msgstr "" #: ../channels/email/accounts/account-setup.rst:156 #: ../channels/email/accounts/account-setup.rst:281 -#: ../manage/webhook/add.rst:72 ../settings/security/third-party/saml.rst:170 +#: ../manage/webhook/add.rst:74 ../settings/security/third-party/saml.rst:170 #: ../system/integrations/i-doit.rst:77 msgid "SSL verification" msgstr "" @@ -1114,7 +1114,7 @@ msgstr "" #: ../channels/email/accounts/secondary-addresses.rst:42 #: ../manage/groups/settings.rst:96 ../manage/macros/how-do-they-work.rst:0 #: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:91 -#: ../manage/webhook/add.rst:118 +#: ../manage/webhook/add.rst:120 #: ../system/integrations/cti/includes/inbound-calls.include.rst:10 #: ../system/integrations/cti/includes/outbound-calls.include.rst:20 #: ../system/integrations/cti/includes/inbound-calls.include.rst:9 @@ -2455,7 +2455,7 @@ msgstr "" msgid "" "Feedback or contact forms are used on websites quite often. Usually they " "will generate an email which will be sent to somebody who forwards it and so " -"on. With Zammad it’s quite easy to integrate these forms into your website " +"on. With Zammad it's quite easy to integrate these forms into your website " "and directly generate tickets with them. In just 2 minutes." msgstr "" @@ -2513,7 +2513,7 @@ msgstr "" #: ../channels/form.rst:39 ../manage/groups/settings.rst:112 #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:94 ../manage/templates.rst:43 -#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:43 +#: ../manage/webhook/add.rst:129 ../system/integrations/i-doit.rst:43 msgid "Active" msgstr "" @@ -2567,7 +2567,7 @@ msgstr "" msgid "So let's talk about the options the designer provides." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:70 msgid "Title of the form" msgstr "" @@ -2581,7 +2581,7 @@ msgstr "" msgid "Default: ``Feedback Form``" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:75 msgid "Name of form submit button" msgstr "" @@ -2592,7 +2592,7 @@ msgid "" "form is shown." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:86 msgid "Message after sending form" msgstr "" @@ -2606,7 +2606,7 @@ msgstr "" msgid "Default *after* sending a form will look like so:" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:146 msgid "Options" msgstr "" @@ -2771,7 +2771,7 @@ msgid "" "apply Zammad's web form to your website. It basically consists of two parts." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:186 msgid "Header section" msgstr "" @@ -2793,7 +2793,7 @@ msgstr "" msgid "Do not mix jQuery versions - it's likely to break something." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:207 msgid "Body section" msgstr "" @@ -5217,13 +5217,13 @@ msgstr "" #: ../manage/calendars.rst:40 msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5623,8 +5623,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6102,7 +6102,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6143,14 +6143,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6165,7 +6162,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6178,35 +6175,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6214,53 +6211,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6271,7 +6265,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6312,14 +6306,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6338,15 +6332,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6356,54 +6350,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6411,68 +6404,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6484,16 +6477,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6501,39 +6494,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6542,52 +6535,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6595,10 +6588,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7034,7 +7027,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8084,7 +8077,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8105,21 +8098,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8128,8 +8121,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8182,15 +8175,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8669,6 +8662,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -8992,6 +8989,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9001,9 +9002,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9032,7 +9033,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9958,12 +9959,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10037,7 +10042,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10141,6 +10146,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10149,7 +10158,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10161,7 +10170,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10176,7 +10185,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10311,92 +10320,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10418,38 +10422,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10457,48 +10461,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10510,39 +10514,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10550,20 +10554,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10577,18 +10581,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10805,15 +10809,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10838,7 +10841,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10876,7 +10879,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -10990,34 +10993,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11028,17 +11031,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11049,32 +11052,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16263,6 +16266,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16632,6 +16639,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17232,6 +17243,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/fr/LC_MESSAGES/admin-docs.po b/locale/fr/LC_MESSAGES/admin-docs.po index ab5eea90..84d61165 100644 --- a/locale/fr/LC_MESSAGES/admin-docs.po +++ b/locale/fr/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2023-03-22 11:17+0000\n" "Last-Translator: Antoine Ducret \n" "Language-Team: French determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5717,8 +5717,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6196,7 +6196,10 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +#, fuzzy +#| msgid "" +#| "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" "Les macros sont des **commandes raccourcis** pour appliquer un changement " "sur un ticket." @@ -6239,14 +6242,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6261,7 +6261,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6274,35 +6274,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6310,54 +6310,52 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" -msgstr "" +#, fuzzy +msgid "Macro Example" +msgstr "exemple" #: ../manage/macros/learn-by-example.rst:4 msgid "" @@ -6367,7 +6365,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6408,14 +6406,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6434,15 +6432,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6452,54 +6450,53 @@ msgstr "Sociétés" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6507,69 +6504,69 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 #, fuzzy msgid "📢 Shared Organization" msgstr "Sociétés" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6581,16 +6578,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6598,39 +6595,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6639,52 +6636,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6692,10 +6689,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7131,7 +7128,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8183,7 +8180,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8204,21 +8201,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8227,8 +8224,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8281,15 +8278,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8769,6 +8766,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9094,6 +9095,12 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +#, fuzzy +#| msgid "example" +msgid "SLA example" +msgstr "exemple" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9103,9 +9110,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9134,8 +9141,9 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" -msgstr "" +#, fuzzy +msgid "**Attributes**" +msgstr "Variables Article" #: ../manage/slas/learn-by-example.rst:22 msgid "User / VIP (default, Boolean)" @@ -10062,12 +10070,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10141,7 +10153,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10245,6 +10257,12 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +#, fuzzy +#| msgid "example" +msgid "Trigger examples" +msgstr "exemple" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10253,7 +10271,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10265,7 +10283,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10280,7 +10298,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10415,92 +10433,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10522,38 +10535,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10561,49 +10574,49 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 #, fuzzy msgid "🏤 Secondary Organizations" msgstr "Sociétés" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10615,39 +10628,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10655,20 +10668,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10682,18 +10695,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10910,15 +10923,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10943,7 +10955,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10981,7 +10993,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11095,34 +11107,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11133,17 +11145,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11154,32 +11166,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16400,6 +16412,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16769,6 +16785,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17370,6 +17390,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/fr_CA/LC_MESSAGES/admin-docs.po b/locale/fr_CA/LC_MESSAGES/admin-docs.po index 0e2dadc3..05e07f14 100644 --- a/locale/fr_CA/LC_MESSAGES/admin-docs.po +++ b/locale/fr_CA/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2021-12-03 14:33+0000\n" "Last-Translator: TRANSFER FROM TRANSIFEX \n" "Language-Team: French (Canada) determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 #, fuzzy msgid "Group Permissions" msgstr "Groupe: Achats" @@ -5808,8 +5808,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6287,7 +6287,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6328,14 +6328,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6350,7 +6347,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6363,35 +6360,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6399,54 +6396,52 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" -msgstr "" +#, fuzzy +msgid "Macro Example" +msgstr "Exemple" #: ../manage/macros/learn-by-example.rst:4 msgid "" @@ -6456,7 +6451,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6497,14 +6492,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6523,15 +6518,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6541,55 +6536,54 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 #, fuzzy msgid "This is relevant to you? Consider domain based assignments." msgstr "Billet > Organisation > Affectation basée sur un domaine" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6597,68 +6591,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6670,17 +6664,17 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 #, fuzzy msgid "🗄️ Domain based assignment" msgstr "Billet > Organisation > Affectation basée sur un domaine" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6688,39 +6682,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6729,52 +6723,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6782,10 +6776,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7221,7 +7215,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8275,7 +8269,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8296,21 +8290,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8319,8 +8313,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8373,15 +8367,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8864,6 +8858,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9192,6 +9190,12 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +#, fuzzy +#| msgid "example" +msgid "SLA example" +msgstr "Exemple" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9201,9 +9205,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9232,8 +9236,10 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" -msgstr "" +#, fuzzy +#| msgid "Article attributes" +msgid "**Attributes**" +msgstr "Attributs d'article" #: ../manage/slas/learn-by-example.rst:22 msgid "User / VIP (default, Boolean)" @@ -10170,12 +10176,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10249,7 +10259,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10354,6 +10364,12 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +#, fuzzy +#| msgid "example" +msgid "Trigger examples" +msgstr "Exemple" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10362,7 +10378,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10374,7 +10390,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10389,7 +10405,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10524,92 +10540,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10631,38 +10642,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10670,48 +10681,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10723,39 +10734,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10763,20 +10774,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10790,18 +10801,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -11018,15 +11029,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -11051,7 +11061,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -11089,7 +11099,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11203,34 +11213,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11241,17 +11251,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11262,32 +11272,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16603,6 +16613,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16972,6 +16986,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17573,6 +17591,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/hr/LC_MESSAGES/admin-docs.po b/locale/hr/LC_MESSAGES/admin-docs.po index 22b35344..dde67f1c 100644 --- a/locale/hr/LC_MESSAGES/admin-docs.po +++ b/locale/hr/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2022-06-15 13:40+0000\n" "Last-Translator: Ivan Perovic \n" "Language-Team: Croatian determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5694,8 +5694,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6173,7 +6173,10 @@ msgid "Macros" msgstr "Makro-naredbe" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +#, fuzzy +#| msgid "" +#| "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" "Makro-naredbe su **🖱️prečac jednim klikom** kako bi izvršili promjene u " "ticketu." @@ -6216,14 +6219,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6238,7 +6238,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6251,35 +6251,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6287,54 +6287,53 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" -msgstr "" +#, fuzzy +#| msgid "Example" +msgid "Macro Example" +msgstr "Primjer" #: ../manage/macros/learn-by-example.rst:4 msgid "" @@ -6344,7 +6343,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6385,14 +6384,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6411,15 +6410,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6429,54 +6428,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6484,68 +6482,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6557,16 +6555,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6574,39 +6572,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6615,52 +6613,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6668,10 +6666,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7107,7 +7105,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8159,7 +8157,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8180,21 +8178,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8203,8 +8201,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8257,15 +8255,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8746,6 +8744,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9069,6 +9071,12 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +#, fuzzy +#| msgid "Example" +msgid "SLA example" +msgstr "Primjer" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9078,9 +9086,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9109,7 +9117,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -10036,12 +10044,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10115,7 +10127,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10219,6 +10231,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10227,7 +10243,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10239,7 +10255,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10254,7 +10270,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10389,92 +10405,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10496,38 +10507,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10535,48 +10546,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10588,39 +10599,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10628,20 +10639,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10655,18 +10666,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10883,15 +10894,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10916,7 +10926,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10954,7 +10964,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11068,34 +11078,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11106,17 +11116,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11127,32 +11137,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16351,6 +16361,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16720,6 +16734,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17320,6 +17338,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/hu/LC_MESSAGES/admin-docs.po b/locale/hu/LC_MESSAGES/admin-docs.po index 95219a72..7e11d276 100644 --- a/locale/hu/LC_MESSAGES/admin-docs.po +++ b/locale/hu/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -553,7 +553,7 @@ msgstr "" #: ../channels/email/accounts/account-setup.rst:156 #: ../channels/email/accounts/account-setup.rst:281 -#: ../manage/webhook/add.rst:72 ../settings/security/third-party/saml.rst:170 +#: ../manage/webhook/add.rst:74 ../settings/security/third-party/saml.rst:170 #: ../system/integrations/i-doit.rst:77 msgid "SSL verification" msgstr "" @@ -1114,7 +1114,7 @@ msgstr "" #: ../channels/email/accounts/secondary-addresses.rst:42 #: ../manage/groups/settings.rst:96 ../manage/macros/how-do-they-work.rst:0 #: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:91 -#: ../manage/webhook/add.rst:118 +#: ../manage/webhook/add.rst:120 #: ../system/integrations/cti/includes/inbound-calls.include.rst:10 #: ../system/integrations/cti/includes/outbound-calls.include.rst:20 #: ../system/integrations/cti/includes/inbound-calls.include.rst:9 @@ -2455,7 +2455,7 @@ msgstr "" msgid "" "Feedback or contact forms are used on websites quite often. Usually they " "will generate an email which will be sent to somebody who forwards it and so " -"on. With Zammad it’s quite easy to integrate these forms into your website " +"on. With Zammad it's quite easy to integrate these forms into your website " "and directly generate tickets with them. In just 2 minutes." msgstr "" @@ -2513,7 +2513,7 @@ msgstr "" #: ../channels/form.rst:39 ../manage/groups/settings.rst:112 #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:94 ../manage/templates.rst:43 -#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:43 +#: ../manage/webhook/add.rst:129 ../system/integrations/i-doit.rst:43 msgid "Active" msgstr "" @@ -2567,7 +2567,7 @@ msgstr "" msgid "So let's talk about the options the designer provides." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:70 msgid "Title of the form" msgstr "" @@ -2581,7 +2581,7 @@ msgstr "" msgid "Default: ``Feedback Form``" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:75 msgid "Name of form submit button" msgstr "" @@ -2592,7 +2592,7 @@ msgid "" "form is shown." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:86 msgid "Message after sending form" msgstr "" @@ -2606,7 +2606,7 @@ msgstr "" msgid "Default *after* sending a form will look like so:" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:146 msgid "Options" msgstr "" @@ -2771,7 +2771,7 @@ msgid "" "apply Zammad's web form to your website. It basically consists of two parts." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:186 msgid "Header section" msgstr "" @@ -2793,7 +2793,7 @@ msgstr "" msgid "Do not mix jQuery versions - it's likely to break something." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:207 msgid "Body section" msgstr "" @@ -5217,13 +5217,13 @@ msgstr "" #: ../manage/calendars.rst:40 msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5623,8 +5623,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6102,7 +6102,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6143,14 +6143,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6165,7 +6162,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6178,35 +6175,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6214,53 +6211,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6271,7 +6265,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6312,14 +6306,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6338,15 +6332,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6356,54 +6350,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6411,68 +6404,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6484,16 +6477,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6501,39 +6494,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6542,52 +6535,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6595,10 +6588,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7034,7 +7027,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8084,7 +8077,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8105,21 +8098,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8128,8 +8121,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8182,15 +8175,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8669,6 +8662,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -8992,6 +8989,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9001,9 +9002,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9032,7 +9033,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9958,12 +9959,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10037,7 +10042,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10141,6 +10146,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10149,7 +10158,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10161,7 +10170,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10176,7 +10185,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10311,92 +10320,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10418,38 +10422,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10457,48 +10461,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10510,39 +10514,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10550,20 +10554,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10577,18 +10581,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10805,15 +10809,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10838,7 +10841,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10876,7 +10879,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -10990,34 +10993,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11028,17 +11031,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11049,32 +11052,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16263,6 +16266,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16632,6 +16639,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17232,6 +17243,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/it/LC_MESSAGES/admin-docs.po b/locale/it/LC_MESSAGES/admin-docs.po index 1aad7e35..06a8137e 100644 --- a/locale/it/LC_MESSAGES/admin-docs.po +++ b/locale/it/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2023-04-15 10:17+0000\n" "Last-Translator: crnfpp \n" "Language-Team: Italian determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5642,8 +5642,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6121,7 +6121,10 @@ msgid "Macros" msgstr "Macros" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +#, fuzzy +#| msgid "" +#| "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" "Le Macros sono **🖱️ scorciatoie con un click** per applicare modifiche ad un " "ticket." @@ -6164,14 +6167,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6186,7 +6186,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6199,35 +6199,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6235,53 +6235,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6292,7 +6289,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6333,14 +6330,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6359,15 +6356,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6377,54 +6374,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6432,68 +6428,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6505,16 +6501,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6522,39 +6518,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6563,52 +6559,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6616,10 +6612,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7055,7 +7051,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8105,7 +8101,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8126,21 +8122,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8149,8 +8145,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8203,15 +8199,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8690,6 +8686,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9013,6 +9013,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9022,9 +9026,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9053,7 +9057,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9983,12 +9987,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10062,7 +10070,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10166,6 +10174,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10174,7 +10186,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10186,7 +10198,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10201,7 +10213,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10336,92 +10348,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10443,38 +10450,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10482,48 +10489,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10535,39 +10542,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10575,20 +10582,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10602,18 +10609,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10830,15 +10837,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10863,7 +10869,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10901,7 +10907,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11015,34 +11021,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11053,17 +11059,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11074,32 +11080,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16290,6 +16296,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16659,6 +16669,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17259,6 +17273,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/nl/LC_MESSAGES/admin-docs.po b/locale/nl/LC_MESSAGES/admin-docs.po index ed03b8d6..54a618b4 100644 --- a/locale/nl/LC_MESSAGES/admin-docs.po +++ b/locale/nl/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -553,7 +553,7 @@ msgstr "" #: ../channels/email/accounts/account-setup.rst:156 #: ../channels/email/accounts/account-setup.rst:281 -#: ../manage/webhook/add.rst:72 ../settings/security/third-party/saml.rst:170 +#: ../manage/webhook/add.rst:74 ../settings/security/third-party/saml.rst:170 #: ../system/integrations/i-doit.rst:77 msgid "SSL verification" msgstr "" @@ -1114,7 +1114,7 @@ msgstr "" #: ../channels/email/accounts/secondary-addresses.rst:42 #: ../manage/groups/settings.rst:96 ../manage/macros/how-do-they-work.rst:0 #: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:91 -#: ../manage/webhook/add.rst:118 +#: ../manage/webhook/add.rst:120 #: ../system/integrations/cti/includes/inbound-calls.include.rst:10 #: ../system/integrations/cti/includes/outbound-calls.include.rst:20 #: ../system/integrations/cti/includes/inbound-calls.include.rst:9 @@ -2455,7 +2455,7 @@ msgstr "" msgid "" "Feedback or contact forms are used on websites quite often. Usually they " "will generate an email which will be sent to somebody who forwards it and so " -"on. With Zammad it’s quite easy to integrate these forms into your website " +"on. With Zammad it's quite easy to integrate these forms into your website " "and directly generate tickets with them. In just 2 minutes." msgstr "" @@ -2513,7 +2513,7 @@ msgstr "" #: ../channels/form.rst:39 ../manage/groups/settings.rst:112 #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:94 ../manage/templates.rst:43 -#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:43 +#: ../manage/webhook/add.rst:129 ../system/integrations/i-doit.rst:43 msgid "Active" msgstr "" @@ -2567,7 +2567,7 @@ msgstr "" msgid "So let's talk about the options the designer provides." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:70 msgid "Title of the form" msgstr "" @@ -2581,7 +2581,7 @@ msgstr "" msgid "Default: ``Feedback Form``" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:75 msgid "Name of form submit button" msgstr "" @@ -2592,7 +2592,7 @@ msgid "" "form is shown." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:86 msgid "Message after sending form" msgstr "" @@ -2606,7 +2606,7 @@ msgstr "" msgid "Default *after* sending a form will look like so:" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:146 msgid "Options" msgstr "" @@ -2771,7 +2771,7 @@ msgid "" "apply Zammad's web form to your website. It basically consists of two parts." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:186 msgid "Header section" msgstr "" @@ -2793,7 +2793,7 @@ msgstr "" msgid "Do not mix jQuery versions - it's likely to break something." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:207 msgid "Body section" msgstr "" @@ -5217,13 +5217,13 @@ msgstr "" #: ../manage/calendars.rst:40 msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5623,8 +5623,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6102,7 +6102,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6143,14 +6143,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6165,7 +6162,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6178,35 +6175,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6214,53 +6211,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6271,7 +6265,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6312,14 +6306,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6338,15 +6332,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6356,54 +6350,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6411,68 +6404,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6484,16 +6477,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6501,39 +6494,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6542,52 +6535,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6595,10 +6588,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7034,7 +7027,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8084,7 +8077,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8105,21 +8098,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8128,8 +8121,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8182,15 +8175,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8669,6 +8662,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -8992,6 +8989,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9001,9 +9002,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9032,7 +9033,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9958,12 +9959,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10037,7 +10042,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10141,6 +10146,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10149,7 +10158,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10161,7 +10170,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10176,7 +10185,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10311,92 +10320,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10418,38 +10422,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10457,48 +10461,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10510,39 +10514,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10550,20 +10554,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10577,18 +10581,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10805,15 +10809,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10838,7 +10841,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10876,7 +10879,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -10990,34 +10993,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11028,17 +11031,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11049,32 +11052,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16263,6 +16266,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16632,6 +16639,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17232,6 +17243,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/pl/LC_MESSAGES/admin-docs.po b/locale/pl/LC_MESSAGES/admin-docs.po index 5aa95baa..683300f6 100644 --- a/locale/pl/LC_MESSAGES/admin-docs.po +++ b/locale/pl/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2023-09-23 01:11+0000\n" "Last-Translator: SamolJacek \n" "Language-Team: Polish determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5628,8 +5628,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6109,7 +6109,7 @@ msgstr "Makra" #: ../manage/macros.rst:4 #, fuzzy -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" "Makra to **🖱️ skróty za pomocą jednego kliknięcia** do wprowadzania zmian w " "zgłoszeniu." @@ -6152,14 +6152,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6174,7 +6171,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6187,35 +6184,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6223,54 +6220,52 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" -msgstr "" +#, fuzzy +msgid "Macro Example" +msgstr "Przykład" #: ../manage/macros/learn-by-example.rst:4 msgid "" @@ -6280,7 +6275,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6321,14 +6316,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6347,15 +6342,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6365,54 +6360,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6420,68 +6414,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6493,16 +6487,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6510,39 +6504,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6551,52 +6545,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6604,10 +6598,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7043,7 +7037,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8093,7 +8087,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8114,21 +8108,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8137,8 +8131,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8191,15 +8185,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8679,6 +8673,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9002,6 +9000,11 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +#, fuzzy +msgid "SLA example" +msgstr "Przykład" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9011,9 +9014,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9042,7 +9045,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9968,12 +9971,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10047,7 +10054,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10151,6 +10158,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10159,7 +10170,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10171,7 +10182,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10186,7 +10197,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10321,92 +10332,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10428,38 +10434,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10467,48 +10473,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10520,39 +10526,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10560,20 +10566,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10587,18 +10593,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10815,15 +10821,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10848,7 +10853,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10886,7 +10891,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11000,34 +11005,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11038,17 +11043,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11059,32 +11064,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16273,6 +16278,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16642,6 +16651,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17243,6 +17256,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/pt_BR/LC_MESSAGES/admin-docs.po b/locale/pt_BR/LC_MESSAGES/admin-docs.po index d0ee94de..83421ef4 100644 --- a/locale/pt_BR/LC_MESSAGES/admin-docs.po +++ b/locale/pt_BR/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2022-08-01 14:09+0000\n" "Last-Translator: Erico Cesar \n" "Language-Team: Portuguese (Brazil) determine a name, a time-zone, the business hours to be used for this " +#| "calendar and special holidays. In addition, you can subscribe to the " +#| "iCalendar, which will automatically load all holidays from Google " +#| "(updated once a day) ... and you can add a note." msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." @@ -5305,7 +5311,7 @@ msgstr "" "iCalendar, que irá carregar automaticamente todos os feriados do Google " "(atualizado uma vez por dia) ...e você pode adicionar uma nota." -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 #, fuzzy msgid "Group Permissions" msgstr "Permissões de objetos" @@ -5727,8 +5733,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 #, fuzzy msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" "\"sim\": o chamado irá permanecer com o último agente que era seu " "proprietário." @@ -6218,7 +6224,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6259,15 +6265,14 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" -msgstr "" +#, fuzzy +#| msgid "How does this work...?!" +msgid "How do macros work" +msgstr "Como isso funciona...?!" #: ../manage/macros/how-do-they-work.rst:4 msgid "" @@ -6281,7 +6286,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6294,35 +6299,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6330,54 +6335,52 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" -msgstr "" +#, fuzzy +msgid "Macro Example" +msgstr "**Por exemplo:**" #: ../manage/macros/learn-by-example.rst:4 msgid "" @@ -6387,7 +6390,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6428,14 +6431,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6454,15 +6457,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6472,55 +6475,54 @@ msgstr "Organizações" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 #, fuzzy msgid "😲 **Technical Limitations**" msgstr "Limitação" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6528,69 +6530,69 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 #, fuzzy msgid "📢 Shared Organization" msgstr "Organização" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6602,16 +6604,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6619,39 +6621,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6660,52 +6662,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6713,10 +6715,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7154,7 +7156,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8207,7 +8209,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "Papéis" @@ -8228,21 +8230,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8251,8 +8253,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8305,15 +8307,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8794,6 +8796,12 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +#, fuzzy +#| msgid "How does this work...?!" +msgid "How do SLAs work" +msgstr "Como isso funciona...?!" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9126,6 +9134,12 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +#, fuzzy +#| msgid "example" +msgid "SLA example" +msgstr "exemplo" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9135,9 +9149,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9167,8 +9181,10 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" -msgstr "" +#, fuzzy +#| msgid "Article attributes" +msgid "**Attributes**" +msgstr "Atributos do artigo" #: ../manage/slas/learn-by-example.rst:22 msgid "User / VIP (default, Boolean)" @@ -10125,12 +10141,17 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +#, fuzzy +msgid "How do trigger work" +msgstr "Funciona desta forma:" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10204,7 +10225,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10308,6 +10329,12 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +#, fuzzy +#| msgid "Triggers" +msgid "Trigger examples" +msgstr "Gatilhos" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10316,7 +10343,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10328,7 +10355,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10343,7 +10370,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10478,92 +10505,87 @@ msgstr "Usuários" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10585,38 +10607,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10624,49 +10646,49 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 #, fuzzy msgid "🏤 Secondary Organizations" msgstr "Organizações" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10678,39 +10700,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10718,20 +10740,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10745,18 +10767,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10973,15 +10995,16 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" -msgstr "" +#: ../manage/webhook.rst:20 +#, fuzzy +#| msgid "How does this work...?!" +msgid "How do Webhooks work" +msgstr "Como isso funciona...?!" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -11006,7 +11029,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -11044,7 +11067,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11159,34 +11182,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11197,17 +11220,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11218,32 +11241,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16483,6 +16506,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16852,6 +16879,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17453,6 +17484,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/ru/LC_MESSAGES/admin-docs.po b/locale/ru/LC_MESSAGES/admin-docs.po index 69557cdb..cec0501d 100644 --- a/locale/ru/LC_MESSAGES/admin-docs.po +++ b/locale/ru/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2023-09-09 23:18+0000\n" "Last-Translator: ElectroKos \n" "Language-Team: Russian determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5633,8 +5633,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6112,7 +6112,10 @@ msgid "Macros" msgstr "Макрос" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +#, fuzzy +#| msgid "" +#| "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" "Макрос это **🖱️ горячая клавиша** для внесения предопределённых изменений в " "билет." @@ -6155,14 +6158,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6177,7 +6177,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6190,35 +6190,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6226,53 +6226,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6283,7 +6280,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6324,14 +6321,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6350,15 +6347,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6368,54 +6365,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6423,68 +6419,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6496,16 +6492,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6513,39 +6509,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6554,52 +6550,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6607,10 +6603,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7046,7 +7042,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8096,7 +8092,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8117,21 +8113,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8140,8 +8136,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8194,15 +8190,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8681,6 +8677,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9004,6 +9004,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9013,9 +9017,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9044,7 +9048,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9970,12 +9974,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10049,7 +10057,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10153,6 +10161,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10161,7 +10173,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10173,7 +10185,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10188,7 +10200,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10323,92 +10335,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10430,38 +10437,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10469,48 +10476,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10522,39 +10529,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10562,20 +10569,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10589,18 +10596,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10817,15 +10824,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10850,7 +10856,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10888,7 +10894,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11002,34 +11008,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11040,17 +11046,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11061,32 +11067,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16275,6 +16281,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16644,6 +16654,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17244,6 +17258,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/sr/LC_MESSAGES/admin-docs.po b/locale/sr/LC_MESSAGES/admin-docs.po index c30b4592..f2c59c30 100644 --- a/locale/sr/LC_MESSAGES/admin-docs.po +++ b/locale/sr/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad Admin Documentation pre-release\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2023-11-23 02:10+0000\n" "Last-Translator: Dusan Vuckovic \n" "Language-Team: Serbian determine a name, a time-zone, the business hours to be used for this " +#| "calendar and special holidays. In addition, you can subscribe to the " +#| "iCalendar, which will automatically load all holidays from Google " +#| "(updated once a day) ... and you can add a note." msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." @@ -6359,7 +6371,7 @@ msgstr "" "који ће аутоматски учитавати све празнике са Google-а (ажурира се једном " "дневно) ... и можете додати напомену." -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "Групне дозволе" @@ -6843,9 +6855,13 @@ msgstr "" "ресетује власника на никога." #: ../manage/groups/settings.rst:62 +#, fuzzy +#| msgid "" +#| "The ticket will remain to the last agent who owned it. This is the " +#| "default value" msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" "Тикет ће остати последњем оператеру који га је поседовао. Ово је " "подразумевана вредност." @@ -7403,7 +7419,10 @@ msgid "Macros" msgstr "Макрои" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +#, fuzzy +#| msgid "" +#| "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "Макрои су **🖱 брзе пречице** за промене на тикета." #: ../manage/macros.rst:6 @@ -7455,14 +7474,15 @@ msgstr "" "панелу:" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +#, fuzzy +#| msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "Снимак екрана странице „Макрои“ у административном панелу" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#, fuzzy +#| msgid "How do they work?" +msgid "How do macros work" msgstr "Како то уствари функционише?" #: ../manage/macros/how-do-they-work.rst:4 @@ -7481,7 +7501,7 @@ msgstr "" "Постоји и неколико других подешавања која утичу на то ко може да користи " "макро или како се он понаша." -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "Додавање макроа" @@ -7494,27 +7514,27 @@ msgstr "Снимак екрана који приказује различите msgid "Actions" msgstr "Радње" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "Можете креирати радње за:" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "подешавање атрибута тикета (приоритет, стање, група, итд.)" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "додавање нових напомена у тикет" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "**Не постоје** радње за:" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "слање одговора клијенту" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." @@ -7522,9 +7542,13 @@ msgstr "" "За разлику од окидача, планера и текстуалних исечака, макро радње **не " "подржавају** употребу :doc:`/system/variables`." -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 +#, fuzzy +#| msgid "" +#| "If the ticket is missing a required attribute and the macro doesn’t set " +#| "it, then **no actions will be applied**." msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" "Ако тикету недостаје обавезни атрибут и макро га не подеси, онда **неће бити " @@ -7534,38 +7558,49 @@ msgstr "" msgid "Once completed..." msgstr "Када се заврши…" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 +#, fuzzy +#| msgid "" +#| "After running this macro, should Zammad remain on the current tab, close " +#| "it, or automatically switch to the next ticket? (Does not apply when " +#| "running macros “in bulk”.)" msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" "Након покретања овог макроа, да ли Zammad треба да остане у тренутном " "прозору, затвори га или аутоматски пређе на следећи тикет? (Не примењује се " "када се макрои покрећу „масовном радњом“.)" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 +#, fuzzy +#| msgid "" +#| "What should other Zammad admins know about this macro? (Visible only via " +#| "the “Edit: Macro” dialog, Rails console, and API.)" msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" "Шта други Zammad администратори треба да знају о овом макроу? (Видљиво само " "преко дијалога „Измена: Макро“, Rails конзоле и API-ја.)" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" "Који :doc:`групе ` смеју да виде/користе овај макро?" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +#, fuzzy +#| msgid "Choose “inactive” to disable this macro without deleting it." +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "Изаберите „искључено“ да бисте онемогућили овај макро без брисања." -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "Управљање макроима" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." @@ -7573,27 +7608,30 @@ msgstr "" "Можете да избришете или чак клонирате постојеће макрое у административном " "панелу под **Управљање > Макрои**." -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" "Снимак екрана који приказује додавање новог макроа путем клонирања и његово " "уклањање" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 +#, fuzzy +#| msgid "" +#| "When cloning a macro, you *must* click “Submit” for the duplicate to be " +#| "created." msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" "Када клонирате макро, *морате* кликнути на „Пошаљи“ да би се направио " "дупликат." #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" -msgstr "Учите на примеру" +#, fuzzy +#| msgid "Example" +msgid "Macro Example" +msgstr "Пример" #: ../manage/macros/learn-by-example.rst:4 msgid "" @@ -7604,8 +7642,13 @@ msgstr "" "можете подесити помоћу макроа." #: ../manage/macros/learn-by-example.rst:9 +#, fuzzy +#| msgid "" +#| "If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +#| "manage/macros/how-do-they-work` to learn about all the options in detail, " +#| "then come back here to see them in action." msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -7653,11 +7696,17 @@ msgstr "" "очистили нежељене тикете." #: ../manage/macros/learn-by-example.rst:29 +#, fuzzy +#| msgid "" +#| "If you want to set a ticket’s state to *pending reminder*, it’s usually a " +#| "two-step process—first select the state, then select a date. To always " +#| "set a reminder for the same, fixed amount of time (say, seven days " +#| "later), you can bundle the whole change into a macro:" msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" "Ако желите да подесите стање тикета на *чека на подсетник*, то је обично " "процес у два корака – прво изаберите стање, а затим изаберите датум. Да " @@ -7665,7 +7714,9 @@ msgstr "" "касније), можете да групишете целу измену у макро:" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +#, fuzzy +#| msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "„Одлагање тикета за 7 дана.” (🔒 видљиво само интерно)" #: ../manage/macros/learn-by-example.rst:35 @@ -7684,15 +7735,15 @@ msgstr "релативно / 7 / дан(а)" msgid "Screencast showing postpone macro configuration and behavior" msgstr "Снимак екрана који приказује подешавање и понашање макроа за одлагање" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "преко администраторског панела" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "преко CSV увоза" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "преко REST API-ја" @@ -7702,32 +7753,29 @@ msgstr "Организације" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -"У зависности од IT могућности ваше организације, организацијама се може " -"управљати појединачно или групно." -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "Додавање и уређивање корисника директно у панелу администратора" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" "Најједноставнији начин управљања организацијама је директно у " "администраторском панелу." -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "Сазнајте више о управљању организацијама..." -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "😲 **Техничка ограничења**" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." @@ -7735,7 +7783,7 @@ msgstr "" "Организације тренутно не могу да се уклоне. Једини изузетак је Zammad " "функција :doc:`/system/data-privacy`." -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." @@ -7744,7 +7792,7 @@ msgstr "" "Консултујте :doc:`референцу дозволa ` да " "бисте сазнали више." -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." @@ -7753,15 +7801,15 @@ msgstr "" "спољне синхронизације као што су LDAP или Exchange *не* подржавају мапирање " "организације." -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "Ово се односи на вас? Размотрите доделу на основу домена." -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "🥵 **ВЕЛИКЕ организације могу изазвати проблеме са перформансама**" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -7773,40 +7821,44 @@ msgstr "" "покрећу многа освежавања, на пример отварање тикета или честа комуникација. " "Много повезаних синхронизација података може да изазове додатне трошкове." -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "Наставите опрезно." -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "Референтни водич: детаљи организација" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 +#, fuzzy +#| msgid "" +#| "Most of the attributes you can set on organizations are self-explanatory. " +#| "The ones that aren’t are described below." msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" "Већина атрибута које можете поставити организацијама су сами по себи " "разумљиви. Они које нису описани су у наставку." -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" "Дијалог за уређивање организације, који приказује различита поља детаља о " "организацији" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" "Детаљи о организацији се могу подесити у дијалогу **Ново/Измена: " "Организација**." -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "🕵 **Администратори нису једини који могу да промене ова подешавања.**" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." @@ -7814,11 +7866,11 @@ msgstr "" "У већини случајева могу и оператери (користећи :user-docs:`панел тикета ` или страницу са детаљима о организацији)." -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "📢 Заједничка организација" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " @@ -7827,7 +7879,7 @@ msgstr "" "Ако ову опцију поставите на ``да``, сви чланови организације ће моћи да " "**виде** и **освежавају** тикете чланова исте организације поред својих." -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." @@ -7836,11 +7888,11 @@ msgstr "" "доступни само дељеним организацијама. Сазнајте више у секцији :doc:`/manage/" "overviews`." -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "Подразумевана вредност у дијалозима за додавање је ``да``." -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " @@ -7850,7 +7902,7 @@ msgstr "" "раде у истој Zammad инстанци. Заједничке организације су обично релевантне " "за фирме за подршку са прилично великим клијентима и контингентима подршке." -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -7866,18 +7918,18 @@ msgstr "" "Снимак екрана који приказује преглед „Тикети моје организације“ са тикетима\n" "свих чланова организације" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" "Чланови заједничке организације имају приступ прегледима заснованим на " "организацији" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "🗄 Додела на основу домена" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -7889,11 +7941,11 @@ msgstr "" "ваше напоре у одржавању и сматра се решењем за немогућност мапирања " "организација преко LDAP." -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "Подразумевана вредност у дијалогу за додавање је ``не``" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." @@ -7901,11 +7953,11 @@ msgstr "" "Додела на основу домена функционише само за *нове* кориснике и нема утицаја " "на постојеће кориснике." -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "🌐 Домен" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " @@ -7915,7 +7967,7 @@ msgstr "" "корисника да би се одредила додела. Ова опција припада додели на основу " "домена и потребна је ако је иста постављена на ``да``." -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " @@ -7925,11 +7977,11 @@ msgstr "" "и да проверите да за ове доделе не користите бесплатне имејл домене као што " "је ``gmail.com``." -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "👑 VIP" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -7942,50 +7994,63 @@ msgstr "" "manage/overviews>` само за VIP особе." #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +#, fuzzy +#| msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "Приказ тикета који приказује аватар VIP организације са круном на њему" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "VIP организације су приказане са круном изнад њихових аватара." -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "📑 Напомена" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "Напомене су видљиве свим члановима особља, **укључујући оператере**." -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 +#, fuzzy +#| msgid "" +#| "😵 **Are you using the Note field to keep track of your own “custom” " +#| "organization attributes?**" msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" "😵 **Да ли користите поље Напомена да бисте пратили сопствене „прилагођене“ " "атрибуте организације?**" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +#, fuzzy +#| msgid "" +#| "Wish you could add your own fields to the New/Edit Organization dialog?" +msgid "Wish you could add your own fields Organizations?" msgstr "Желите да додате сопствена поља у дијалог Новo/Измена: Организација?" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "Можете! Да бисте сазнали више, погледајте :doc:`/system/objects`." -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "Активно" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 +#, fuzzy +#| msgid "" +#| "Disabling this flag is a soft alternative to deleting an organization. So " +#| "what’s the difference?" msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" "Искључивање овог атрибута је мека алтернатива брисању организације. Па, у " "чему је разлика?" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." @@ -7993,7 +8058,7 @@ msgstr "" "Не постоји начин за враћање избрисане организације; искључене организације " "могу се поново укључити у било ком тренутку." -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "Искључене организације се и даље појављују у резултатима претраге:" @@ -8001,10 +8066,14 @@ msgstr "Искључене организације се и даље појав msgid "An inactive organization displayed in a quick search list" msgstr "Искључена организација приказана на листи брзе претраге" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 +#, fuzzy +#| msgid "" +#| "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " +#| "inactive organizations are greyed out." msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" "Пресечена иконица 🏢 означава искључену организацију. У другим случајевима, " "искључене организације су приказане у сивој боји." @@ -8542,8 +8611,8 @@ msgstr "" "унутар подешавања" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." -msgstr "Научите како да ..." +msgid "See here:" +msgstr "" #: ../manage/public-links.rst:14 msgid ":ref:`public_links_add_new`" @@ -9747,7 +9816,7 @@ msgstr "" "Да бисте то постигли, потребне су вам две одвојене улоге: једна са ``ticket." "agent`` и друга са ``ticket.customer``." -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "Улоге" @@ -9774,15 +9843,24 @@ msgstr "" "**Управљање > Улоге**." #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +#, fuzzy +#| msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "👀 Корисници могу имати и улоге „оператера” и „клијента” у исто време!" #: ../manage/roles/index.rst:18 +#, fuzzy +#| msgid "" +#| "Why would you want this? Agents get :doc:`overviews ` " +#| "of all the tickets they're *assigned to* (among other things), while " +#| "customers get an overview of all the tickets they've *opened*. But some " +#| "teams use Zammad for both internal and public communication, so their " +#| "agents need both." msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" "Зашто ми ово треба? Оператери имају приступ :doc:`прегледима ` свих тикета којима су *додељени* (између осталог), док клијенти " @@ -9791,9 +9869,13 @@ msgstr "" "оператерима требају оба." #: ../manage/roles/index.rst:25 +#, fuzzy +#| msgid "" +#| "Having both roles also changes what you see in the ticket view, depending " +#| "on whether you're the “customer” or not." msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" "Обе улоге такође мењају оно што видите у приказу тикета, у зависности од " "тога да ли сте „клијент” тикета или не." @@ -9803,9 +9885,13 @@ msgid "💡 **LDAP/Active Directory users:**" msgstr "💡 **Корисници LDAP/активног директоријума:**" #: ../manage/roles/index.rst:30 +#, fuzzy +#| msgid "" +#| "Syncing your LDAP “groups” to Zammad roles can make access management " +#| "*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" "Синхронизација ваших LDAP „група” са Zammad улогама може да олакша *начин* " "управљања приступом. Да бисте сазнали више, погледајте :doc:`/system/" @@ -9866,20 +9952,30 @@ msgid "create/edit knowledge base articles" msgstr "додају/уреде чланке базе знања" #: ../manage/roles/index.rst:61 +#, fuzzy +#| msgid "" +#| "Zammad has dozens of these permissions, which is a lot to keep track of. " +#| "So instead of saying “This user has permissions A, B, and C”, Zammad says " +#| "“The *agent role* has permissions A, B, and C, and this user is an agent.”" msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" "Zammad има на десетине ових дозвола, што је много за праћење. Дакле, уместо " "да каже „Овај корисник има дозволе A, B и C”, Zammad каже „*улога оператера* " "има дозволе A, B и C, а овај корисник је оператер.”" #: ../manage/roles/index.rst:67 +#, fuzzy +#| msgid "" +#| "This makes creating user accounts for new agents a whole lot simpler, and " +#| "it also makes it easier to invent a new permission D and say “All " +#| "existing agents can do *that* now, too.”" msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" "Ово чини додавање корисничких налога за нове оператере много једноставнијим, " "а такође олакшава измишљање нове дозволе D и изговарање „Сви постојећи " @@ -10454,6 +10550,12 @@ msgid "" "tickets." msgstr "Ема неће примати обавештења када јој планер додели ове тикете." +#: ../manage/slas/how-do-they-work.rst:2 +#, fuzzy +#| msgid "How do they work?" +msgid "How do SLAs work" +msgstr "Како то уствари функционише?" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -10850,6 +10952,12 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "Тикет након почетног одговора оператера и одговора корисника." +#: ../manage/slas/learn-by-example.rst:2 +#, fuzzy +#| msgid "example" +msgid "SLA example" +msgstr "пример" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -10861,10 +10969,15 @@ msgstr "" "морају да буду баш за вас!" #: ../manage/slas/learn-by-example.rst:10 +#, fuzzy +#| msgid "" +#| "If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-" +#| "do-they-work` to learn about all the options in detail, then come back " +#| "here to see them in action." msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" "Ако вам немају смисла, не брините – само прескочите на :doc:`how-do-they-" "work` да бисте детаљно сазнали о свим опцијама, а затим се вратите овде да " @@ -10898,7 +11011,9 @@ msgid "2nd Level" msgstr "2nd Level" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +#, fuzzy +#| msgid "**Attribtues**" +msgid "**Attributes**" msgstr "**Атрибути**" #: ../manage/slas/learn-by-example.rst:22 @@ -11988,12 +12103,24 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "Снимак екрана странице „Окидачи“ у административном панелу" +#: ../manage/trigger/how-do-they-work.rst:2 +#, fuzzy +#| msgid "How do they work?" +msgid "How do trigger work" +msgstr "Како то уствари функционише?" + #: ../manage/trigger/how-do-they-work.rst:4 +#, fuzzy +#| msgid "" +#| "Triggers consist of three parts: **activators**, **conditions** and " +#| "**changes**. Activator defines “when the question is asked?”. Conditions " +#| "answer the question, “when should this trigger fire?” Changes answer the " +#| "question, “what should happen when it does?”" msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" "Окидачи се састоје из три дела: **активације**, **услова** и **измена**. " "Активатор дефинише „када се поставља питање?“. Услови одговарају на питање " @@ -12087,9 +12214,13 @@ msgstr "" "је тикет премештен у другу групу док је приоритет подешен на **1 низак**." #: ../manage/trigger/how-do-they-work.rst:47 +#, fuzzy +#| msgid "" +#| "**Time event** activator simply checks if **Conditions** match. This is " +#| "the same behavior as Action-based activator's „Always“ mode." msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" "Активација **временског догађаја** једноставно проверава да ли се **услови** " "подударају. Ово је исто понашање као и режим „Увек“ активације засноване на " @@ -12216,6 +12347,12 @@ msgstr "" "`променљиве `, које се могу користити за израду високо " "прилагођених шаблона порука." +#: ../manage/trigger/learn-by-example.rst:2 +#, fuzzy +#| msgid "Triggers" +msgid "Trigger examples" +msgstr "Окидачи" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -12225,8 +12362,13 @@ msgstr "" "аутоматизације које можете подесити помоћу окидача." #: ../manage/trigger/learn-by-example.rst:7 +#, fuzzy +#| msgid "" +#| "If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +#| "manage/trigger/how-do-they-work` to learn about all the options in " +#| "detail, then come back here to see them in action." msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -12239,9 +12381,14 @@ msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" msgstr "Сваки пут када Jacob Smith отвори тикет, додели је Sales групи:" #: ../manage/trigger/learn-by-example.rst:16 +#, fuzzy +#| msgid "" +#| "Emma Taylor is responsible for all sales internally, so if a new ticket " +#| "has the word “order” in the subject, assign it to her and make sure it’s " +#| "set with a high priority:" msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" "Emma Taylor је одговорна за сву продају интерно, па ако нов тикет има реч " @@ -12259,9 +12406,15 @@ msgid "📨 **Not all automated messages come from triggers!**" msgstr "📨 **Не долазе све аутоматске поруке од окидача!**" #: ../manage/trigger/learn-by-example.rst:28 +#, fuzzy +#| msgid "" +#| "For instance, when *agents* receive a system email about a newly created " +#| "ticket, that’s built into the system itself. If you need to customize " +#| "those, you will have to :doc:`manually edit files on your server `." msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -12430,34 +12583,38 @@ msgid "Users" msgstr "Корисници" #: ../manage/users/index.rst:4 +#, fuzzy +#| msgid "" +#| "Depending on your organization's IT capabilities, users can be managed " +#| "individually or in bulk, or even synchronized with third-party directory " +#| "services." msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" "У зависности од IT могућности ваше организације, корисницима се може " "управљати појединачно или групно, или чак синхронизовати са услугама " "директоријума трећег лица." -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" "Најједноставнији начин управљања корисницима је директно у панелу " "администратора." -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "Сазнајте више о управљању корисницима..." -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr ":doc:`преко панела администратора `" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr ":doc:`преко CSV увоза `" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" @@ -12465,19 +12622,19 @@ msgstr "" ":doc:`преко LDAP/Active Directory интеграције `" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr ":doc:`преко Exchange интеграције `" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr ":docs:`преко REST API-ја `" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "😲 **Клијенти такође добијају сопствене корисничке налоге?**" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." @@ -12485,24 +12642,29 @@ msgstr "" "Да! За разлику од нпр. OTRS, Zammad треба да складишти налоге за *све* који " "комуницирају преко система." -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" "Зашто? Помаже нам да урадимо ствари као што је да покажемо све тикете " "одређеног клијента." -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 +#, fuzzy +#| msgid "" +#| "How? Zammad checks the sender of every incoming message at every inbox it " +#| "monitors, and if it doesn't recognize the address, ✨ **poof**—new " +#| "customer account!" msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" "Како? Zammad проверава пошиљаоца сваке долазне поруке у сваком пријемном " "сандучету које надгледа, а ако не препозна адресу, ✨ **пуф**—нови кориснички " "налог клијента!" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" @@ -12510,11 +12672,11 @@ msgstr "" "(Ваши клијенти никада не морају да постављају лозинку. Наравно, могу ако то " "желе, али налог ће постојати чак и ако га никада не користе.)" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "Референтни водич: Кориснички детаљи" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." @@ -12522,22 +12684,18 @@ msgstr "" "Већина атрибута које можете подесити на корисничким налозима је разумљива " "сама по себи. Они који нису описани су у наставку." -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" "Дијалог за уређивање корисника, који приказује различита поља са детаљима о " "кориснику" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" "Детаљи о кориснику се могу подесити у дијалогу **Ново/Измена: Корисник**." -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "🕵 **Администратори нису једини који могу да промене ова подешавања.**" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar ` или :user-docs:`панел тикета `)." -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "👤 Пријава" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -12565,7 +12723,7 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "Преглед корисника, који приказује пријаве у првој колони" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." @@ -12573,7 +12731,7 @@ msgstr "" "Корисничке пријаве **нису** приказане у дијалогу Ново/Измена: Корисник, али " "су видљиве из прегледа корисника." -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, :docs:`REST " "API `, или :doc:`CSV увоз `." -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "🔑 Лозинка" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" "Да, администратори заиста имају моћ да мењају лозинке других корисника." -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "(Оператери, међутим, немају.)" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "🏢 Организација" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -12614,23 +12772,23 @@ msgstr "" "видите све тикете те фирме или да подесите посебне :doc:`окидаче ` који се активирају само за те клијенте." -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" "🚫 **Не можете да доделите клијента организацији која још увек не постоји.**" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" "Да бисте је додали, идите на **Управљање > Организације** у панелу " "администратора." -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "🏤 Додатне организације" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." @@ -12638,7 +12796,7 @@ msgstr "" "Ова опција вам омогућава да доделите више организација, поред примарне " "организације корисника." -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." @@ -12646,7 +12804,7 @@ msgstr "" "Додатне организације се понашају исто као и примарне са једним изузетком: " "додатне организације нису толико истакнуте као примарне." -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." @@ -12654,7 +12812,7 @@ msgstr "" "Ово не утиче на листе за све организационе тикете. Zammad ће комбиновати " "тикете примарне и додатне организације." -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." @@ -12662,11 +12820,11 @@ msgstr "" "Иако број додатних организација није директно ограничен, можда бисте желели " "да ово задржите на разумном броју." -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "30-40 организација *требало би* бити сасвим довољно." -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -12682,23 +12840,27 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "Приказ тикета који приказује аватар VIP корисника са круном на њему" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "VIP особе су приказане са круном изнад њихових аватара." -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 +#, fuzzy +#| msgid "" +#| "😵 **Are you using the Note field to keep track of your own “custom” user " +#| "attributes?**" msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" "😵 **Да ли користите поље напомене да бисте пратили сопствене „прилагођене“ " "корисничке атрибуте?**" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "Желите да додате сопствена поља у дијалог Ново/Измена: Корисник?" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" @@ -12706,7 +12868,7 @@ msgstr "" "Онемогућавање овог атрибута је мека алтернатива брисању корисника. Па у чему " "је разлика?" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." @@ -12714,7 +12876,7 @@ msgstr "" "Не постоји начин да вратите избрисаног корисника; искључени корисници се " "могу поново укључити у било ком тренутку." -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." @@ -12722,7 +12884,7 @@ msgstr "" "Када се корисник избрише, губе се и сви повезани тикети; искључивање " "корисника задржава све повезане тикете нетакнуте." -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "Искључени корисници се и даље појављују у резултатима претраге:" @@ -12730,15 +12892,19 @@ msgstr "Искључени корисници се и даље појављуј msgid "An inactive user displayed in a customer search list" msgstr "Искључен корисник приказан на листи резулата претраге клијената" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 +#, fuzzy +#| msgid "" +#| "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " +#| "users are greyed out." msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" "Пресечена иконица 👤 означава искљученог корисника. У другим случајевима, " "искључени корисници су засивљени." -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " @@ -12748,7 +12914,7 @@ msgstr "" "Ако желите да некоме дате дозволе за уређивање базе знача или за приступ " "панелу администратора, улоге вам могу помоћи у томе." -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -12767,7 +12933,7 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "Дозволе у дијалогу за уређивање корисника" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " @@ -12777,11 +12943,11 @@ msgstr "" "којим :doc:`групама ` припадају. **При дну:** Групне " "доделе се могу алтернативно подесити по кориснику." -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "**🤔 Хм? Не видим табелу за приступ на основу групе…**" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -13063,15 +13229,22 @@ msgstr "" "Повратни позиви су доступни за :doc:`окидаче ` и :doc:" "`планере `." -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +#, fuzzy +#| msgid "How do they work?" +msgid "How do Webhooks work" msgstr "Како то уствари функционише?" #: ../manage/webhook.rst:22 +#, fuzzy +#| msgid "" +#| "Under the hood, Zammad sends a POST request to a third-party URL (“API " +#| "endpoint”) you specify in the New Webhook dialog. The application server " +#| "behind this URL/endpoint must be configured to receive messages from " +#| "Zammad and handle the provided payload accordingly." msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -13103,7 +13276,9 @@ msgid "*all* associated articles" msgstr "*сви* повезани чланци" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +#, fuzzy +#| msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "повезани корисници (*нпр.* пошиљаоци чланака, власници, итд.)" #: ../manage/webhook.rst:35 @@ -13147,7 +13322,9 @@ msgstr "" "специфичну путању за неколико окидача или планера." #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +#, fuzzy +#| msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "**🦻 Подразумевани подаци Zammad повратног позива су специфични**" #: ../manage/webhook/add.rst:9 @@ -13286,28 +13463,28 @@ msgstr "" "Подразумевано је ``да`` - ако користите небезбедне самопотписане " "сертификате, подесите ову опцију на ``не``." -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "_`HTTP basic auth корисник`" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "Подесите ово ако путања захтева HTTP basic auth акредитиве." -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "_`HTTP basic auth лозинка`" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "Повратни позив по шаблону" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "Ово поље је доступно само за повратне позиве по шаблону!" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." @@ -13316,7 +13493,7 @@ msgstr "" "референца на шаблон повратног позива. Није могуће променити га за постојеће " "повратне позиве." -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -13330,11 +13507,11 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "Додатна поља повратног позива по шаблону" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "_`Прилагођени подаци`" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." @@ -13342,7 +13519,7 @@ msgstr "" "Подразумевано је искључено - повратни позив ће увек слати :ref:" "`подразумеване податке ` циљној путањи." -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -13357,7 +13534,7 @@ msgstr "" msgid "Custom payload code editor" msgstr "Уредник кода прилагођених података" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " @@ -13367,7 +13544,7 @@ msgstr "" "вас обавестити путем аутоматизованих савета ако постоји проблем са кодом. " "Такође, неће бити могуће сачувати неисправну JSON структуру." -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." @@ -13375,7 +13552,7 @@ msgstr "" "Унапред дефинисани повратни позиви ће увек обезбедити почетне прилагођене " "податке, специфичне за одговарајући сервис." -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." @@ -13383,7 +13560,7 @@ msgstr "" "Ако је потребно, можете оставити корисне информације другим Zammad " "администраторима да боље разумеју дотични повратни позив." -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." @@ -13391,7 +13568,7 @@ msgstr "" "Ако је подешено на ``искључено``, више не можете да изаберете повратни позив " "у оквиру радњи окидача или планера." -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -19654,6 +19831,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "Дијалог за додавање новог радног тока" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "Како то уствари функционише?" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -20095,6 +20276,10 @@ msgstr "" "Радни токови се процењују у узлазном редоследу према приоритету. Ово ѕначи " "да се ниже вредности (нпр. ``100``) процењују пре виших (нпр. ``999``)." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "Учите на примеру" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -20819,6 +21004,11 @@ msgstr "" "Ова прилагођена скрипта ће аутоматски поставити све тикете које отвара на " "**високи приоритет** и **доделити их на charlie@chrispresso.com**." +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "Како то уствари функционише?" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" @@ -29376,6 +29566,20 @@ msgstr "Верзија" msgid "Shows which version is currently being used on your Zammad-instance." msgstr "Приказује која верзија се користи тренутно на вашој Zammad инстанци." +#~ msgid "" +#~ "Depending on your organization’s IT capabilities, organizations can be " +#~ "managed individually or in bulk." +#~ msgstr "" +#~ "У зависности од IT могућности ваше организације, организацијама се може " +#~ "управљати појединачно или групно." + +#~ msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#~ msgstr "" +#~ "🕵 **Администратори нису једини који могу да промене ова подешавања.**" + +#~ msgid "Learn how to ..." +#~ msgstr "Научите како да ..." + #~ msgid "" #~ "The filters can be combined with each other as desired. The filters build " #~ "on each other, which means that they are further restricted per " diff --git a/locale/sv/LC_MESSAGES/admin-docs.po b/locale/sv/LC_MESSAGES/admin-docs.po index 1e506526..1cd09419 100644 --- a/locale/sv/LC_MESSAGES/admin-docs.po +++ b/locale/sv/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -553,7 +553,7 @@ msgstr "" #: ../channels/email/accounts/account-setup.rst:156 #: ../channels/email/accounts/account-setup.rst:281 -#: ../manage/webhook/add.rst:72 ../settings/security/third-party/saml.rst:170 +#: ../manage/webhook/add.rst:74 ../settings/security/third-party/saml.rst:170 #: ../system/integrations/i-doit.rst:77 msgid "SSL verification" msgstr "" @@ -1114,7 +1114,7 @@ msgstr "" #: ../channels/email/accounts/secondary-addresses.rst:42 #: ../manage/groups/settings.rst:96 ../manage/macros/how-do-they-work.rst:0 #: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:91 -#: ../manage/webhook/add.rst:118 +#: ../manage/webhook/add.rst:120 #: ../system/integrations/cti/includes/inbound-calls.include.rst:10 #: ../system/integrations/cti/includes/outbound-calls.include.rst:20 #: ../system/integrations/cti/includes/inbound-calls.include.rst:9 @@ -2455,7 +2455,7 @@ msgstr "" msgid "" "Feedback or contact forms are used on websites quite often. Usually they " "will generate an email which will be sent to somebody who forwards it and so " -"on. With Zammad it’s quite easy to integrate these forms into your website " +"on. With Zammad it's quite easy to integrate these forms into your website " "and directly generate tickets with them. In just 2 minutes." msgstr "" @@ -2513,7 +2513,7 @@ msgstr "" #: ../channels/form.rst:39 ../manage/groups/settings.rst:112 #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:94 ../manage/templates.rst:43 -#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:43 +#: ../manage/webhook/add.rst:129 ../system/integrations/i-doit.rst:43 msgid "Active" msgstr "" @@ -2567,7 +2567,7 @@ msgstr "" msgid "So let's talk about the options the designer provides." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:70 msgid "Title of the form" msgstr "" @@ -2581,7 +2581,7 @@ msgstr "" msgid "Default: ``Feedback Form``" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:75 msgid "Name of form submit button" msgstr "" @@ -2592,7 +2592,7 @@ msgid "" "form is shown." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:86 msgid "Message after sending form" msgstr "" @@ -2606,7 +2606,7 @@ msgstr "" msgid "Default *after* sending a form will look like so:" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:146 msgid "Options" msgstr "" @@ -2771,7 +2771,7 @@ msgid "" "apply Zammad's web form to your website. It basically consists of two parts." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:186 msgid "Header section" msgstr "" @@ -2793,7 +2793,7 @@ msgstr "" msgid "Do not mix jQuery versions - it's likely to break something." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:207 msgid "Body section" msgstr "" @@ -5217,13 +5217,13 @@ msgstr "" #: ../manage/calendars.rst:40 msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5623,8 +5623,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6102,7 +6102,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6143,14 +6143,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6165,7 +6162,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6178,35 +6175,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6214,53 +6211,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6271,7 +6265,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6312,14 +6306,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6338,15 +6332,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6356,54 +6350,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6411,68 +6404,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6484,16 +6477,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6501,39 +6494,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6542,52 +6535,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6595,10 +6588,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7034,7 +7027,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8084,7 +8077,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8105,21 +8098,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8128,8 +8121,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8182,15 +8175,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8669,6 +8662,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -8992,6 +8989,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9001,9 +9002,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9032,7 +9033,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9958,12 +9959,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10037,7 +10042,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10141,6 +10146,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10149,7 +10158,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10161,7 +10170,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10176,7 +10185,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10311,92 +10320,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10418,38 +10422,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10457,48 +10461,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10510,39 +10514,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10550,20 +10554,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10577,18 +10581,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10805,15 +10809,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10838,7 +10841,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10876,7 +10879,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -10990,34 +10993,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11028,17 +11031,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11049,32 +11052,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16263,6 +16266,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16632,6 +16639,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17232,6 +17243,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/th/LC_MESSAGES/admin-docs.po b/locale/th/LC_MESSAGES/admin-docs.po index ed218ea7..db8e2d1a 100644 --- a/locale/th/LC_MESSAGES/admin-docs.po +++ b/locale/th/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -553,7 +553,7 @@ msgstr "" #: ../channels/email/accounts/account-setup.rst:156 #: ../channels/email/accounts/account-setup.rst:281 -#: ../manage/webhook/add.rst:72 ../settings/security/third-party/saml.rst:170 +#: ../manage/webhook/add.rst:74 ../settings/security/third-party/saml.rst:170 #: ../system/integrations/i-doit.rst:77 msgid "SSL verification" msgstr "" @@ -1114,7 +1114,7 @@ msgstr "" #: ../channels/email/accounts/secondary-addresses.rst:42 #: ../manage/groups/settings.rst:96 ../manage/macros/how-do-they-work.rst:0 #: ../manage/macros/learn-by-example.rst:0 ../manage/scheduler.rst:91 -#: ../manage/webhook/add.rst:118 +#: ../manage/webhook/add.rst:120 #: ../system/integrations/cti/includes/inbound-calls.include.rst:10 #: ../system/integrations/cti/includes/outbound-calls.include.rst:20 #: ../system/integrations/cti/includes/inbound-calls.include.rst:9 @@ -2455,7 +2455,7 @@ msgstr "" msgid "" "Feedback or contact forms are used on websites quite often. Usually they " "will generate an email which will be sent to somebody who forwards it and so " -"on. With Zammad it’s quite easy to integrate these forms into your website " +"on. With Zammad it's quite easy to integrate these forms into your website " "and directly generate tickets with them. In just 2 minutes." msgstr "" @@ -2513,7 +2513,7 @@ msgstr "" #: ../channels/form.rst:39 ../manage/groups/settings.rst:112 #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:94 ../manage/templates.rst:43 -#: ../manage/webhook/add.rst:127 ../system/integrations/i-doit.rst:43 +#: ../manage/webhook/add.rst:129 ../system/integrations/i-doit.rst:43 msgid "Active" msgstr "" @@ -2567,7 +2567,7 @@ msgstr "" msgid "So let's talk about the options the designer provides." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:70 msgid "Title of the form" msgstr "" @@ -2581,7 +2581,7 @@ msgstr "" msgid "Default: ``Feedback Form``" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:75 msgid "Name of form submit button" msgstr "" @@ -2592,7 +2592,7 @@ msgid "" "form is shown." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:86 msgid "Message after sending form" msgstr "" @@ -2606,7 +2606,7 @@ msgstr "" msgid "Default *after* sending a form will look like so:" msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:146 msgid "Options" msgstr "" @@ -2771,7 +2771,7 @@ msgid "" "apply Zammad's web form to your website. It basically consists of two parts." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:186 msgid "Header section" msgstr "" @@ -2793,7 +2793,7 @@ msgstr "" msgid "Do not mix jQuery versions - it's likely to break something." msgstr "" -#: ../channels/form.rst:0 +#: ../channels/form.rst:207 msgid "Body section" msgstr "" @@ -5217,13 +5217,13 @@ msgstr "" #: ../manage/calendars.rst:40 msgid "" -"--> determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5623,8 +5623,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6102,7 +6102,7 @@ msgid "Macros" msgstr "" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6143,14 +6143,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6165,7 +6162,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6178,35 +6175,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6214,53 +6211,50 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" +msgid "Macro Example" msgstr "" #: ../manage/macros/learn-by-example.rst:4 @@ -6271,7 +6265,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6312,14 +6306,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6338,15 +6332,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6356,54 +6350,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6411,68 +6404,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6484,16 +6477,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6501,39 +6494,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6542,52 +6535,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6595,10 +6588,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7034,7 +7027,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8084,7 +8077,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8105,21 +8098,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8128,8 +8121,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8182,15 +8175,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8669,6 +8662,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -8992,6 +8989,10 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +msgid "SLA example" +msgstr "" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9001,9 +9002,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9032,7 +9033,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -9958,12 +9959,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10037,7 +10042,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10141,6 +10146,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10149,7 +10158,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10161,7 +10170,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10176,7 +10185,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10311,92 +10320,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10418,38 +10422,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10457,48 +10461,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10510,39 +10514,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10550,20 +10554,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10577,18 +10581,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10805,15 +10809,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10838,7 +10841,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10876,7 +10879,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -10990,34 +10993,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11028,17 +11031,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11049,32 +11052,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16263,6 +16266,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16632,6 +16639,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17232,6 +17243,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/tr/LC_MESSAGES/admin-docs.po b/locale/tr/LC_MESSAGES/admin-docs.po index a1d58207..384f4ef1 100644 --- a/locale/tr/LC_MESSAGES/admin-docs.po +++ b/locale/tr/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2021-12-03 14:33+0000\n" "Last-Translator: TRANSFER FROM TRANSIFEX \n" "Language-Team: Turkish determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 #, fuzzy msgid "Group Permissions" msgstr "🔓 İzinler" @@ -5891,10 +5891,11 @@ msgid "" msgstr "" #: ../manage/groups/settings.rst:62 +#, fuzzy msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" -msgstr "" +"The ticket will remain with the last agent who owned it. This is the default " +"value." +msgstr "*evet*: bilet yeniden açılacak." #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 #, fuzzy @@ -6381,7 +6382,10 @@ msgid "Macros" msgstr "Makrolar" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +#, fuzzy +#| msgid "" +#| "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" "Makrolar, değişiklikleri bir bilete uygulamak için **🖱️ tek tıklamalı " "kısayollardır**." @@ -6435,14 +6439,17 @@ msgstr "" "düzenleyebilirsiniz:" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +#, fuzzy +#| msgid "You can create or edit macros on the Macros page of the admin panel:" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" +"Yönetici panelinin Makrolar sayfasında makro oluşturabilir veya " +"düzenleyebilirsiniz:" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#, fuzzy +#| msgid "How do they work?" +msgid "How do macros work" msgstr "Nasıl çalışırlar?" #: ../manage/macros/how-do-they-work.rst:4 @@ -6457,7 +6464,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "Makrolar Oluşturmak" @@ -6470,35 +6477,35 @@ msgstr "" msgid "Actions" msgstr "Eylemler" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "Şunları için eylemler oluşturabilirsiniz:" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "bilet niteliklerini (öncelik, durum, grup vb.) ayarlamak" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "bir bilete yeni notlar eklemek" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6506,55 +6513,56 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" "Bu makroyu görmek/kullanmak için hangi :doc:`/manage/groups/index` izinli?" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +#, fuzzy +#| msgid "Choose “inactive” to disable this macro without deleting it." +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "Bu makroyu silmeden kaldırmak için \"pasifleştir\"i seçin." -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "Makro Yönetimi" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" -msgstr "Örnek ile öğren" +#, fuzzy +#| msgid "Example" +msgid "Macro Example" +msgstr "Örnek" #: ../manage/macros/learn-by-example.rst:4 msgid "" @@ -6563,11 +6571,19 @@ msgid "" msgstr "" #: ../manage/macros/learn-by-example.rst:9 +#, fuzzy +#| msgid "" +#| "If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +#| "manage/trigger/how-do-they-work` to learn about all the options in " +#| "detail, then come back here to see them in action." msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" +"Size mantıklı gelmiyorlarsa, endişelenmeyin; tüm seçenekleri ayrıntılı " +"olarak öğrenmek için :doc:`/manage/trigger/how-do-they-work` bölümüne " +"atlayın ve ardından buraya geri gelin, onları iş başında görün." #: ../manage/macros/learn-by-example.rst:14 msgid "" @@ -6605,14 +6621,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6631,15 +6647,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6649,56 +6665,55 @@ msgstr "Organizasyonlar" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 #, fuzzy msgid "😲 **Technical Limitations**" msgstr "Sınırlamalar" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 #, fuzzy msgid "This is relevant to you? Consider domain based assignments." msgstr "Bilet > Organizasyon > Alan adına göre atama" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6706,70 +6721,70 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 #, fuzzy msgid "Reference Guide: Organization Details" msgstr "Geçerli Kullanıcı > Organizasyon > Alan adı" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 #, fuzzy msgid "📢 Shared Organization" msgstr "🏢 Organizasyon" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6781,17 +6796,17 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 #, fuzzy msgid "🗄️ Domain based assignment" msgstr "Bilet > Organizasyon > Alan adına göre atama" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6799,39 +6814,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "👑 VIP" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6840,52 +6855,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "📑 Not" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "▶️ Aktif" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6893,10 +6908,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7345,7 +7360,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8452,7 +8467,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "Roller" @@ -8473,21 +8488,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8496,8 +8511,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8550,15 +8565,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -9044,6 +9059,12 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +#, fuzzy +#| msgid "How do they work?" +msgid "How do SLAs work" +msgstr "Nasıl çalışırlar?" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9376,6 +9397,12 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +#, fuzzy +#| msgid "example" +msgid "SLA example" +msgstr "örnek" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9384,11 +9411,19 @@ msgid "" msgstr "" #: ../manage/slas/learn-by-example.rst:10 +#, fuzzy +#| msgid "" +#| "If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +#| "manage/trigger/how-do-they-work` to learn about all the options in " +#| "detail, then come back here to see them in action." msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" +"Size mantıklı gelmiyorlarsa, endişelenmeyin; tüm seçenekleri ayrıntılı " +"olarak öğrenmek için :doc:`/manage/trigger/how-do-they-work` bölümüne " +"atlayın ve ardından buraya geri gelin, onları iş başında görün." #: ../manage/slas/learn-by-example.rst:14 msgid "" @@ -9417,8 +9452,10 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" -msgstr "" +#, fuzzy +#| msgid "Ticket Attributes" +msgid "**Attributes**" +msgstr "Bilet Nitelikleri" #: ../manage/slas/learn-by-example.rst:22 msgid "User / VIP (default, Boolean)" @@ -10413,12 +10450,18 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +#, fuzzy +#| msgid "How do they work?" +msgid "How do trigger work" +msgstr "Nasıl çalışırlar?" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10493,7 +10536,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10598,6 +10641,12 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +#, fuzzy +#| msgid "Learn by example" +msgid "Trigger examples" +msgstr "Örnek ile öğren" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10608,8 +10657,13 @@ msgstr "" "verilmiştir." #: ../manage/trigger/learn-by-example.rst:7 +#, fuzzy +#| msgid "" +#| "If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +#| "manage/trigger/how-do-they-work` to learn about all the options in " +#| "detail, then come back here to see them in action." msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10622,9 +10676,14 @@ msgid "Any time Jacob Smith creates a ticket, assign it to the Sales group:" msgstr "Jacob Smith bir bilet oluşturduğunda, onu Satış grubuna atayın:" #: ../manage/trigger/learn-by-example.rst:16 +#, fuzzy +#| msgid "" +#| "Emma Taylor is responsible for all sales internally, so if a new ticket " +#| "has the word “order” in the subject, assign it to her and make sure it’s " +#| "set with a high priority:" msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" "Emma Taylor dahili olarak tüm satışlardan sorumludur, bu nedenle yeni bir " @@ -10640,9 +10699,15 @@ msgid "📨 **Not all automated messages come from triggers!**" msgstr "📨 **Tüm otomatik mesajlar tetikleyicilerden gelmez!**" #: ../manage/trigger/learn-by-example.rst:28 +#, fuzzy +#| msgid "" +#| "For instance, when *agents* receive a system email about a newly created " +#| "ticket, that’s built into the system itself. If you need to customize " +#| "those, you will have to :doc:`manually edit files on your server `." msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10817,95 +10882,90 @@ msgstr "Kullanıcılar" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 #, fuzzy msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr ":doc:`Sistem > Entegrasyonlar `" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 #, fuzzy msgid ":doc:`via Exchange integration `" msgstr ":doc:`Sistem > Entegrasyonlar `" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 #, fuzzy msgid ":docs:`via REST API `" msgstr "`Sistem > API `_" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "👤 Giriş" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10927,38 +10987,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "🔑 Parola" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "🏢 Organizasyon" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10966,49 +11026,49 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 #, fuzzy msgid "🏤 Secondary Organizations" msgstr "🏢 Organizasyon" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -11020,39 +11080,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -11060,20 +11120,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -11087,19 +11147,19 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 #, fuzzy msgid "**🤔 Huh? I don't see the group access table...**" msgstr "🤔 **Pardon? Veri Gizliliği panelini göremedim...**" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -11320,15 +11380,16 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" -msgstr "Nasıl çalışır?" +#: ../manage/webhook.rst:20 +#, fuzzy +#| msgid "How do they work?" +msgid "How do Webhooks work" +msgstr "Nasıl çalışırlar?" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -11353,7 +11414,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -11392,7 +11453,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11507,34 +11568,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11545,17 +11606,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11566,32 +11627,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16941,6 +17002,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "Nasıl çalışırlar?" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -17311,6 +17376,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "Örnek ile öğren" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17927,6 +17996,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "Nasıl çalışır?" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-" diff --git a/locale/zh_Hans/LC_MESSAGES/admin-docs.po b/locale/zh_Hans/LC_MESSAGES/admin-docs.po index b73ad35d..4c685e29 100644 --- a/locale/zh_Hans/LC_MESSAGES/admin-docs.po +++ b/locale/zh_Hans/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-22 08:09+0100\n" +"POT-Creation-Date: 2023-11-24 11:01+0100\n" "PO-Revision-Date: 2023-08-14 12:18+0000\n" "Last-Translator: chen \n" "Language-Team: Chinese (Simplified) determine a name, a time-zone, the business hours to be used for this " +"Determine a name, a time-zone, the business hours to be used for this " "calendar and special holidays. In addition, you can subscribe to the " "iCalendar, which will automatically load all holidays from Google (updated " "once a day) ... and you can add a note." msgstr "" -#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:190 +#: ../manage/groups/access-levels.rst:2 ../manage/users/index.rst:189 msgid "Group Permissions" msgstr "" @@ -5684,8 +5684,8 @@ msgstr "" #: ../manage/groups/settings.rst:62 msgid "" -"The ticket will remain to the last agent who owned it. This is the default " -"value" +"The ticket will remain with the last agent who owned it. This is the default " +"value." msgstr "" #: ../manage/groups/settings.rst:65 ../misc/object-conditions/basics.rst:0 @@ -6163,7 +6163,7 @@ msgid "Macros" msgstr "宏" #: ../manage/macros.rst:4 -msgid "Macros are **🖱️ one-click shortcuts** for applying changes to a ticket." +msgid "Macros are **🖱️ one-click actions** for applying changes to a ticket." msgstr "" #: ../manage/macros.rst:6 @@ -6204,14 +6204,11 @@ msgid "You can create or edit macros on the Macros page of the admin panel:" msgstr "" #: ../manage/macros.rst:None -msgid "Screenshot of “Macros” page in admin panel" +msgid "Screenshot of \"Macros\" page in admin panel" msgstr "" #: ../manage/macros/how-do-they-work.rst:2 -#: ../manage/slas/how-do-they-work.rst:2 -#: ../manage/trigger/how-do-they-work.rst:2 -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +msgid "How do macros work" msgstr "" #: ../manage/macros/how-do-they-work.rst:4 @@ -6226,7 +6223,7 @@ msgid "" "it behaves." msgstr "" -#: ../manage/macros/how-do-they-work.rst:10 +#: ../manage/macros/how-do-they-work.rst:11 msgid "Creating Macros" msgstr "" @@ -6239,35 +6236,35 @@ msgstr "" msgid "Actions" msgstr "" -#: ../manage/macros/how-do-they-work.rst:18 +#: ../manage/macros/how-do-they-work.rst:19 msgid "You can create actions to:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:20 +#: ../manage/macros/how-do-they-work.rst:21 msgid "set ticket attributes (priority, state, group, etc.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:21 +#: ../manage/macros/how-do-they-work.rst:22 msgid "add new notes to a ticket" msgstr "" -#: ../manage/macros/how-do-they-work.rst:23 +#: ../manage/macros/how-do-they-work.rst:24 msgid "There are **no** actions for:" msgstr "" -#: ../manage/macros/how-do-they-work.rst:25 +#: ../manage/macros/how-do-they-work.rst:26 msgid "sending a reply to the customer" msgstr "" -#: ../manage/macros/how-do-they-work.rst:27 +#: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " "support the use of :doc:`/system/variables`." msgstr "" -#: ../manage/macros/how-do-they-work.rst:31 +#: ../manage/macros/how-do-they-work.rst:32 msgid "" -"If the ticket is missing a required attribute and the macro doesn’t set it, " +"If the ticket is missing a required attribute and the macro doesn't set it, " "then **no actions will be applied**." msgstr "" @@ -6275,54 +6272,53 @@ msgstr "" msgid "Once completed..." msgstr "" -#: ../manage/macros/how-do-they-work.rst:36 +#: ../manage/macros/how-do-they-work.rst:37 msgid "" "After running this macro, should Zammad remain on the current tab, close it, " "or automatically switch to the next ticket? (Does not apply when running " -"macros “in bulk”.)" +"macros \"in bulk\".)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:41 +#: ../manage/macros/how-do-they-work.rst:42 msgid "" "What should other Zammad admins know about this macro? (Visible only via the " -"“Edit: Macro” dialog, Rails console, and API.)" +"\"Edit: Macro\" dialog, Rails console, and API.)" msgstr "" -#: ../manage/macros/how-do-they-work.rst:45 +#: ../manage/macros/how-do-they-work.rst:46 msgid "Which :doc:`/manage/groups/index` are allowed to see/use this macro?" msgstr "" -#: ../manage/macros/how-do-they-work.rst:48 -msgid "Choose “inactive” to disable this macro without deleting it." +#: ../manage/macros/how-do-they-work.rst:49 +msgid "Choose \"inactive\" to disable this macro without deleting it." msgstr "" -#: ../manage/macros/how-do-they-work.rst:51 +#: ../manage/macros/how-do-they-work.rst:52 msgid "Managing Macros" msgstr "" -#: ../manage/macros/how-do-they-work.rst:53 +#: ../manage/macros/how-do-they-work.rst:54 msgid "" "You can delete or even clone existing macros in the Admin Panel under " "**Manage > Macros**." msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" "Screencast showing the creation of a new macro via cloning and its removal" msgstr "" -#: ../manage/macros/how-do-they-work.rst:60 +#: ../manage/macros/how-do-they-work.rst:61 msgid "" -"When cloning a macro, you *must* click “Submit” for the duplicate to be " +"When cloning a macro, you *must* click \"Submit\" for the duplicate to be " "created." msgstr "" #: ../manage/macros/learn-by-example.rst:2 -#: ../manage/slas/learn-by-example.rst:2 -#: ../manage/trigger/learn-by-example.rst:2 -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by example" -msgstr "" +#, fuzzy +#| msgid "Example" +msgid "Macro Example" +msgstr "例如" #: ../manage/macros/learn-by-example.rst:4 msgid "" @@ -6332,7 +6328,7 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:9 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/macros/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -6373,14 +6369,14 @@ msgstr "" #: ../manage/macros/learn-by-example.rst:29 msgid "" -"If you want to set a ticket’s state to *pending reminder*, it’s usually a " -"two-step process—first select the state, then select a date. To always set a " -"reminder for the same, fixed amount of time (say, seven days later), you can " -"bundle the whole change into a macro:" +"If you want to set a ticket's state to *pending reminder*, it's usually a " +"two-step process - first select the state, then select a date. To always set " +"a reminder for the same, fixed amount of time (say, seven days later), you " +"can bundle the whole change into a macro:" msgstr "" #: ../manage/macros/learn-by-example.rst:34 -msgid "“Postponing ticket for 7 days.” (🔒 internal visibility only)" +msgid "\"Postponing ticket for 7 days.\" (🔒 internal visibility only)" msgstr "" #: ../manage/macros/learn-by-example.rst:35 @@ -6399,15 +6395,15 @@ msgstr "" msgid "Screencast showing postpone macro configuration and behavior" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via CSV import" msgstr "" -#: ../manage/organizations/index.rst:16 +#: ../manage/organizations/index.rst:15 msgid "via REST API" msgstr "" @@ -6417,54 +6413,53 @@ msgstr "" #: ../manage/organizations/index.rst:4 msgid "" -"Depending on your organization’s IT capabilities, organizations can be " -"managed individually or in bulk." +"Organizations can be managed individually via UI, via CSV import or the API." msgstr "" -#: ../manage/organizations/index.rst:12 ../manage/users/index.rst:13 +#: ../manage/organizations/index.rst:11 ../manage/users/index.rst:12 msgid "Creating and editing users directly in the Admin Panel" msgstr "" -#: ../manage/organizations/index.rst:12 +#: ../manage/organizations/index.rst:11 msgid "" "The simplest way to manage organizations is directly in the Admin Panel." msgstr "" -#: ../manage/organizations/index.rst:14 +#: ../manage/organizations/index.rst:13 msgid "Learn more about managing organizations..." msgstr "" -#: ../manage/organizations/index.rst:23 +#: ../manage/organizations/index.rst:22 msgid "😲 **Technical Limitations**" msgstr "" -#: ../manage/organizations/index.rst:25 +#: ../manage/organizations/index.rst:24 msgid "" "Organizations currently cannot be removed. The only exception is Zammad's :" "doc:`/system/data-privacy` function." msgstr "" -#: ../manage/organizations/index.rst:27 +#: ../manage/organizations/index.rst:26 msgid "" "Unlike users, agents cannot just create new organizations. Check the :doc:" "`permission reference ` to learn more." msgstr "" -#: ../manage/organizations/index.rst:30 +#: ../manage/organizations/index.rst:29 msgid "" "Because of how organization references work with users, external syncs like " "LDAP or Exchange *do not* support organization mapping." msgstr "" -#: ../manage/organizations/index.rst:35 +#: ../manage/organizations/index.rst:34 msgid "This is relevant to you? Consider domain based assignments." msgstr "" -#: ../manage/organizations/index.rst:37 +#: ../manage/organizations/index.rst:36 msgid "🥵 **BIG organizations can cause performance issues**" msgstr "" -#: ../manage/organizations/index.rst:39 +#: ../manage/organizations/index.rst:38 msgid "" "Organizations with many members can cause a fairly high system load in some " "situations. This especially affects organizations whose members run many " @@ -6472,68 +6467,68 @@ msgid "" "linked data syncs may cause an overhead." msgstr "" -#: ../manage/organizations/index.rst:44 +#: ../manage/organizations/index.rst:43 msgid "Proceed with caution." msgstr "" -#: ../manage/organizations/index.rst:49 +#: ../manage/organizations/index.rst:48 msgid "Reference Guide: Organization Details" msgstr "" -#: ../manage/organizations/index.rst:51 +#: ../manage/organizations/index.rst:50 msgid "" "Most of the attributes you can set on organizations are self-explanatory. " -"The ones that aren’t are described below." +"The ones that aren't are described below." msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "" "The edit organization dialog, showing the various organization detail fields" msgstr "" -#: ../manage/organizations/index.rst:59 +#: ../manage/organizations/index.rst:58 msgid "User details can be set in the **New/Edit Organization** dialog." msgstr "" -#: ../manage/organizations/index.rst:61 -msgid "🕵️ **Admins aren’t the only ones who can change these settings.**" +#: ../manage/organizations/index.rst:60 ../manage/users/index.rst:59 +msgid "🕵️ **Admins aren't the only ones who can change these settings.**" msgstr "" -#: ../manage/organizations/index.rst:63 +#: ../manage/organizations/index.rst:62 msgid "" "In most cases, agents can, too (using the :user-docs:`ticket pane ` or organization detail page)." msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "📢 Shared Organization" msgstr "" -#: ../manage/organizations/index.rst:68 +#: ../manage/organizations/index.rst:67 msgid "" "If you set this option to ``yes``, all organization members will be able to " "**view** and **update** tickets of their organizational members in addition " "to their own." msgstr "" -#: ../manage/organizations/index.rst:72 +#: ../manage/organizations/index.rst:71 msgid "" "Setting this option to yes also provides access to overviews being available " "to shared organizations only. Learn more on :doc:`/manage/overviews`." msgstr "" -#: ../manage/organizations/index.rst:76 +#: ../manage/organizations/index.rst:75 msgid "The default value on creation dialogues is ``yes``." msgstr "" -#: ../manage/organizations/index.rst:80 +#: ../manage/organizations/index.rst:79 msgid "" "This can cause serious issues if you have e.g.human resources working in the " "same Zammad instance. Shared organizations usually are relevant for Support " "companies with fairly big customers and support contingents." msgstr "" -#: ../manage/organizations/index.rst:86 +#: ../manage/organizations/index.rst:85 msgid "" "Sharing organizations don't just affect customers, however, if you want to " "provide ticket access to agents, please see the :ref:`permission-guide`." @@ -6545,16 +6540,16 @@ msgid "" "belonging to all organization members" msgstr "" -#: ../manage/organizations/index.rst:95 +#: ../manage/organizations/index.rst:94 msgid "" "Members of shared organization have access to organization based overviews" msgstr "" -#: ../manage/organizations/index.rst:108 +#: ../manage/organizations/index.rst:107 msgid "🗄️ Domain based assignment" msgstr "" -#: ../manage/organizations/index.rst:98 +#: ../manage/organizations/index.rst:97 msgid "" "Activating domain based assignment will cause Zammad to automatically add " "newly created users to said organization. This can greatly reduce your " @@ -6562,39 +6557,39 @@ msgid "" "organizations via LDAP." msgstr "" -#: ../manage/organizations/index.rst:103 +#: ../manage/organizations/index.rst:102 msgid "The default value on creation dialogues is ``no``" msgstr "" -#: ../manage/organizations/index.rst:107 +#: ../manage/organizations/index.rst:106 msgid "" "Domain based assignment only works for *newly created* users and has no " "effect on existing users." msgstr "" -#: ../manage/organizations/index.rst:119 +#: ../manage/organizations/index.rst:118 msgid "🌐 Domain" msgstr "" -#: ../manage/organizations/index.rst:111 +#: ../manage/organizations/index.rst:110 msgid "" "Add the email domain of the organization with this option. It's being used " "on user creation to determine the assignment. This option belongs to domain " "based assignment and is required if set to ``yes``." msgstr "" -#: ../manage/organizations/index.rst:117 +#: ../manage/organizations/index.rst:116 msgid "" "At the time Zammad allows *one* domain per organization. You may also want " "to ensure to not use free mailer domains like ``gmail.com`` for these " "assignments." msgstr "" -#: ../manage/organizations/index.rst:132 ../manage/users/index.rst:131 +#: ../manage/organizations/index.rst:131 ../manage/users/index.rst:130 msgid "👑 VIP" msgstr "" -#: ../manage/organizations/index.rst:122 +#: ../manage/organizations/index.rst:121 msgid "" "This flag is a way for your team to indicate high-status organizations. Just " "as with customers, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -6603,52 +6598,52 @@ msgid "" msgstr "" #: ../manage/organizations/index.rst:0 -msgid "Ticket view showing a VIP organization’s avatar with a crown on it" +msgid "Ticket view showing a VIP organization's avatar with a crown on it" msgstr "" -#: ../manage/organizations/index.rst:132 +#: ../manage/organizations/index.rst:131 msgid "VIP organizations are displayed with a crown above their avatars." msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "📑 Note" msgstr "" -#: ../manage/organizations/index.rst:135 ../manage/users/index.rst:134 +#: ../manage/organizations/index.rst:134 ../manage/users/index.rst:133 msgid "Notes are visible to all staff members, **including agents**." msgstr "" -#: ../manage/organizations/index.rst:137 +#: ../manage/organizations/index.rst:136 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” " +"😵 **Are you using the Note field to keep track of your own \"custom\" " "organization attributes?**" msgstr "" -#: ../manage/organizations/index.rst:140 -msgid "Wish you could add your own fields to the New/Edit Organization dialog?" +#: ../manage/organizations/index.rst:139 +msgid "Wish you could add your own fields Organizations?" msgstr "" -#: ../manage/organizations/index.rst:142 ../manage/users/index.rst:141 +#: ../manage/organizations/index.rst:141 ../manage/users/index.rst:140 msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" -#: ../manage/organizations/index.rst:157 ../manage/users/index.rst:162 +#: ../manage/organizations/index.rst:156 ../manage/users/index.rst:161 msgid "▶️ Active" msgstr "" -#: ../manage/organizations/index.rst:145 +#: ../manage/organizations/index.rst:144 msgid "" "Disabling this flag is a soft alternative to deleting an organization. So " -"what’s the difference?" +"what's the difference?" msgstr "" -#: ../manage/organizations/index.rst:148 +#: ../manage/organizations/index.rst:147 msgid "" "There is no way to restore a deleted organization; inactive organizations " "can be reactivated at any time." msgstr "" -#: ../manage/organizations/index.rst:151 +#: ../manage/organizations/index.rst:150 msgid "Inactive organizations still appear in search results:" msgstr "" @@ -6656,10 +6651,10 @@ msgstr "" msgid "An inactive organization displayed in a quick search list" msgstr "" -#: ../manage/organizations/index.rst:157 +#: ../manage/organizations/index.rst:156 msgid "" "A slashed-out 🏢 icon indicates an inactive organization. In other cases, " -"inactive organizations are greyed out." +"inactive organizations are grayed out." msgstr "" #: ../manage/organizations/via-csv-import.rst:2 @@ -7095,7 +7090,7 @@ msgid "" msgstr "" #: ../manage/public-links.rst:18 -msgid "Learn how to ..." +msgid "See here:" msgstr "" #: ../manage/public-links.rst:14 @@ -8147,7 +8142,7 @@ msgid "" "the other with ``ticket.customer``." msgstr "" -#: ../manage/roles/index.rst:2 ../manage/users/index.rst:167 +#: ../manage/roles/index.rst:2 ../manage/users/index.rst:166 msgid "Roles" msgstr "" @@ -8168,21 +8163,21 @@ msgid "Assign user privileges in the Admin Panel, under **Manage > Roles**." msgstr "" #: ../manage/roles/index.rst:16 -msgid "👀 Users can have both “agent” and “customer” roles at the same time!" +msgid "Users can have both \"agent\" and \"customer\" roles at the same time!" msgstr "" #: ../manage/roles/index.rst:18 msgid "" "Why would you want this? Agents get :doc:`overviews ` of " -"all the tickets they're *assigned to* (among other things), while customers " -"get an overview of all the tickets they've *opened*. But some teams use " -"Zammad for both internal and public communication, so their agents need both." +"all the tickets they're *assigned to* (among others), while customers get an " +"overview of all the tickets they've *opened*. But some teams use Zammad for " +"both internal and public communication, so their agents need both." msgstr "" #: ../manage/roles/index.rst:25 msgid "" "Having both roles also changes what you see in the ticket view, depending on " -"whether you're the “customer” or not." +"whether you're the \"customer\" or not." msgstr "" #: ../manage/roles/index.rst:28 @@ -8191,8 +8186,8 @@ msgstr "" #: ../manage/roles/index.rst:30 msgid "" -"Syncing your LDAP “groups” to Zammad roles can make access management *way* " -"easier. To learn more, see :doc:`/system/integrations/ldap/index`." +"Syncing your LDAP \"groups\" to Zammad roles can make access management " +"*way* easier. To learn more, see :doc:`/system/integrations/ldap/index`." msgstr "" #: ../manage/roles/index.rst:37 @@ -8245,15 +8240,15 @@ msgstr "" #: ../manage/roles/index.rst:61 msgid "" "Zammad has dozens of these permissions, which is a lot to keep track of. So " -"instead of saying “This user has permissions A, B, and C”, Zammad says “The " -"*agent role* has permissions A, B, and C, and this user is an agent.”" +"instead of saying \"This user has permissions A, B, and C\", Zammad says " +"\"The *agent role* has permissions A, B, and C, and this user is an agent.\"" msgstr "" #: ../manage/roles/index.rst:67 msgid "" "This makes creating user accounts for new agents a whole lot simpler, and it " -"also makes it easier to invent a new permission D and say “All existing " -"agents can do *that* now, too.”" +"also makes it easier to invent a new permission D and say \"All existing " +"agents can do *that* now, too.\"" msgstr "" #: ../manage/roles/index.rst:71 @@ -8734,6 +8729,10 @@ msgid "" "tickets." msgstr "" +#: ../manage/slas/how-do-they-work.rst:2 +msgid "How do SLAs work" +msgstr "" + #: ../manage/slas/how-do-they-work.rst:4 msgid "" "You can define several independent SLAs, however, ensure to have no " @@ -9057,6 +9056,12 @@ msgstr "" msgid "A ticket after the agents initial response and a customer response." msgstr "" +#: ../manage/slas/learn-by-example.rst:2 +#, fuzzy +#| msgid "Example" +msgid "SLA example" +msgstr "例如" + #: ../manage/slas/learn-by-example.rst:4 msgid "" "This page contains some possible example configurations for a SLA we could " @@ -9066,9 +9071,9 @@ msgstr "" #: ../manage/slas/learn-by-example.rst:10 msgid "" -"If they don’t make sense to you, don’t worry—just skip ahead to :doc:`how-do-" -"they-work` to learn about all the options in detail, then come back here to " -"see them in action." +"If they don't make sense to you, don't worry - just skip ahead to :doc:`how-" +"do-they-work` to learn about all the options in detail, then come back here " +"to see them in action." msgstr "" #: ../manage/slas/learn-by-example.rst:14 @@ -9097,7 +9102,7 @@ msgid "2nd Level" msgstr "" #: ../manage/slas/learn-by-example.rst:23 -msgid "**Attribtues**" +msgid "**Attributes**" msgstr "" #: ../manage/slas/learn-by-example.rst:22 @@ -10023,12 +10028,16 @@ msgstr "" msgid "Screenshot of “Triggers” page in admin panel" msgstr "" +#: ../manage/trigger/how-do-they-work.rst:2 +msgid "How do trigger work" +msgstr "" + #: ../manage/trigger/how-do-they-work.rst:4 msgid "" "Triggers consist of three parts: **activators**, **conditions** and " -"**changes**. Activator defines “when the question is asked?”. Conditions " -"answer the question, “when should this trigger fire?” Changes answer the " -"question, “what should happen when it does?”" +"**changes**. Activator defines \"when the question is asked?\". Conditions " +"answer the question, \"when should this trigger fire?\" Changes answer the " +"question, \"what should happen when it does?\"" msgstr "" #: ../manage/trigger/how-do-they-work.rst:9 @@ -10102,7 +10111,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:47 msgid "" "**Time event** activator simply checks if **Conditions** match. This is the " -"same behavior as Action-based activator's „Always“ mode." +"same behavior as Action-based activator's „Always\" mode." msgstr "" #: ../manage/trigger/how-do-they-work.rst:50 @@ -10206,6 +10215,10 @@ msgid "" "variables`, which can be used to build highly-customized message templates." msgstr "" +#: ../manage/trigger/learn-by-example.rst:2 +msgid "Trigger examples" +msgstr "" + #: ../manage/trigger/learn-by-example.rst:4 msgid "" "To get you up and running quickly, here are some examples of the kinds of " @@ -10214,7 +10227,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:7 msgid "" -"If they don't make sense to you, don't worry—just skip ahead to :doc:`/" +"If they don't make sense to you, don't worry - just skip ahead to :doc:`/" "manage/trigger/how-do-they-work` to learn about all the options in detail, " "then come back here to see them in action." msgstr "" @@ -10226,7 +10239,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:16 msgid "" "Emma Taylor is responsible for all sales internally, so if a new ticket has " -"the word “order” in the subject, assign it to her and make sure it’s set " +"the word \"order\" in the subject, assign it to her and make sure it's set " "with a high priority:" msgstr "" @@ -10241,7 +10254,7 @@ msgstr "" #: ../manage/trigger/learn-by-example.rst:28 msgid "" "For instance, when *agents* receive a system email about a newly created " -"ticket, that’s built into the system itself. If you need to customize those, " +"ticket, that's built into the system itself. If you need to customize those, " "you will have to :doc:`manually edit files on your server `." msgstr "" @@ -10376,92 +10389,87 @@ msgstr "" #: ../manage/users/index.rst:4 msgid "" -"Depending on your organization's IT capabilities, users can be managed " -"individually or in bulk, or even synchronized with third-party directory " -"services." +"Users can be managed individually via UI, via API or even synchronized with " +"third-party directory services." msgstr "" -#: ../manage/users/index.rst:13 +#: ../manage/users/index.rst:12 msgid "The simplest way to manage users is directly in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid "Learn more about managing users..." msgstr "" -#: ../manage/users/index.rst:16 +#: ../manage/users/index.rst:15 msgid ":doc:`via the Admin Panel `" msgstr "" -#: ../manage/users/index.rst:17 +#: ../manage/users/index.rst:16 msgid ":doc:`via CSV import `" msgstr "" -#: ../manage/users/index.rst:18 +#: ../manage/users/index.rst:17 msgid "" ":doc:`via LDAP/Active Directory integration `" msgstr "" -#: ../manage/users/index.rst:19 +#: ../manage/users/index.rst:18 msgid ":doc:`via Exchange integration `" msgstr "" -#: ../manage/users/index.rst:20 +#: ../manage/users/index.rst:19 msgid ":docs:`via REST API `" msgstr "" -#: ../manage/users/index.rst:29 +#: ../manage/users/index.rst:28 msgid "😲 **Customers get their own user accounts, too?**" msgstr "" -#: ../manage/users/index.rst:31 +#: ../manage/users/index.rst:30 msgid "" "Yes! Unlike e.g. OTRS, Zammad needs to store accounts for *everyone* who " "communicates through the system." msgstr "" -#: ../manage/users/index.rst:34 +#: ../manage/users/index.rst:33 msgid "" "Why? It helps us do things like show all tickets from a certain customer." msgstr "" -#: ../manage/users/index.rst:36 +#: ../manage/users/index.rst:35 msgid "" "How? Zammad checks the sender of every incoming message at every inbox it " -"monitors, and if it doesn't recognize the address, ✨ **poof**—new customer " +"monitors, and if it doesn't recognize the address, ✨ **poof** - new customer " "account!" msgstr "" -#: ../manage/users/index.rst:41 +#: ../manage/users/index.rst:40 msgid "" "(Your customers never need to set a password. Of course, they can if they " "want to, but the account will be there even if they never use it.)" msgstr "" -#: ../manage/users/index.rst:48 +#: ../manage/users/index.rst:47 msgid "Reference Guide: User Details" msgstr "" -#: ../manage/users/index.rst:50 +#: ../manage/users/index.rst:49 msgid "" "Most of the attributes you can set on user accounts are self-explanatory. " "The ones that aren't are described below." msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "The edit user dialog, showing the various user detail fields" msgstr "" -#: ../manage/users/index.rst:58 +#: ../manage/users/index.rst:57 msgid "User details can be set in the **New/Edit User** dialog." msgstr "" -#: ../manage/users/index.rst:60 -msgid "🕵️ **Admins aren't the only ones who can change these settings.**" -msgstr "" - -#: ../manage/users/index.rst:62 +#: ../manage/users/index.rst:61 msgid "" "In most cases, agents can, too (using the :user-docs:`new ticket dialog `, :user-docs:`search bar `)." msgstr "" -#: ../manage/users/index.rst:83 +#: ../manage/users/index.rst:82 msgid "👤 Login" msgstr "" -#: ../manage/users/index.rst:69 +#: ../manage/users/index.rst:68 msgid "" "A user's email and login may differ, but **either one can be used to sign in." "**" @@ -10483,38 +10491,38 @@ msgstr "" msgid "The user overview, showing logins in the first column" msgstr "" -#: ../manage/users/index.rst:78 +#: ../manage/users/index.rst:77 msgid "" "User logins are **not** shown in the New/Edit User dialog, but they are " "visible from the user overview." msgstr "" -#: ../manage/users/index.rst:81 +#: ../manage/users/index.rst:80 msgid "" "This attribute **cannot** be set via the Admin Panel. Instead, use the :docs:" "`Zammad console `, the :docs:`REST API `, or :doc:`CSV import `." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "🔑 Password" msgstr "" -#: ../manage/users/index.rst:86 +#: ../manage/users/index.rst:85 msgid "" "Yes, administrators really do have the power to change other users' " "passwords." msgstr "" -#: ../manage/users/index.rst:88 +#: ../manage/users/index.rst:87 msgid "(Agents do not, though.)" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "🏢 Organization" msgstr "" -#: ../manage/users/index.rst:91 +#: ../manage/users/index.rst:90 msgid "" ":doc:`/manage/organizations/index` are a way to group customers together " "(usually, members of the same company). This allows you to do things like " @@ -10522,48 +10530,48 @@ msgid "" "that fire only for those customers." msgstr "" -#: ../manage/users/index.rst:96 +#: ../manage/users/index.rst:95 msgid "" "🚫 **You can't assign a customer to an organization that doesn't exist yet.**" msgstr "" -#: ../manage/users/index.rst:99 +#: ../manage/users/index.rst:98 msgid "To add one, go to **Manage > Organizations** in the Admin Panel." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "🏤 Secondary Organizations" msgstr "" -#: ../manage/users/index.rst:102 +#: ../manage/users/index.rst:101 msgid "" "This option allows you to assign more organizations, in addition to the " "user's primary organization." msgstr "" -#: ../manage/users/index.rst:105 +#: ../manage/users/index.rst:104 msgid "" "Secondary organizations behave the same like the primary ones with one " "exception: Secondaries are not as highlighted like their primaries." msgstr "" -#: ../manage/users/index.rst:110 +#: ../manage/users/index.rst:109 msgid "" "Listings for all organizational tickets are not affected by this. Zammad " "will mix primary and secondary organization tickets together." msgstr "" -#: ../manage/users/index.rst:115 +#: ../manage/users/index.rst:114 msgid "" "While the number of secondary organizations is not limited directly, you may " "want to keep this to a reasonable number of organizations." msgstr "" -#: ../manage/users/index.rst:118 +#: ../manage/users/index.rst:117 msgid "30-40 organizations at maximum *should* be good enough." msgstr "" -#: ../manage/users/index.rst:121 +#: ../manage/users/index.rst:120 msgid "" "This flag is a way for your team to indicate high-status customers. Just as " "with organizations, you can set up special :doc:`/manage/trigger`, :doc:`/" @@ -10575,39 +10583,39 @@ msgstr "" msgid "Ticket view showing a VIP user's avatar with a crown on it" msgstr "" -#: ../manage/users/index.rst:131 +#: ../manage/users/index.rst:130 msgid "VIPs are displayed with a crown above their avatars." msgstr "" -#: ../manage/users/index.rst:136 +#: ../manage/users/index.rst:135 msgid "" -"😵 **Are you using the Note field to keep track of your own “custom” user " +"😵 **Are you using the Note field to keep track of your own \"custom\" user " "attributes?**" msgstr "" -#: ../manage/users/index.rst:139 +#: ../manage/users/index.rst:138 msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:143 msgid "" "Disabling this flag is a soft alternative to deleting a user. So what's the " "difference?" msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:146 msgid "" "There is no way to restore a deleted user; inactive users can be reactivated " "at any time." msgstr "" -#: ../manage/users/index.rst:150 +#: ../manage/users/index.rst:149 msgid "" "When a user is deleted, all their associated tickets are lost, as well; " "deactivating a user keeps all associated tickets intact." msgstr "" -#: ../manage/users/index.rst:153 +#: ../manage/users/index.rst:152 msgid "Inactive users still appear in search results:" msgstr "" @@ -10615,20 +10623,20 @@ msgstr "" msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:159 +#: ../manage/users/index.rst:158 msgid "" "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive " -"users are greyed out." +"users are grayed out." msgstr "" -#: ../manage/users/index.rst:165 +#: ../manage/users/index.rst:164 msgid "" "The :doc:`/manage/roles/index` define what users can do in the system. If " "you need to grant someone privileges to edit the knowledge base or access " "part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:170 +#: ../manage/users/index.rst:169 msgid "" "The :doc:`/manage/groups/access-levels` define which tickets an agent can " "work with. If an agent is not receiving notifications for incoming tickets " @@ -10642,18 +10650,18 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:184 +#: ../manage/users/index.rst:183 msgid "" "**Top:** User's roles decide what kind of actions they can perform and " "which :doc:`groups ` they belong to. **Bottom:** Group " "assignments can alternately be set on a per-user basis." msgstr "" -#: ../manage/users/index.rst:188 +#: ../manage/users/index.rst:187 msgid "**🤔 Huh? I don't see the group access table...**" msgstr "" -#: ../manage/users/index.rst:190 +#: ../manage/users/index.rst:189 msgid "" "The group access table is only visible in **agent profiles**, when there is " "**more than one active group** in the system." @@ -10870,15 +10878,14 @@ msgid "" "scheduler`." msgstr "" -#: ../manage/webhook.rst:20 ../system/integrations/checkmk/api-reference.rst:32 -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../manage/webhook.rst:20 +msgid "How do Webhooks work" msgstr "" #: ../manage/webhook.rst:22 msgid "" -"Under the hood, Zammad sends a POST request to a third-party URL (“API " -"endpoint”) you specify in the New Webhook dialog. The application server " +"Under the hood, Zammad sends a POST request to a third-party URL (\"API " +"endpoint\") you specify in the New Webhook dialog. The application server " "behind this URL/endpoint must be configured to receive messages from Zammad " "and handle the provided payload accordingly." msgstr "" @@ -10903,7 +10910,7 @@ msgid "*all* associated articles" msgstr "" #: ../manage/webhook.rst:34 -msgid "associated users (*e.g.* article senders, owners, etc.)" +msgid "associated users (e.g. article senders, owners, etc.)" msgstr "" #: ../manage/webhook.rst:35 @@ -10941,7 +10948,7 @@ msgid "" msgstr "" #: ../manage/webhook/add.rst:7 -msgid "**🦻 Default Zammad webhook payloads are specific**" +msgid "**Default Zammad webhook payloads are specific**" msgstr "" #: ../manage/webhook/add.rst:9 @@ -11055,34 +11062,34 @@ msgid "" "this option to ``no``." msgstr "" -#: ../manage/webhook/add.rst:75 +#: ../manage/webhook/add.rst:77 msgid "_`HTTP Basic Authentication Username`" msgstr "" -#: ../manage/webhook/add.rst:75 ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:77 ../manage/webhook/add.rst:80 msgid "" "Set this if the endpoint requires HTTP basic authentication credentials." msgstr "" -#: ../manage/webhook/add.rst:78 +#: ../manage/webhook/add.rst:80 msgid "_`HTTP Basic Authentication Password`" msgstr "" -#: ../manage/webhook/add.rst:92 +#: ../manage/webhook/add.rst:94 msgid "Pre-defined Webhook" msgstr "" -#: ../manage/webhook/add.rst:81 +#: ../manage/webhook/add.rst:83 msgid "This field is only available for pre-defined webhooks!" msgstr "" -#: ../manage/webhook/add.rst:83 +#: ../manage/webhook/add.rst:85 msgid "" "This field is always disabled in the UI and serves only as a reference to a " "pre-defined webhook. It is not possible to change it for existing webhooks." msgstr "" -#: ../manage/webhook/add.rst:87 +#: ../manage/webhook/add.rst:89 msgid "" "Depending on the pre-defined webhook type, additional fields may be rendered " "below this one. They can be used for additional customization of the webhook " @@ -11093,17 +11100,17 @@ msgstr "" msgid "Additional pre-defined webhook fields" msgstr "" -#: ../manage/webhook/add.rst:114 +#: ../manage/webhook/add.rst:116 msgid "_`Custom Payload`" msgstr "" -#: ../manage/webhook/add.rst:95 +#: ../manage/webhook/add.rst:97 msgid "" "Defaults to off - webhook will always send :ref:`webhook-payload-default` to " "the target endpoint." msgstr "" -#: ../manage/webhook/add.rst:98 +#: ../manage/webhook/add.rst:100 msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" @@ -11114,32 +11121,32 @@ msgstr "" msgid "Custom payload code editor" msgstr "" -#: ../manage/webhook/add.rst:108 +#: ../manage/webhook/add.rst:110 msgid "" "Custom payload must be valid JSON syntax! Code editor will inform you via " "automated hints if there is an issue with the code. Also, it will not be " "possible to save an invalid JSON structure." msgstr "" -#: ../manage/webhook/add.rst:113 +#: ../manage/webhook/add.rst:115 msgid "" "Pre-defined webhooks will always provide an initial custom payload, specific " "for the associated service." msgstr "" -#: ../manage/webhook/add.rst:117 +#: ../manage/webhook/add.rst:119 msgid "" "If required you can leave useful information for other Zammad admins to " "understand the webhook in question better." msgstr "" -#: ../manage/webhook/add.rst:121 +#: ../manage/webhook/add.rst:123 msgid "" "If set to ``inactive`` you can no longer select the webhook within trigger " "or scheduler actions." msgstr "" -#: ../manage/webhook/add.rst:126 +#: ../manage/webhook/add.rst:128 msgid "" "Inactive webhooks used by triggers or schedulers will not be fired. If " "triggers or schedulers have other actions configured as well they will still " @@ -16328,6 +16335,10 @@ msgstr "" msgid "Dialogue for adding a new workflow" msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "" + #: ../system/core-workflows/how-do-they-work.rst:4 msgid "" "Core Workflows are executed according to their priority. If two workflows " @@ -16697,6 +16708,10 @@ msgid "" "lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by example" +msgstr "" + #: ../system/core-workflows/learn-by-example.rst:4 msgid "" "This page provides some basic examples for Core Workflows. Of course you can " @@ -17297,6 +17312,11 @@ msgid "" "priority** and **assign them to charlie@chrispresso.com**." msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "" + #: ../system/integrations/checkmk/api-reference.rst:34 msgid "" "There are two kinds of data you can pass to the API, both in the form of key-"