diff --git a/advanced/macros.rst b/advanced/macros.rst index d66609ce..9a45e9fe 100644 --- a/advanced/macros.rst +++ b/advanced/macros.rst @@ -9,9 +9,9 @@ macros can make the job a whole lot easier. .. note:: 🤔 **How do I make macros?** - You don’t – that’s the - :admin-docs:`administrator’s job `. - If you have an idea for a macro you’d like to use, + You don't - that's the + :admin-docs:`administrator's job `. + If you have an idea for a macro you'd like to use, your Zammad admin can probably make it happen. Macros can be applied in one of two ways: @@ -21,7 +21,7 @@ On a Single Ticket ------------------ The simplest way to apply a macro is to select it -from the **Update ᐱ** submenu in the Ticket View: +from the **Update ^** submenu in the Ticket View: .. figure:: /images/advanced/macros/macro-run-via-ticket-view.gif :width: 90% @@ -30,13 +30,13 @@ from the **Update ᐱ** submenu in the Ticket View: .. tip:: 💾 **Macro = Update** - If you’ve made changes to any other + If you've made changes to any other :ref:`settings on the ticket ` (including typing up a reply to the customer), applying a macro will save them, too. ⚠️ **But beware:** in the event of a conflict, - the macro’s actions override any manual changes – + the macro's actions override any manual changes - including messages to the customer! When in doubt, apply your macro and your manual changes *separately.* diff --git a/basics/find-ticket/search.rst b/basics/find-ticket/search.rst index 0729c6f0..e9dbc7b2 100644 --- a/basics/find-ticket/search.rst +++ b/basics/find-ticket/search.rst @@ -1,15 +1,15 @@ Search for Tickets ================== -Looking for an archived ticket? Use the **search bar**. +Looking for an a specific ticket? Use the **search bar**. .. figure:: /images/basics/find-ticket/search.png :align: center - :scale: 40% + :scale: 70% Results appear immediately under the search bar as you type. -.. hint:: It’s not just for tickets! Results cover 💬 **chat logs**, +.. hint:: It's not just for tickets! Results cover 💬 **chat logs**, 👨 **customers**, and 🏢 **organizations**, too. **🔍 Here are just a few of the places the search engine will look:** @@ -18,10 +18,10 @@ Looking for an archived ticket? Use the **search bar**. * 👩 recipient names & email addresses * 📎 text in file attachments (really!) * 🏷️ user/organization metadata (*e.g.,* notes stored on customer profiles) - + You can find a detailed search document in our `Advanced Search <../../advanced/search.html>`_ page. - + .. figure:: /images/basics/find-ticket/search-details.png :align: center diff --git a/basics/service-ticket.rst b/basics/service-ticket.rst index d6ae6e33..dd693ea7 100644 --- a/basics/service-ticket.rst +++ b/basics/service-ticket.rst @@ -1,9 +1,9 @@ Servicing Tickets ================= -This is where you’ll spend the vast majority of your time in Zammad. +This is where you'll spend the vast majority of your time in Zammad. -Once you get the hang of the tasks below, there’s really not much more to it. +Once you get the hang of the tasks below, there's really not much more to it. .. toctree:: :maxdepth: 1 diff --git a/basics/zammad-glossary.rst b/basics/zammad-glossary.rst index 02df92ed..c5c39a74 100644 --- a/basics/zammad-glossary.rst +++ b/basics/zammad-glossary.rst @@ -23,7 +23,7 @@ Admin Admins can configure user accesses, time recording settings, templates, and text modules and, on a higher level, integrations, reporting, etc. So if you're looking to make a change within your Zammad and you find that - it doesn't work, find an admin in your organization and ask them – chances + it doesn't work, find an admin in your organization and ask them - chances are, they can help. Agent @@ -35,17 +35,12 @@ Agent API An API (Application Programming Interface) is a connection that allows you to create or modify business objects. Zammad has a REST - (`Representational State Transfer`_) API that allows our users, - among other things, to connect third-party systems to their instance - (such as social media or messengers). - - You can learn more on our `API landing page`_. + (`Representational State Transfer `_) + API that allows our users, among other things, to connect third-party systems + to their instance (such as social media or messengers). -.. _Representational State Transfer: - https://en.wikipedia.org/wiki/Representational_state_transfer - -.. _API landing page: - https://zammad.com/en/product/features/rest-api + You can learn more on our + `API landing page `_. Automation There are many processes that can be automated with Zammad. @@ -61,12 +56,10 @@ Article Autosave Autosave might be one of the coolest traits of Zammad: It saves all your work as you go along, so if you ever log out unexpectedly - or your browser crashes (we’ve all been there…) none of your work gets lost! - - You can learn more on our `Autosave landing page`_. + or your browser crashes (we've all been there…) none of your work gets lost! -.. _Autosave landing page: - https://zammad.com/en/product/features/autosave + You can learn more on our + `Autosave landing page `_. B - @@ -94,26 +87,18 @@ Custom Development (CD) Changelog With every new release comes a new changelog. It is basically a list of all the things that have changed, from new enhancements to bug fixes. - - `You can find them all on our GitHub`_! -.. _You can find them all on our GitHub: - https://github.com/zammad/zammad/blob/stable/CHANGELOG.md + You can find them all on our `GitHub `_! Customer A customer is a person that you communicate with from within Zammad. Every customer receives a profile page, which we call the - `Customer Information Page`_, and it shows all the tickets of this particular - customer. + `Customer Information Page `_, + and it shows all the tickets of this particular customer. Various customers can be assigned to the same organization. - Each customer can access their individual `Customer Interface`_, where they - see all their tickets with the current status and live updates. - -.. _Customer Information Page: - https://user-docs.zammad.org/en/latest/extras/customers.html - -.. _Customer Interface: - https://zammad.com/en/product/features/customer-interface + Each customer can access their individual + `Customer Interface `_, + where they see all their tickets with the current status and live updates. Core Workflows This feature allows every organization to configure their individual dynamic @@ -131,16 +116,14 @@ CTI This includes, for example, a call log, an overview of which agent is currently on a call, a caller ID search, and even a Do-Not-Disturb-Mode. - `Learn more on our CTI landing page`_. + You can learn more on our `CTI landing page `_. - Here's the fitting documentation pages: + Here you can find the fitting documentation pages: * :admin-docs:`generic CTI ` * :admin-docs:`placetel CTI ` * :admin-docs:`sipgate CTI ` -.. _Learn more on our CTI landing page: - https://zammad.com/en/product/features/cti-integration Checkmk Checkmk is a powerful IT monitoring tool that can send real-time status @@ -167,7 +150,7 @@ Conflict Warning avatar and a little pen at the bottom of your ticket, it means they are currently editing it. - :ref:`Learn more on our following up page `. + Learn more on our :ref:`following up page `. D - @@ -183,7 +166,7 @@ Dashboard Learn more on :doc:`/extras/dashboard`. Documentation - If this Glossary isn’t enough already (just kidding, it won’t be), + If this Glossary isn't enough already (just kidding, it won't be), our Documentation is the place to head to for all information on Zammad, especially when it comes to the more technical aspects, such as settings or installations. @@ -250,13 +233,11 @@ Feature Feature request Users can let us know if they are missing a particular feature in Zammad. - We collect all of their wishes - `in our Community in the Feature Request category`_. + We collect all of their wishes + `in our Community in the Feature Request category `_. If a request comes in regularly and we feel that it would be a great addition, we'll put it on our roadmap and start working on it. -.. _in our Community in the Feature Request category: - https://community.zammad.org/c/stuff-you-like-zammad-to-have-feel-free-to-discuss-and-add-proposals/6 Feature sponsoring If an organization urgently requires one of the features on the list, @@ -278,10 +259,7 @@ Groups you might remember the principle of "queues". The groups in Zammad are the same as the queues in OTRS. - `Learn more on our group landing page`_. - -.. _Learn more on our group landing page: - https://zammad.com/en/product/features/groups + You can learn more on our `group landing page `_. Grafana Grafana is an open-source reporting tool. @@ -304,7 +282,7 @@ GitHub As Zammad in an open-source project, many developers and tech-lovers from all over the world contribute to it. GitHub is where we coordinate all of this. - `You can find the repository here`_. + You can find the repository `here `_. Besides our own repo, Zammad also has an integration for GitHub. It creates a data exchange that shows you all relevant information about your @@ -315,9 +293,6 @@ GitHub if you're an agent you can learn more about the functionality on this page: :doc:`/extras/github-gitlab-integration`. -.. _You can find the repository here: - https://github.com/zammad/zammad - GitLab GitLab is similar to GitHub. Here at Zammad, we use it for our internal development. @@ -358,10 +333,7 @@ Icinga It can be integrated into Zammad so that it triggers a ticket in case of a warning situation. - `Learn more about Icinga on our landing page`_. - -.. _Learn more about Icinga on our landing page: - https://zammad.com/en/product/features/icinga-integration + You can learn more on our `Icinga landing page `_. Issue-tracking system Issue trackers are usually systems that track processes on a technical level. @@ -380,9 +352,9 @@ K - Knowledge Base - Think of a very extensive set of FAQs – that’s exactly what the + Think of a very extensive set of FAQs - that's exactly what the Zammad knowledge base is. It collects all important information: - definitions, processes, how-to’s, organigrams, etc. + definitions, processes, how-to's, organigrams, etc. Knowledge base articles can be either internal or external, so you can either show them to the world (good for information on your product or @@ -404,10 +376,7 @@ Kibana .. hint:: **🤓 This does not apply to SaaS Zammad instances.** - `Learn more about Kibana on our landing page`_. - -.. _Learn more about Kibana on our landing page: - https://zammad.com/en/product/features/kibana-integration + You can learn more on our `Kibana landing page `_. L - @@ -448,13 +417,10 @@ Migrator / Migration Wizard Monit Monit is an open-source monitoring tool that relies on a simple setup and - a strong community. You can integrate it with Zammad – this way, + a strong community. You can integrate it with Zammad - this way, a ticket is created every time you receive an email in Monit. - `Learn more about Monit on our landing page`_. - -.. _Learn more about Monit on our landing page: - https://zammad.com/en/product/features/monit-integration + You can learn more on our `Monit landing page `_. Mentions Mentions are a Zammad feature that allows you to tag another agent in a @@ -472,10 +438,7 @@ Nagios Nagios can be integrated with Zammad so that a ticket is created in case of an alert. - `Learn more about Nagios on our landing page`_. - -.. _Learn more about Nagios on our landing page: - https://zammad.com/en/product/features/nagios-integration + You can learn more on our `Nagios landing page `_. O - @@ -546,7 +509,7 @@ Role Agents can view and edit tickets, but not change any settings other than those of their own profiles. - Customers can view their tickets’ processing status in their + Customers can view their tickets' processing status in their individual Customer Interface. Release @@ -569,10 +532,7 @@ SSO .. hint:: 🤓 Self Hosted users can also use Kerberos authentication. - `You can learn more about SSO on our landing page`_. - -.. _You can learn more about SSO on our landing page: - https://zammad.com/en/product/features/sso + You can learn more on our `SSO landing page `_. S/MIME S/MIME is the most widely-supported method for secure email communication. @@ -607,10 +567,7 @@ SLA for the first response, an update, and a solution. Once the deadline has been reached, the ticket will escalate. - `Learn more about SLAs on our landing page`_. - -.. _Learn more about SLAs on our landing page: - https://zammad.com/en/product/features/sla + You can learn more on our `SLA landing page `_. Status Every ticket has a status. You can change it once you've updated the ticket. diff --git a/extras/i-doit-track-company-property.rst b/extras/i-doit-track-company-property.rst index 0de1f60f..4f77000c 100644 --- a/extras/i-doit-track-company-property.rst +++ b/extras/i-doit-track-company-property.rst @@ -1,8 +1,8 @@ -i-doit: Use Tickets to Track Company Property -============================================= +i-doit: Track Company Property +============================== With `i-doit `_ integration, -you can list which pieces of your company’s property +you can list which pieces of your company's property are related to any given ticket. That includes both physical and digital infrastructure, from servers to meeting rooms to virtual machines to software licenses. @@ -12,13 +12,13 @@ from servers to meeting rooms to virtual machines to software licenses. :scale: 50% :align: center - Use the 🖨 **printer** tab to view or manage a ticket’s assets from i-doit. + Use the 🖨 **printer** tab to view or manage a ticket's assets from i-doit. -.. note:: **🤔 Huh? I don’t see a 🖨 printer tab...** +.. note:: **🤔 Huh? I don't see a 🖨 printer tab...** This feature is **optional**; - if you don’t see it in the ticket view, - that means your administrator hasn’t enabled it yet. + if you don't see it in the ticket view, + that means your administrator hasn't enabled it yet. Administrators can learn more :admin-docs:`here `. @@ -28,10 +28,10 @@ Why? i-doit can help you keep track of troublesome equipment and find previous tickets from the last time something went wrong with it. -It’s also a great way to document quirks in the company’s belongings: -Why haven’t we upgraded this system from Windows Vista yet? +It's also a great way to document quirks in the company's belongings: +Why haven't we upgraded this system from Windows Vista yet? What did we decide to do about that faulty network switch? -And why does the coffee maker keep shutting off before it’s finished? 🤬 +And why does the coffee maker keep shutting off before it's finished? 🤬 So How Does It Work? -------------------- @@ -40,7 +40,7 @@ So How Does It Work? Ask your administrator / IT personnel to give you a tour—otherwise, the directions below might not make much sense. - (And if your organization isn’t already using i-doit, + (And if your organization isn't already using i-doit, this guide is not for you.) In Zammad: Link i-doit assets to tickets @@ -72,10 +72,10 @@ a list of all the tickets associated with each asset: :alt: (Screencast) See a list of all tickets for an asset in i-doit :align: center - Click the 💬 in the toolbar to list an asset’s tickets. + Click the 💬 in the toolbar to list an asset's tickets. Use the **🔗 Open in ticketsystem** button to open the ticket in Zammad. -You can even launch Zammad’s new ticket dialog directly from i-doit, +You can even launch Zammad's new ticket dialog directly from i-doit, with the asset already linked for you: .. figure:: /images/extras/i-doit-track-company-property/add-ticket-with-idoit-asset_via-idoit.gif diff --git a/extras/secure-email.rst b/extras/secure-email.rst index ba48f111..50a5bbc8 100644 --- a/extras/secure-email.rst +++ b/extras/secure-email.rst @@ -2,7 +2,8 @@ ============ Zammad supports two systems of high-security email communication: - * Pretty Good Privacy (PGP) + + * Pretty Good Privacy (PGP) * Secure/Multipurpose Internet Mail Extensions (S/MIME). .. figure:: /images/extras/secure-email/creating-articles_signed-and-encrypted.gif @@ -13,8 +14,8 @@ Zammad supports two systems of high-security email communication: Use the 🔒 **Encrypt** and ✅ **Sign** buttons to turn on encryption and signing of outgoing emails. -.. note:: **🤔 Huh? I don't see “Sign” or “Encrypt” options in the ticket - view...** +.. note:: **🤔 Huh? I don't see “Sign” or “Encrypt” options in the ticket + view...** This feature is **optional**; if you don't see it in the ticket composer, @@ -28,7 +29,7 @@ Overview -------- PGP and S/MIME are the most widely-supported methods for secure email -communication. With each of the systems, you can exchange **signed** and +communication. With each of the systems, you can exchange **signed** and **encrypted** messages with others. Signing @@ -54,7 +55,7 @@ Encryption Otherwise, you just see the 🔒 **Encrypt** and ✅ **Sign** buttons. .. figure:: /images/extras/secure-email/pgp_and_smime.png - :alt: Screenshot of ticket creation with configured PGP and S/MIME + :alt: Screenshot of ticket creation with configured PGP and S/MIME :scale: 50% :align: center @@ -77,7 +78,7 @@ status. .. list-table:: Status Icons (Incoming) :widths: 5 45 - + * - |lock| - This message was **encrypted for you**. @@ -115,7 +116,7 @@ to turn on encryption and signing for outgoing emails. .. list-table:: Status Icons (Outgoing) :widths: 5 45 - + * - |lock| - This message **will be encrypted**. diff --git a/extras/shared-drafts.rst b/extras/shared-drafts.rst index ba2d68a2..f6718fbd 100644 --- a/extras/shared-drafts.rst +++ b/extras/shared-drafts.rst @@ -9,12 +9,12 @@ Load, modify and safe an existing draft e.g. as QA process with colleagues. option to save the draft :align: center - By using ᐱ next to the "Update" button Zammad will provide you with an option + By using ^ next to the "Update" button Zammad will provide you with an option to save your draft (and thus share it) if the option is enabled. -.. note:: **🤔 Huh? I don’t see “Share Draft” option...** +.. note:: **🤔 Huh? I don't see “Share Draft” option...** - This feature is **optional**; if you don’t see it in the menu, + This feature is **optional**; if you don't see it in the menu, that means your administrator disabled this function. Administrators can learn more in our :admin-docs:`admin documentation `. @@ -123,7 +123,7 @@ New ticket :alt: Screencast showing how to rename / update existing shared drafts Existing ticket - Use the ᐱ button next to the update button. If the group of the ticket + Use the ^ button next to the update button. If the group of the ticket (or in your selection) allows shared drafts, Zammad will provide the option "Save Draft". diff --git a/extras/two-factor-authentication.rst b/extras/two-factor-authentication.rst index c328d121..3757b5b9 100644 --- a/extras/two-factor-authentication.rst +++ b/extras/two-factor-authentication.rst @@ -15,8 +15,8 @@ the account. Set Up Two-Factor Authentication -------------------------------- -If the system admin has enabled this feature, you can head to "Avatar -> Profile --> Password & Authentication" to set it up. Depending on the enabled two-factor +If the system admin has enabled this feature, you can head to "Avatar > Profile +> Password & Authentication" to set it up. Depending on the enabled two-factor methods, you may see one or more options in the table. To set up a two-factor method, use the ⋮ **Actions** menu next to it and choose @@ -119,13 +119,13 @@ place. Once used, a recovery code cannot be reused. You also have an option to regenerate your recovery codes at any time, which invalidates already existing recovery codes and provides you with a list of fresh codes. You can do this by clicking on **Regenerate recovery codes** button -in "Avatar -> Profile -> Password & Authentication". +in "Avatar > Profile > Password & Authentication". Set a Two-Factor Method as Default ---------------------------------- To set an already set up two-factor method as default, use the ⋮ **Actions** -menu next to it in "Avatar -> Profile -> Password & Authentication" and choose +menu next to it in "Avatar > Profile > Password & Authentication" and choose **Set as default**. .. figure:: /images/extras/two-factor-authentication/user-profile-default.png @@ -143,7 +143,7 @@ Edit a Two-Factor Method ------------------------ To edit an already set up two-factor method, use the ⋮ **Actions** menu -next to it in "Avatar -> Profile -> Password & Authentication" and choose +next to it in "Avatar > Profile > Password & Authentication" and choose **Edit**. .. figure:: /images/extras/two-factor-authentication/user-profile-edit.png @@ -161,7 +161,7 @@ Remove a Two-Factor Method -------------------------- To remove an already set up two-factor method, use the ⋮ **Actions** menu -next to it in "Avatar -> Profile -> Password & Authentication" and choose +next to it in "Avatar > Profile > Password & Authentication" and choose **Remove**. .. figure:: /images/extras/two-factor-authentication/user-profile-remove.png @@ -182,7 +182,7 @@ you will be asked to do so at your next sign-in or application reload. :alt: Remove Two-Factor Method in Password & Authentication :align: center -Choose a method of your choice, and then follow its `setup guide`_. +Choose a method of your choice, and then follow its :ref:`setup guide `. .. warning:: If you are required to set up a two-factor authentication for your account, diff --git a/extras/two-factor-authentication/authenticator-app-setup.rst b/extras/two-factor-authentication/authenticator-app-setup.rst index 4ac4bedd..97b9df44 100644 --- a/extras/two-factor-authentication/authenticator-app-setup.rst +++ b/extras/two-factor-authentication/authenticator-app-setup.rst @@ -26,10 +26,6 @@ code in the middle. your secret. Next, add a manual entry to your authenticator app and enter the provided secret when asked. - .. figure:: /images/extras/two-factor-authentication/authenticator-app-reveal-secret.png - :alt: Authenticator App Secret Revealed - :align: center - Your authenticator app should immediately add the new entry for your Zammad account, and a 6-digit code will be displayed next to it together with a timer. diff --git a/images/extras/two-factor-authentication/authenticator-app-reveal-secret.png b/images/extras/two-factor-authentication/authenticator-app-reveal-secret.png deleted file mode 100644 index 8c9f23ac..00000000 Binary files a/images/extras/two-factor-authentication/authenticator-app-reveal-secret.png and /dev/null differ diff --git a/locale/user-docs.pot b/locale/user-docs.pot index 4fa10c0a..a8a7977d 100644 --- a/locale/user-docs.pot +++ b/locale/user-docs.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad User Documentation pre-release\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-09 13:15+0100\n" +"POT-Creation-Date: 2023-12-13 11:13+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -496,7 +496,7 @@ msgid "🤔 **How do I make macros?**" msgstr "" #: ../advanced/macros.rst:12 -msgid "You don’t – that’s the :admin-docs:`administrator’s job `. If you have an idea for a macro you’d like to use, your Zammad admin can probably make it happen." +msgid "You don't - that's the :admin-docs:`administrator's job `. If you have an idea for a macro you'd like to use, your Zammad admin can probably make it happen." msgstr "" #: ../advanced/macros.rst:17 @@ -508,7 +508,7 @@ msgid "On a Single Ticket" msgstr "" #: ../advanced/macros.rst:23 -msgid "The simplest way to apply a macro is to select it from the **Update ᐱ** submenu in the Ticket View:" +msgid "The simplest way to apply a macro is to select it from the **Update ^** submenu in the Ticket View:" msgstr "" #: ../advanced/macros.rst:None @@ -520,11 +520,11 @@ msgid "💾 **Macro = Update**" msgstr "" #: ../advanced/macros.rst:33 -msgid "If you’ve made changes to any other :ref:`settings on the ticket ` (including typing up a reply to the customer), applying a macro will save them, too." +msgid "If you've made changes to any other :ref:`settings on the ticket ` (including typing up a reply to the customer), applying a macro will save them, too." msgstr "" #: ../advanced/macros.rst:38 -msgid "⚠️ **But beware:** in the event of a conflict, the macro’s actions override any manual changes – including messages to the customer! When in doubt, apply your macro and your manual changes *separately.*" +msgid "⚠️ **But beware:** in the event of a conflict, the macro's actions override any manual changes - including messages to the customer! When in doubt, apply your macro and your manual changes *separately.*" msgstr "" #: ../advanced/macros.rst:0 @@ -1655,7 +1655,7 @@ msgid "Search for Tickets" msgstr "" #: ../basics/find-ticket/search.rst:4 -msgid "Looking for an archived ticket? Use the **search bar**." +msgid "Looking for an a specific ticket? Use the **search bar**." msgstr "" #: ../basics/find-ticket/search.rst:10 @@ -1663,7 +1663,7 @@ msgid "Results appear immediately under the search bar as you type." msgstr "" #: ../basics/find-ticket/search.rst:12 -msgid "It’s not just for tickets! Results cover 💬 **chat logs**, 👨 **customers**, and 🏢 **organizations**, too." +msgid "It's not just for tickets! Results cover 💬 **chat logs**, 👨 **customers**, and 🏢 **organizations**, too." msgstr "" #: ../basics/find-ticket/search.rst:15 @@ -1699,11 +1699,11 @@ msgid "Servicing Tickets" msgstr "" #: ../basics/service-ticket.rst:4 -msgid "This is where you’ll spend the vast majority of your time in Zammad." +msgid "This is where you'll spend the vast majority of your time in Zammad." msgstr "" #: ../basics/service-ticket.rst:6 -msgid "Once you get the hang of the tasks below, there’s really not much more to it." +msgid "Once you get the hang of the tasks below, there's really not much more to it." msgstr "" #: ../basics/service-ticket/create.rst:2 @@ -1771,7 +1771,7 @@ msgid "The title of the ticket will be used as the **subject line** for all emai msgstr "" #: ../basics/service-ticket/create.rst:55 -#: ../basics/zammad-glossary.rst:110 +#: ../basics/zammad-glossary.rst:101 msgid "Customer" msgstr "" @@ -2197,7 +2197,7 @@ msgid "If you belong to more than one group, you may re-assign a ticket from one msgstr "" #: ../basics/service-ticket/settings/owner.rst:2 -#: ../basics/zammad-glossary.rst:491 +#: ../basics/zammad-glossary.rst:454 msgid "Owner" msgstr "" @@ -2226,7 +2226,7 @@ msgid "Sometimes, complicated issues will require a ticket to be :ref:`passed ba msgstr "" #: ../basics/service-ticket/settings/priority.rst:2 -#: ../basics/zammad-glossary.rst:529 +#: ../basics/zammad-glossary.rst:492 msgid "Priority" msgstr "" @@ -2328,7 +2328,7 @@ msgid "So, for instance, a ticket may be marked *pending reminder* if it’s wai msgstr "" #: ../basics/service-ticket/settings/tags.rst:2 -#: ../basics/zammad-glossary.rst:657 +#: ../basics/zammad-glossary.rst:614 msgid "Tags" msgstr "" @@ -2425,7 +2425,7 @@ msgid "Admin" msgstr "" #: ../basics/zammad-glossary.rst:22 -msgid "An admin(istrator) is a user in Zammad who has special rights. Admins can configure user accesses, time recording settings, templates, and text modules and, on a higher level, integrations, reporting, etc. So if you're looking to make a change within your Zammad and you find that it doesn't work, find an admin in your organization and ask them – chances are, they can help." +msgid "An admin(istrator) is a user in Zammad who has special rights. Admins can configure user accesses, time recording settings, templates, and text modules and, on a higher level, integrations, reporting, etc. So if you're looking to make a change within your Zammad and you find that it doesn't work, find an admin in your organization and ask them - chances are, they can help." msgstr "" #: ../basics/zammad-glossary.rst:33 @@ -2436,789 +2436,789 @@ msgstr "" msgid "An agent is what we call a user in Zammad who processes tickets/inquiries. There are usually several or many agents who use Zammad regularly and sometimes even consider it their main tool. Some of them are admins, meaning that they can change settings, user rights, and so on (see above)." msgstr "" -#: ../basics/zammad-glossary.rst:42 +#: ../basics/zammad-glossary.rst:43 msgid "API" msgstr "" #: ../basics/zammad-glossary.rst:36 -msgid "An API (Application Programming Interface) is a connection that allows you to create or modify business objects. Zammad has a REST (`Representational State Transfer`_) API that allows our users, among other things, to connect third-party systems to their instance (such as social media or messengers)." +msgid "An API (Application Programming Interface) is a connection that allows you to create or modify business objects. Zammad has a REST (`Representational State Transfer `_) API that allows our users, among other things, to connect third-party systems to their instance (such as social media or messengers)." msgstr "" #: ../basics/zammad-glossary.rst:42 -msgid "You can learn more on our `API landing page`_." +msgid "You can learn more on our `API landing page `_." msgstr "" -#: ../basics/zammad-glossary.rst:54 +#: ../basics/zammad-glossary.rst:49 msgid "Automation" msgstr "" -#: ../basics/zammad-glossary.rst:51 +#: ../basics/zammad-glossary.rst:46 msgid "There are many processes that can be automated with Zammad. This means that certain steps or actions take place automatically, hence no further action is required from the agents. One example would be the weekly deletion of tickets at a pre-defined time." msgstr "" -#: ../basics/zammad-glossary.rst:59 +#: ../basics/zammad-glossary.rst:54 msgid "Article" msgstr "" -#: ../basics/zammad-glossary.rst:57 +#: ../basics/zammad-glossary.rst:52 msgid "Each correspondence within a ticket is called an article. Ticket articles can be internal (so only agents can see them) or public (e.g. emails to your customers, which they receive, too)." msgstr "" -#: ../basics/zammad-glossary.rst:66 +#: ../basics/zammad-glossary.rst:62 msgid "Autosave" msgstr "" -#: ../basics/zammad-glossary.rst:62 -msgid "Autosave might be one of the coolest traits of Zammad: It saves all your work as you go along, so if you ever log out unexpectedly or your browser crashes (we’ve all been there…) none of your work gets lost!" +#: ../basics/zammad-glossary.rst:57 +msgid "Autosave might be one of the coolest traits of Zammad: It saves all your work as you go along, so if you ever log out unexpectedly or your browser crashes (we've all been there…) none of your work gets lost!" msgstr "" -#: ../basics/zammad-glossary.rst:66 -msgid "You can learn more on our `Autosave landing page`_." +#: ../basics/zammad-glossary.rst:61 +msgid "You can learn more on our `Autosave landing page `_." msgstr "" -#: ../basics/zammad-glossary.rst:72 +#: ../basics/zammad-glossary.rst:65 msgid "B" msgstr "" -#: ../basics/zammad-glossary.rst:80 +#: ../basics/zammad-glossary.rst:73 msgid "Branding" msgstr "" -#: ../basics/zammad-glossary.rst:75 +#: ../basics/zammad-glossary.rst:68 msgid "Every company has a different identity, and Zammad accommodates this in various ways, e.g. by letting you design your signatures freely and add your company logo to the platform." msgstr "" -#: ../basics/zammad-glossary.rst:79 +#: ../basics/zammad-glossary.rst:72 msgid "Learn more about branding options :admin-docs:`in the admin documentation `." msgstr "" -#: ../basics/zammad-glossary.rst:83 +#: ../basics/zammad-glossary.rst:76 msgid "C" msgstr "" -#: ../basics/zammad-glossary.rst:92 +#: ../basics/zammad-glossary.rst:85 msgid "Custom Development (CD)" msgstr "" -#: ../basics/zammad-glossary.rst:86 +#: ../basics/zammad-glossary.rst:79 msgid "We are constantly working on improving Zammad, and we keep adding new features with every single release. However, sometimes our customers might require a very specific new feature, addition, or adjustment that is either very urgent or very particular to their individual use case. This is when a custom development can take place: We offer the customer to develop the desired feature at a price that we agree upon previously (which is based on the expected hours needed for completion)." msgstr "" -#: ../basics/zammad-glossary.rst:98 +#: ../basics/zammad-glossary.rst:91 msgid "Changelog" msgstr "" -#: ../basics/zammad-glossary.rst:95 +#: ../basics/zammad-glossary.rst:88 msgid "With every new release comes a new changelog. It is basically a list of all the things that have changed, from new enhancements to bug fixes." msgstr "" -#: ../basics/zammad-glossary.rst:98 -msgid "`You can find them all on our GitHub`_!" +#: ../basics/zammad-glossary.rst:91 +msgid "You can find them all on our `GitHub `_!" msgstr "" -#: ../basics/zammad-glossary.rst:104 -msgid "A customer is a person that you communicate with from within Zammad. Every customer receives a profile page, which we call the `Customer Information Page`_, and it shows all the tickets of this particular customer. Various customers can be assigned to the same organization. Each customer can access their individual `Customer Interface`_, where they see all their tickets with the current status and live updates." +#: ../basics/zammad-glossary.rst:94 +msgid "A customer is a person that you communicate with from within Zammad. Every customer receives a profile page, which we call the `Customer Information Page `_, and it shows all the tickets of this particular customer. Various customers can be assigned to the same organization. Each customer can access their individual `Customer Interface `_, where they see all their tickets with the current status and live updates." msgstr "" -#: ../basics/zammad-glossary.rst:126 +#: ../basics/zammad-glossary.rst:111 msgid "Core Workflows" msgstr "" -#: ../basics/zammad-glossary.rst:119 +#: ../basics/zammad-glossary.rst:104 msgid "This feature allows every organization to configure their individual dynamic fields and ticket masks based on their specific workflows. This way, certain Groups will only (or always) see certain fields. You can even set up dependencies, as in, if one field is filled in, another one opens up or becomes mandatory." msgstr "" -#: ../basics/zammad-glossary.rst:125 +#: ../basics/zammad-glossary.rst:110 msgid "Learn more about Core Workflows :admin-docs:`in the admin documentation `." msgstr "" -#: ../basics/zammad-glossary.rst:140 +#: ../basics/zammad-glossary.rst:126 msgid "CTI" msgstr "" -#: ../basics/zammad-glossary.rst:129 +#: ../basics/zammad-glossary.rst:114 msgid "CTI stands for Computer Telephony Integration and allows you to collect detailed information on all your incoming and outgoing calls. This includes, for example, a call log, an overview of which agent is currently on a call, a caller ID search, and even a Do-Not-Disturb-Mode." msgstr "" -#: ../basics/zammad-glossary.rst:134 -msgid "`Learn more on our CTI landing page`_." +#: ../basics/zammad-glossary.rst:119 +msgid "You can learn more on our `CTI landing page `_." msgstr "" -#: ../basics/zammad-glossary.rst:136 -msgid "Here's the fitting documentation pages:" +#: ../basics/zammad-glossary.rst:121 +msgid "Here you can find the fitting documentation pages:" msgstr "" -#: ../basics/zammad-glossary.rst:138 +#: ../basics/zammad-glossary.rst:123 msgid ":admin-docs:`generic CTI `" msgstr "" -#: ../basics/zammad-glossary.rst:139 +#: ../basics/zammad-glossary.rst:124 msgid ":admin-docs:`placetel CTI `" msgstr "" -#: ../basics/zammad-glossary.rst:140 +#: ../basics/zammad-glossary.rst:125 msgid ":admin-docs:`sipgate CTI `" msgstr "" -#: ../basics/zammad-glossary.rst:152 +#: ../basics/zammad-glossary.rst:135 msgid "Checkmk" msgstr "" -#: ../basics/zammad-glossary.rst:146 +#: ../basics/zammad-glossary.rst:129 msgid "Checkmk is a powerful IT monitoring tool that can send real-time status alerts to Zammad via email or REST API. Set these alerts up in Checkmk, and Zammad will automatically create, update, and close tickets based on the health of your system." msgstr "" -#: ../basics/zammad-glossary.rst:151 +#: ../basics/zammad-glossary.rst:134 msgid "Learn more about checkmk integration :admin-docs:`in the admin documentation `." msgstr "" -#: ../basics/zammad-glossary.rst:161 +#: ../basics/zammad-glossary.rst:144 msgid "Clearbit" msgstr "" -#: ../basics/zammad-glossary.rst:155 +#: ../basics/zammad-glossary.rst:138 msgid "Clearbit is a marketing data engine designed to collect information on your contacts. Thus, new queries from unknown users in Zammad can be automatically enriched with information such as company, number of employees, annual turnover, industry, and much more." msgstr "" -#: ../basics/zammad-glossary.rst:160 +#: ../basics/zammad-glossary.rst:143 msgid "Learn more about clearbit integration :admin-docs:`in the admin documentation `." msgstr "" -#: ../basics/zammad-glossary.rst:170 +#: ../basics/zammad-glossary.rst:153 msgid "Conflict Warning" msgstr "" -#: ../basics/zammad-glossary.rst:164 +#: ../basics/zammad-glossary.rst:147 msgid "When two agents edit the same ticket at the same time, a lot can go wrong - from duplicate replies to overwritten messages. Zammad helps you to avoid this with its integrated conflict warning. So if you see another agents avatar and a little pen at the bottom of your ticket, it means they are currently editing it." msgstr "" -#: ../basics/zammad-glossary.rst:170 -msgid ":ref:`Learn more on our following up page `." +#: ../basics/zammad-glossary.rst:153 +msgid "Learn more on our :ref:`following up page `." msgstr "" -#: ../basics/zammad-glossary.rst:173 +#: ../basics/zammad-glossary.rst:156 msgid "D" msgstr "" -#: ../basics/zammad-glossary.rst:183 +#: ../basics/zammad-glossary.rst:166 msgid "Dashboard" msgstr "" -#: ../basics/zammad-glossary.rst:176 +#: ../basics/zammad-glossary.rst:159 msgid "The dashboard is every agent's individual Welcome Page in Zammad and gives you feedback on your situation by collecting information and statistics about your work. Here you can find all sorts of overviews, such as the open tickets, the average waiting time, or the reopening rate. You can also see what your colleagues are doing by checking the Activity Stream." msgstr "" -#: ../basics/zammad-glossary.rst:183 +#: ../basics/zammad-glossary.rst:166 msgid "Learn more on :doc:`/extras/dashboard`." msgstr "" -#: ../basics/zammad-glossary.rst:193 +#: ../basics/zammad-glossary.rst:176 msgid "Documentation" msgstr "" -#: ../basics/zammad-glossary.rst:186 -msgid "If this Glossary isn’t enough already (just kidding, it won’t be), our Documentation is the place to head to for all information on Zammad, especially when it comes to the more technical aspects, such as settings or installations." +#: ../basics/zammad-glossary.rst:169 +msgid "If this Glossary isn't enough already (just kidding, it won't be), our Documentation is the place to head to for all information on Zammad, especially when it comes to the more technical aspects, such as settings or installations." msgstr "" -#: ../basics/zammad-glossary.rst:191 +#: ../basics/zammad-glossary.rst:174 msgid "We have three different ones: :doc:`/index`, :admin-docs:`Zammad Admin Documentation `, and the :docs:`Zammad System Documentation `." msgstr "" -#: ../basics/zammad-glossary.rst:196 +#: ../basics/zammad-glossary.rst:179 msgid "E" msgstr "" -#: ../basics/zammad-glossary.rst:204 +#: ../basics/zammad-glossary.rst:187 msgid "Escalation" msgstr "" -#: ../basics/zammad-glossary.rst:199 +#: ../basics/zammad-glossary.rst:182 msgid "An escalation is what happens after the deadline for a ticket has passed and, for example, no update to the customer has been created. The ticket is marked in red in your taskbar and the overviews and everyone else who is involved in its process gets very sad. So don't let tickets escalate! Also, in order to prevent escalations, you can use our SLAs (see :ref:`SLAs `)." msgstr "" -#: ../basics/zammad-glossary.rst:214 +#: ../basics/zammad-glossary.rst:197 msgid "External Authentication" msgstr "" -#: ../basics/zammad-glossary.rst:207 +#: ../basics/zammad-glossary.rst:190 msgid "External authentication is an easy, one-click option for your users to log into Zammad. It has various benefits: not only is it faster but it also means that your users will have to remember fewer passwords. Zammad currently supports more than ten login providers, such as Facebook, GitHub, GitLab, Google, or Microsoft / Office365." msgstr "" -#: ../basics/zammad-glossary.rst:213 +#: ../basics/zammad-glossary.rst:196 msgid "See our :admin-docs:`admin documentation ` for all third party authentication providers." msgstr "" -#: ../basics/zammad-glossary.rst:223 +#: ../basics/zammad-glossary.rst:206 msgid "Exchange Integration" msgstr "" -#: ../basics/zammad-glossary.rst:217 +#: ../basics/zammad-glossary.rst:200 msgid "The Exchange integration allows users to sync their contacts from their Exchange address book with Zammad. This way, every time a contact is updated in Exchange, the iteration will be reflected in Zammad, giving you direct access to all your Exchange contacts from within your helpdesk." msgstr "" -#: ../basics/zammad-glossary.rst:222 +#: ../basics/zammad-glossary.rst:205 msgid "Learn more about the exchange integration :admin-docs:`in our admin documentation `." msgstr "" -#: ../basics/zammad-glossary.rst:241 +#: ../basics/zammad-glossary.rst:224 msgid "Elasticsearch" msgstr "" -#: ../basics/zammad-glossary.rst:226 +#: ../basics/zammad-glossary.rst:209 msgid "Zammad offers an Elasticsearch integration (a free and open search engine) that makes the search process within Zammad super fast (even for data sets of several terra bytes!)." msgstr "" -#: ../basics/zammad-glossary.rst:230 +#: ../basics/zammad-glossary.rst:213 msgid "Spoiler: Zammad is currently the only helpdesk system with a search function that combs attachments, too!" msgstr "" -#: ../basics/zammad-glossary.rst:233 +#: ../basics/zammad-glossary.rst:216 msgid "**🤓 This affects hosted environments only!**" msgstr "" -#: ../basics/zammad-glossary.rst:235 +#: ../basics/zammad-glossary.rst:218 msgid "Via a read-only user in Elasticsearch, you can also integrate your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../basics/zammad-glossary.rst:244 +#: ../basics/zammad-glossary.rst:227 msgid "F" msgstr "" -#: ../basics/zammad-glossary.rst:249 +#: ../basics/zammad-glossary.rst:232 msgid "Feature" msgstr "" -#: ../basics/zammad-glossary.rst:247 +#: ../basics/zammad-glossary.rst:230 msgid "A feature is what we call the different functionalities of Zammad, such as our integrations, productivity tools, or time-saving aspects. We keep adding new features with every release." msgstr "" -#: ../basics/zammad-glossary.rst:256 +#: ../basics/zammad-glossary.rst:240 msgid "Feature request" msgstr "" -#: ../basics/zammad-glossary.rst:252 -msgid "Users can let us know if they are missing a particular feature in Zammad. We collect all of their wishes `in our Community in the Feature Request category`_. If a request comes in regularly and we feel that it would be a great addition, we'll put it on our roadmap and start working on it." +#: ../basics/zammad-glossary.rst:235 +msgid "Users can let us know if they are missing a particular feature in Zammad. We collect all of their wishes `in our Community in the Feature Request category `_. If a request comes in regularly and we feel that it would be a great addition, we'll put it on our roadmap and start working on it." msgstr "" -#: ../basics/zammad-glossary.rst:264 +#: ../basics/zammad-glossary.rst:245 msgid "Feature sponsoring" msgstr "" -#: ../basics/zammad-glossary.rst:262 +#: ../basics/zammad-glossary.rst:243 msgid "If an organization urgently requires one of the features on the list, they can fast-forward the development and put it on top of the list by sponsoring it, which means that they cover the costs for the development." msgstr "" -#: ../basics/zammad-glossary.rst:267 +#: ../basics/zammad-glossary.rst:248 msgid "G" msgstr "" -#: ../basics/zammad-glossary.rst:281 +#: ../basics/zammad-glossary.rst:262 msgid "Groups" msgstr "" -#: ../basics/zammad-glossary.rst:270 +#: ../basics/zammad-glossary.rst:251 msgid "Groups are a synonym for departments or processing groups. The incoming tickets are assigned to them. The corresponding group is responsible for the processing. Within the group, an owner can be defined, who is then responsible for this ticket. Access rights to tickets are also controlled via the groups. The possible permissions are \"full access\", \"read-only\" and \"no access\"." msgstr "" -#: ../basics/zammad-glossary.rst:277 +#: ../basics/zammad-glossary.rst:258 msgid "If you have worked with the OTRS system in the past, you might remember the principle of \"queues\". The groups in Zammad are the same as the queues in OTRS." msgstr "" -#: ../basics/zammad-glossary.rst:281 -msgid "`Learn more on our group landing page`_." +#: ../basics/zammad-glossary.rst:262 +msgid "You can learn more on our `group landing page `_." msgstr "" -#: ../basics/zammad-glossary.rst:297 +#: ../basics/zammad-glossary.rst:275 msgid "Grafana" msgstr "" -#: ../basics/zammad-glossary.rst:287 +#: ../basics/zammad-glossary.rst:265 msgid "Grafana is an open-source reporting tool. Zammad users on the Plus plan can integrate it into their instance and receive detailed analytics on their performance." msgstr "" -#: ../basics/zammad-glossary.rst:291 +#: ../basics/zammad-glossary.rst:269 msgid "**🤓 Self Hosted users**" msgstr "" -#: ../basics/zammad-glossary.rst:293 +#: ../basics/zammad-glossary.rst:271 msgid "Hooking up Grafana to Elasticsearch is an possibility you can do on your own as well." msgstr "" -#: ../basics/zammad-glossary.rst:296 +#: ../basics/zammad-glossary.rst:274 msgid "Learn more on how to add Grafana dashboards for Zammad :docs:`in our documentation `." msgstr "" -#: ../basics/zammad-glossary.rst:316 +#: ../basics/zammad-glossary.rst:294 msgid "GitHub" msgstr "" -#: ../basics/zammad-glossary.rst:300 +#: ../basics/zammad-glossary.rst:278 msgid "GitHub is a service for the version management of software development projects. It uses Git, a software that tracks changes in file sets. Here at Zammad, we use it to maintain our repository." msgstr "" -#: ../basics/zammad-glossary.rst:304 +#: ../basics/zammad-glossary.rst:282 msgid "As Zammad in an open-source project, many developers and tech-lovers from all over the world contribute to it. GitHub is where we coordinate all of this." msgstr "" -#: ../basics/zammad-glossary.rst:307 -msgid "`You can find the repository here`_." +#: ../basics/zammad-glossary.rst:285 +msgid "You can find the repository `here `_." msgstr "" -#: ../basics/zammad-glossary.rst:309 +#: ../basics/zammad-glossary.rst:287 msgid "Besides our own repo, Zammad also has an integration for GitHub. It creates a data exchange that shows you all relevant information about your issues directly in the helpdesk, such as status or assignees." msgstr "" -#: ../basics/zammad-glossary.rst:313 +#: ../basics/zammad-glossary.rst:291 msgid "Administrators can learn more about GitHub :admin-docs:`in the admin documentation `, if you're an agent you can learn more about the functionality on this page: :doc:`/extras/github-gitlab-integration`." msgstr "" -#: ../basics/zammad-glossary.rst:332 +#: ../basics/zammad-glossary.rst:307 msgid "GitLab" msgstr "" -#: ../basics/zammad-glossary.rst:322 +#: ../basics/zammad-glossary.rst:297 msgid "GitLab is similar to GitHub. Here at Zammad, we use it for our internal development." msgstr "" -#: ../basics/zammad-glossary.rst:325 +#: ../basics/zammad-glossary.rst:300 msgid "There is also an integration that allows users to connect GitLab to Zammad so that all their issues and their corresponding changes are reflected in both systems." msgstr "" -#: ../basics/zammad-glossary.rst:329 +#: ../basics/zammad-glossary.rst:304 msgid "Administrators can learn more about GitLab :admin-docs:`in the admin documentation `, if you're an agent you can learn more about the functionality on this page: :doc:`/extras/github-gitlab-integration`." msgstr "" -#: ../basics/zammad-glossary.rst:335 +#: ../basics/zammad-glossary.rst:310 msgid "H" msgstr "" -#: ../basics/zammad-glossary.rst:340 +#: ../basics/zammad-glossary.rst:315 msgid "I" msgstr "" -#: ../basics/zammad-glossary.rst:353 +#: ../basics/zammad-glossary.rst:328 msgid "i-doit" msgstr "" -#: ../basics/zammad-glossary.rst:343 +#: ../basics/zammad-glossary.rst:318 msgid "i-doit is a CMDB (Configuration Management Data Base). It helps you to keep an eye on every piece of the physical and digital infrastructure. A corresponding integration makes it possible to connect it to Zammad, where it adds a new tab to Zammad's ticket sidebar so you can link to existing i-doit objects for easy reference. It also allows you to create Zammad tickets in i-doit." msgstr "" -#: ../basics/zammad-glossary.rst:350 +#: ../basics/zammad-glossary.rst:325 msgid "Administrators can learn more about i-doit :admin-docs:`in the admin documentation `, if you're an agent you can learn more about the functionality on this page: :doc:`/extras/i-doit-track-company-property`." msgstr "" -#: ../basics/zammad-glossary.rst:361 +#: ../basics/zammad-glossary.rst:336 msgid "Icinga" msgstr "" -#: ../basics/zammad-glossary.rst:356 +#: ../basics/zammad-glossary.rst:331 msgid "Icinga is a monitoring system that supervises the availability of an organization's entire system infrastructure. It can be integrated into Zammad so that it triggers a ticket in case of a warning situation." msgstr "" -#: ../basics/zammad-glossary.rst:361 -msgid "`Learn more about Icinga on our landing page`_." +#: ../basics/zammad-glossary.rst:336 +msgid "You can learn more on our `Icinga landing page `_." msgstr "" -#: ../basics/zammad-glossary.rst:372 +#: ../basics/zammad-glossary.rst:344 msgid "Issue-tracking system" msgstr "" -#: ../basics/zammad-glossary.rst:367 +#: ../basics/zammad-glossary.rst:339 msgid "Issue trackers are usually systems that track processes on a technical level. Two of the best-known examples are GitHub and GitLab." msgstr "" -#: ../basics/zammad-glossary.rst:370 +#: ../basics/zammad-glossary.rst:342 msgid "Zammad is also often referred to as an issue-tracking system. However, as a helpdesk, it focuses on communication at the customer level rather than the technical level." msgstr "" -#: ../basics/zammad-glossary.rst:375 +#: ../basics/zammad-glossary.rst:347 msgid "J" msgstr "" -#: ../basics/zammad-glossary.rst:380 +#: ../basics/zammad-glossary.rst:352 msgid "K" msgstr "" -#: ../basics/zammad-glossary.rst:395 +#: ../basics/zammad-glossary.rst:367 #: ../extras/knowledge-base.rst:2 msgid "Knowledge Base" msgstr "" -#: ../basics/zammad-glossary.rst:383 -msgid "Think of a very extensive set of FAQs – that’s exactly what the Zammad knowledge base is. It collects all important information: definitions, processes, how-to’s, organigrams, etc." +#: ../basics/zammad-glossary.rst:355 +msgid "Think of a very extensive set of FAQs - that's exactly what the Zammad knowledge base is. It collects all important information: definitions, processes, how-to's, organigrams, etc." msgstr "" -#: ../basics/zammad-glossary.rst:387 +#: ../basics/zammad-glossary.rst:359 msgid "Knowledge base articles can be either internal or external, so you can either show them to the world (good for information on your product or service, for example) or keep them for your team (e.g. for internal processes or team info)." msgstr "" -#: ../basics/zammad-glossary.rst:392 +#: ../basics/zammad-glossary.rst:364 msgid "Administrators can learn more about the Knowledge Base :admin-docs:`in the admin documentation `, if you're an agent you can learn more about the functionality on this page: :doc:`/extras/knowledge-base`." msgstr "" -#: ../basics/zammad-glossary.rst:407 +#: ../basics/zammad-glossary.rst:379 msgid "Kibana" msgstr "" -#: ../basics/zammad-glossary.rst:398 +#: ../basics/zammad-glossary.rst:370 msgid "Kibana is a browser-based, open-source reporting tool that focuses on data evaluation. It was developed by Elastic, which is why it is not a surprise that it uses data from Elasticsearch for its analytics." msgstr "" -#: ../basics/zammad-glossary.rst:402 +#: ../basics/zammad-glossary.rst:374 msgid "Kibana can be integrated with Zammad, allowing for helpdesk data to be mapped in the reporting tool." msgstr "" -#: ../basics/zammad-glossary.rst:405 +#: ../basics/zammad-glossary.rst:377 msgid "**🤓 This does not apply to SaaS Zammad instances.**" msgstr "" -#: ../basics/zammad-glossary.rst:407 -msgid "`Learn more about Kibana on our landing page`_." +#: ../basics/zammad-glossary.rst:379 +msgid "You can learn more on our `Kibana landing page `_." msgstr "" -#: ../basics/zammad-glossary.rst:413 +#: ../basics/zammad-glossary.rst:382 msgid "L" msgstr "" -#: ../basics/zammad-glossary.rst:421 +#: ../basics/zammad-glossary.rst:390 msgid "LDAP" msgstr "" -#: ../basics/zammad-glossary.rst:416 +#: ../basics/zammad-glossary.rst:385 msgid "A Lightweight Directory Access Protocol (LDAP) helps provide information about your users within Zammad. Authentication of users against the LDAP and LDAP role mapping to Zammad roles are also possible." msgstr "" -#: ../basics/zammad-glossary.rst:420 +#: ../basics/zammad-glossary.rst:389 msgid "Learn more about LDAP integration :admin-docs:`in the admin documentation `." msgstr "" -#: ../basics/zammad-glossary.rst:424 +#: ../basics/zammad-glossary.rst:393 msgid "M" msgstr "" -#: ../basics/zammad-glossary.rst:441 +#: ../basics/zammad-glossary.rst:410 msgid "Macro" msgstr "" -#: ../basics/zammad-glossary.rst:427 +#: ../basics/zammad-glossary.rst:396 msgid "A macro is a series of actions. By starting the macro, the actions are also triggered (like a domino effect), so users don't have to work through each individual step separately. It saves an enormous amount of time and ensures that no step is forgotten." msgstr "" -#: ../basics/zammad-glossary.rst:432 +#: ../basics/zammad-glossary.rst:401 msgid "An example of this is declaring a ticket as \"spam\". The manual way here would be to assign an owner, set a status, and add the tag \"spam\". Using a macro, all this can be done in just one action. Macros can be used in the ticket zoom or within an overview (using multiple selection)." msgstr "" -#: ../basics/zammad-glossary.rst:438 +#: ../basics/zammad-glossary.rst:407 msgid "Administrators can learn more about Macros :admin-docs:`in the admin documentation `, if you're an agent you can learn more about the functionality on this page: :doc:`/advanced/macros`." msgstr "" -#: ../basics/zammad-glossary.rst:447 +#: ../basics/zammad-glossary.rst:416 msgid "Migrator / Migration Wizard" msgstr "" -#: ../basics/zammad-glossary.rst:444 +#: ../basics/zammad-glossary.rst:413 msgid "If a company wants to switch from another helpdesk software to Zammad, they often have one concern: What about their existing data? That's why we have built our migration wizards that help with migrating all data at the touch of a button." msgstr "" -#: ../basics/zammad-glossary.rst:454 +#: ../basics/zammad-glossary.rst:423 msgid "Monit" msgstr "" -#: ../basics/zammad-glossary.rst:450 -msgid "Monit is an open-source monitoring tool that relies on a simple setup and a strong community. You can integrate it with Zammad – this way, a ticket is created every time you receive an email in Monit." +#: ../basics/zammad-glossary.rst:419 +msgid "Monit is an open-source monitoring tool that relies on a simple setup and a strong community. You can integrate it with Zammad - this way, a ticket is created every time you receive an email in Monit." msgstr "" -#: ../basics/zammad-glossary.rst:454 -msgid "`Learn more about Monit on our landing page`_." +#: ../basics/zammad-glossary.rst:423 +msgid "You can learn more on our `Monit landing page `_." msgstr "" -#: ../basics/zammad-glossary.rst:464 +#: ../basics/zammad-glossary.rst:430 msgid "Mentions" msgstr "" -#: ../basics/zammad-glossary.rst:460 +#: ../basics/zammad-glossary.rst:426 msgid "Mentions are a Zammad feature that allows you to tag another agent in a ticket. Just type ``@@`` and the name. The selected person will be notified and will be watching the ticket from now on." msgstr "" -#: ../basics/zammad-glossary.rst:464 +#: ../basics/zammad-glossary.rst:430 msgid "Learn more on this page: :ref:`mentions`." msgstr "" -#: ../basics/zammad-glossary.rst:467 +#: ../basics/zammad-glossary.rst:433 msgid "N" msgstr "" -#: ../basics/zammad-glossary.rst:475 +#: ../basics/zammad-glossary.rst:441 msgid "Nagios" msgstr "" -#: ../basics/zammad-glossary.rst:470 +#: ../basics/zammad-glossary.rst:436 msgid "Nagios is another monitoring tool that alerts IT teams when, for example, a server is no longer accessible or a hard disk is about to be exhausted. Nagios can be integrated with Zammad so that a ticket is created in case of an alert." msgstr "" -#: ../basics/zammad-glossary.rst:475 -msgid "`Learn more about Nagios on our landing page`_." +#: ../basics/zammad-glossary.rst:441 +msgid "You can learn more on our `Nagios landing page `_." msgstr "" -#: ../basics/zammad-glossary.rst:481 +#: ../basics/zammad-glossary.rst:444 msgid "O" msgstr "" -#: ../basics/zammad-glossary.rst:484 +#: ../basics/zammad-glossary.rst:447 msgid "The owner of a ticket is the person responsible for it and ensures that it is processed in the best possible way. Of course, ownership can be transferred to another agent. In this case, it is recommended to leave a handover note on the ticket so that the new owner knows what is expected of them." msgstr "" -#: ../basics/zammad-glossary.rst:490 +#: ../basics/zammad-glossary.rst:453 msgid "Learn more about ticket owners on this page: :doc:`/basics/service-ticket/settings`" msgstr "" -#: ../basics/zammad-glossary.rst:497 +#: ../basics/zammad-glossary.rst:460 #: ../extras/customers.rst:0 msgid "Organization" msgstr "" -#: ../basics/zammad-glossary.rst:494 +#: ../basics/zammad-glossary.rst:457 msgid "An organization identifies a grouping of customers that operate under the same roof or within the same customer group. If a customer whose organization is \"sharing\" logs in to the customer interface, this user has access to all tickets of his organization." msgstr "" -#: ../basics/zammad-glossary.rst:500 +#: ../basics/zammad-glossary.rst:463 msgid "P" msgstr "" -#: ../basics/zammad-glossary.rst:509 +#: ../basics/zammad-glossary.rst:472 msgid "Parent/Child Relationship" msgstr "" -#: ../basics/zammad-glossary.rst:503 +#: ../basics/zammad-glossary.rst:466 msgid "If one ticket results in other subtasks (or additional correspondences), you can split it into several tickets. The main one will then be the parent ticket and the tickets with related subtopics are children. By the way: in the same way, you can also merge two tickets into one." msgstr "" -#: ../basics/zammad-glossary.rst:508 +#: ../basics/zammad-glossary.rst:471 msgid "Learn more about this function on this page: :doc:`/advanced/ticket-actions/link`." msgstr "" -#: ../basics/zammad-glossary.rst:524 +#: ../basics/zammad-glossary.rst:487 msgid "Placetel" msgstr "" -#: ../basics/zammad-glossary.rst:512 +#: ../basics/zammad-glossary.rst:475 msgid "Placetel is a Cloud Telephone System that allows users to make phone calls via VoIP. Use your regular phone number and call someone directly on their mobile or landline while still having all communication in one place (aka Zammad)." msgstr "" -#: ../basics/zammad-glossary.rst:517 +#: ../basics/zammad-glossary.rst:480 msgid "Integrating a Placetel account with Zammad provides users with a call log, making the history of their correspondences even more accurate. Callers are identified directly by their caller ID - a key function that saves agents a lot of time when assigning callers." msgstr "" -#: ../basics/zammad-glossary.rst:522 +#: ../basics/zammad-glossary.rst:485 msgid "Administrators can learn more on the `placetel CTI` integration page. Agents can learn more about this function on this page: :doc:`/extras/caller-log`" msgstr "" -#: ../basics/zammad-glossary.rst:527 +#: ../basics/zammad-glossary.rst:490 msgid "Every ticket gets assigned a priority. By default, the priority is 2 (normal). But it can be changed to either 1 (low) or 3 (high)." msgstr "" -#: ../basics/zammad-glossary.rst:532 +#: ../basics/zammad-glossary.rst:495 msgid "Q" msgstr "" -#: ../basics/zammad-glossary.rst:537 +#: ../basics/zammad-glossary.rst:500 msgid "R" msgstr "" -#: ../basics/zammad-glossary.rst:550 +#: ../basics/zammad-glossary.rst:513 msgid "Role" msgstr "" -#: ../basics/zammad-glossary.rst:540 +#: ../basics/zammad-glossary.rst:503 msgid "Everyone who logs into Zammad has a predefined role. There are three types: admin, agent, and customer." msgstr "" -#: ../basics/zammad-glossary.rst:543 +#: ../basics/zammad-glossary.rst:506 msgid "Admins have the most rights: they can define roles, permissions, and settings for the entire team and instance." msgstr "" -#: ../basics/zammad-glossary.rst:546 +#: ../basics/zammad-glossary.rst:509 msgid "Agents can view and edit tickets, but not change any settings other than those of their own profiles." msgstr "" -#: ../basics/zammad-glossary.rst:549 -msgid "Customers can view their tickets’ processing status in their individual Customer Interface." +#: ../basics/zammad-glossary.rst:512 +msgid "Customers can view their tickets' processing status in their individual Customer Interface." msgstr "" -#: ../basics/zammad-glossary.rst:560 +#: ../basics/zammad-glossary.rst:523 msgid "Release" msgstr "" -#: ../basics/zammad-glossary.rst:553 +#: ../basics/zammad-glossary.rst:516 msgid "Every few months, we bring a new version of Zammad into the world, which is called a release. It all started with Zammad 1.0." msgstr "" -#: ../basics/zammad-glossary.rst:556 +#: ../basics/zammad-glossary.rst:519 msgid "Every release adds new features to our software. There are major and minor releases: major releases (such as Zammad 1.0, 2.0, etc.) bring major changes. Minor releases are installed on top of them (such as 1.1, 2.1, etc.) and bring smaller updates." msgstr "" -#: ../basics/zammad-glossary.rst:563 +#: ../basics/zammad-glossary.rst:526 msgid "S" msgstr "" -#: ../basics/zammad-glossary.rst:572 +#: ../basics/zammad-glossary.rst:535 msgid "SSO" msgstr "" -#: ../basics/zammad-glossary.rst:566 +#: ../basics/zammad-glossary.rst:529 msgid "Single-sign-on (SSO) allows you to access all your systems and devices with just one login. There are various providers that make this process easy and secure. Zammad currently supports SSO via SAML and Shibboleth." msgstr "" -#: ../basics/zammad-glossary.rst:570 +#: ../basics/zammad-glossary.rst:533 msgid "🤓 Self Hosted users can also use Kerberos authentication." msgstr "" -#: ../basics/zammad-glossary.rst:572 -msgid "`You can learn more about SSO on our landing page`_." +#: ../basics/zammad-glossary.rst:535 +msgid "You can learn more on our `SSO landing page `_." msgstr "" -#: ../basics/zammad-glossary.rst:585 +#: ../basics/zammad-glossary.rst:545 msgid "S/MIME" msgstr "" -#: ../basics/zammad-glossary.rst:578 +#: ../basics/zammad-glossary.rst:538 msgid "S/MIME is the most widely-supported method for secure email communication. By activating it in Zammad, all messages sent from Zammad will be signed and encrypted." msgstr "" -#: ../basics/zammad-glossary.rst:582 +#: ../basics/zammad-glossary.rst:542 msgid "Administrators can learn more about S/MIME :admin-docs:`in the admin documentation `, if you're an agent you can learn more about the functionality on this page: :doc:`/extras/secure-email`." msgstr "" -#: ../basics/zammad-glossary.rst:595 +#: ../basics/zammad-glossary.rst:555 msgid "Sipgate" msgstr "" -#: ../basics/zammad-glossary.rst:588 +#: ../basics/zammad-glossary.rst:548 msgid "Sipgate is a SaaS solution for internet telephony. The Zammad integration for Sipgate provides users with a detailed call overview. If you have a customer that wants to get connected to a certain agent, the caller log will tell you if this colleague is currently available." msgstr "" -#: ../basics/zammad-glossary.rst:593 +#: ../basics/zammad-glossary.rst:553 msgid "Administrators can learn more on the `sipgate CTI` integration page. Agents can learn more about this function on this page: :doc:`/extras/caller-log`" msgstr "" -#: ../basics/zammad-glossary.rst:610 +#: ../basics/zammad-glossary.rst:570 msgid "SLA" msgstr "" -#: ../basics/zammad-glossary.rst:600 +#: ../basics/zammad-glossary.rst:560 msgid "A Service Level Agreement (SLA) is a contract between an end-user and a company that defines the minimum expected service requirements including quality, availability, and punctuality. They are used to set expectations and hold companies accountable for keeping their promises." msgstr "" -#: ../basics/zammad-glossary.rst:606 +#: ../basics/zammad-glossary.rst:566 msgid "You can easily set up SLAs in Zammad and define parameters such as the time for the first response, an update, and a solution. Once the deadline has been reached, the ticket will escalate." msgstr "" -#: ../basics/zammad-glossary.rst:610 -msgid "`Learn more about SLAs on our landing page`_." +#: ../basics/zammad-glossary.rst:570 +msgid "You can learn more on our `SLA landing page `_." msgstr "" -#: ../basics/zammad-glossary.rst:620 +#: ../basics/zammad-glossary.rst:577 msgid "Status" msgstr "" -#: ../basics/zammad-glossary.rst:616 +#: ../basics/zammad-glossary.rst:573 msgid "Every ticket has a status. You can change it once you've updated the ticket. There are four types of status, and they are all color-coded." msgstr "" -#: ../basics/zammad-glossary.rst:619 +#: ../basics/zammad-glossary.rst:576 msgid "Learn more about states and they color coding on this page: :doc:`/basics/service-ticket/settings/state`" msgstr "" -#: ../basics/zammad-glossary.rst:623 +#: ../basics/zammad-glossary.rst:580 msgid "T" msgstr "" -#: ../basics/zammad-glossary.rst:637 +#: ../basics/zammad-glossary.rst:594 msgid "Text module" msgstr "" -#: ../basics/zammad-glossary.rst:626 +#: ../basics/zammad-glossary.rst:583 msgid "If you find that you send the same answers / text bits over and over again, you can save yourself a bunch of work and create a text module. This way, you just need to type ``::`` shortcut and the pre-defined paragraph will automatically appear in your article." msgstr "" -#: ../basics/zammad-glossary.rst:631 +#: ../basics/zammad-glossary.rst:588 msgid "For example, here at Zammad, we have a text module with the shortcut ``::ilff``, which turns into ``I look forward to your feedback``." msgstr "" -#: ../basics/zammad-glossary.rst:634 +#: ../basics/zammad-glossary.rst:591 msgid "Administrators can learn more about text modules :admin-docs:`here `. Agents can learn more about this function on this page: :doc:`/advanced/text-modules`" msgstr "" -#: ../basics/zammad-glossary.rst:644 +#: ../basics/zammad-glossary.rst:601 msgid "(Ticket) Template" msgstr "" -#: ../basics/zammad-glossary.rst:640 +#: ../basics/zammad-glossary.rst:597 msgid "If you create many similar tickets or write many similar texts, you can create a template for them. This is helpful for introductions to your product/service or for drawing up an offer. It's a real time-saver!" msgstr "" -#: ../basics/zammad-glossary.rst:644 +#: ../basics/zammad-glossary.rst:601 msgid "You can learn more on this page: :doc:`/advanced/ticket-templates`." msgstr "" -#: ../basics/zammad-glossary.rst:647 +#: ../basics/zammad-glossary.rst:604 msgid "Tags help you to categorize tickets. You can define them based on your use case. For example, if you're a retail business, your tags could be based on your product categories to help you organize tickets by the type of product they refer to. But they could also be based on the type of request, e.g. refund, delivery issue, missing…" msgstr "" -#: ../basics/zammad-glossary.rst:654 +#: ../basics/zammad-glossary.rst:611 msgid "Administrators can learn more about tags :admin-docs:`here `. Agents can learn more about this function on this page: :doc:`/basics/service-ticket/settings/tags`" msgstr "" -#: ../basics/zammad-glossary.rst:660 +#: ../basics/zammad-glossary.rst:617 msgid "U" msgstr "" -#: ../basics/zammad-glossary.rst:666 +#: ../basics/zammad-glossary.rst:623 msgid "User" msgstr "" -#: ../basics/zammad-glossary.rst:663 +#: ../basics/zammad-glossary.rst:620 msgid "A user is any user of the ticket system. Each user is assigned certain permissions, which allow them to access certain areas and information. Users can have various roles, with the standard options being agent, admin, and customer." msgstr "" -#: ../basics/zammad-glossary.rst:669 +#: ../basics/zammad-glossary.rst:626 msgid "V" msgstr "" -#: ../basics/zammad-glossary.rst:674 +#: ../basics/zammad-glossary.rst:631 msgid "W" msgstr "" -#: ../basics/zammad-glossary.rst:683 +#: ../basics/zammad-glossary.rst:640 msgid "Webhooks" msgstr "" -#: ../basics/zammad-glossary.rst:677 +#: ../basics/zammad-glossary.rst:634 msgid "In a nutshell, webhooks are an easy way for systems to communicate with each other and allow you to send real-time data to any other application. We use them to allow our users to inform a third-party system about new information in Zammad." msgstr "" -#: ../basics/zammad-glossary.rst:682 +#: ../basics/zammad-glossary.rst:639 msgid "Learn more about webhooks on :admin-docs:`this page `." msgstr "" -#: ../basics/zammad-glossary.rst:686 +#: ../basics/zammad-glossary.rst:643 msgid "X" msgstr "" -#: ../basics/zammad-glossary.rst:691 +#: ../basics/zammad-glossary.rst:648 msgid "Y" msgstr "" -#: ../basics/zammad-glossary.rst:696 +#: ../basics/zammad-glossary.rst:653 msgid "Z" msgstr "" -#: ../basics/zammad-glossary.rst:698 +#: ../basics/zammad-glossary.rst:655 msgid "Zammad" msgstr "" -#: ../basics/zammad-glossary.rst:699 +#: ../basics/zammad-glossary.rst:656 msgid "Zammad is the greatest helpdesk in the world. Period." msgstr "" @@ -3692,11 +3692,11 @@ msgid "Click the ✕ button next to an issue title to unlink it." msgstr "" #: ../extras/i-doit-track-company-property.rst:2 -msgid "i-doit: Use Tickets to Track Company Property" +msgid "i-doit: Track Company Property" msgstr "" #: ../extras/i-doit-track-company-property.rst:4 -msgid "With `i-doit `_ integration, you can list which pieces of your company’s property are related to any given ticket. That includes both physical and digital infrastructure, from servers to meeting rooms to virtual machines to software licenses." +msgid "With `i-doit `_ integration, you can list which pieces of your company's property are related to any given ticket. That includes both physical and digital infrastructure, from servers to meeting rooms to virtual machines to software licenses." msgstr "" #: ../extras/i-doit-track-company-property.rst:15 @@ -3704,15 +3704,15 @@ msgid "(Screenshot) The i-doit integration menu in the ticket view" msgstr "" #: ../extras/i-doit-track-company-property.rst:15 -msgid "Use the 🖨 **printer** tab to view or manage a ticket’s assets from i-doit." +msgid "Use the 🖨 **printer** tab to view or manage a ticket's assets from i-doit." msgstr "" #: ../extras/i-doit-track-company-property.rst:17 -msgid "**🤔 Huh? I don’t see a 🖨 printer tab...**" +msgid "**🤔 Huh? I don't see a 🖨 printer tab...**" msgstr "" #: ../extras/i-doit-track-company-property.rst:19 -msgid "This feature is **optional**; if you don’t see it in the ticket view, that means your administrator hasn’t enabled it yet. Administrators can learn more :admin-docs:`here `." +msgid "This feature is **optional**; if you don't see it in the ticket view, that means your administrator hasn't enabled it yet. Administrators can learn more :admin-docs:`here `." msgstr "" #: ../extras/i-doit-track-company-property.rst:26 @@ -3724,7 +3724,7 @@ msgid "i-doit can help you keep track of troublesome equipment and find previous msgstr "" #: ../extras/i-doit-track-company-property.rst:31 -msgid "It’s also a great way to document quirks in the company’s belongings: Why haven’t we upgraded this system from Windows Vista yet? What did we decide to do about that faulty network switch? And why does the coffee maker keep shutting off before it’s finished? 🤬" +msgid "It's also a great way to document quirks in the company's belongings: Why haven't we upgraded this system from Windows Vista yet? What did we decide to do about that faulty network switch? And why does the coffee maker keep shutting off before it's finished? 🤬" msgstr "" #: ../extras/i-doit-track-company-property.rst:37 @@ -3736,7 +3736,7 @@ msgid "👨‍💻 **New to i-doit?**" msgstr "" #: ../extras/i-doit-track-company-property.rst:41 -msgid "Ask your administrator / IT personnel to give you a tour—otherwise, the directions below might not make much sense. (And if your organization isn’t already using i-doit, this guide is not for you.)" +msgid "Ask your administrator / IT personnel to give you a tour—otherwise, the directions below might not make much sense. (And if your organization isn't already using i-doit, this guide is not for you.)" msgstr "" #: ../extras/i-doit-track-company-property.rst:47 @@ -3780,11 +3780,11 @@ msgid "(Screencast) See a list of all tickets for an asset in i-doit" msgstr "" #: ../extras/i-doit-track-company-property.rst:75 -msgid "Click the 💬 in the toolbar to list an asset’s tickets. Use the **🔗 Open in ticketsystem** button to open the ticket in Zammad." +msgid "Click the 💬 in the toolbar to list an asset's tickets. Use the **🔗 Open in ticketsystem** button to open the ticket in Zammad." msgstr "" #: ../extras/i-doit-track-company-property.rst:78 -msgid "You can even launch Zammad’s new ticket dialog directly from i-doit, with the asset already linked for you:" +msgid "You can even launch Zammad's new ticket dialog directly from i-doit, with the asset already linked for you:" msgstr "" #: ../extras/i-doit-track-company-property.rst:85 @@ -4728,244 +4728,244 @@ msgstr "" msgid "Secure Email" msgstr "" -#: ../extras/secure-email.rst:6 +#: ../extras/secure-email.rst:4 msgid "Zammad supports two systems of high-security email communication:" msgstr "" -#: ../extras/secure-email.rst:5 +#: ../extras/secure-email.rst:6 msgid "Pretty Good Privacy (PGP)" msgstr "" -#: ../extras/secure-email.rst:6 +#: ../extras/secure-email.rst:7 msgid "Secure/Multipurpose Internet Mail Extensions (S/MIME)." msgstr "" -#: ../extras/secure-email.rst:13 +#: ../extras/secure-email.rst:14 msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../extras/secure-email.rst:13 +#: ../extras/secure-email.rst:14 msgid "Use the 🔒 **Encrypt** and ✅ **Sign** buttons to turn on encryption and signing of outgoing emails." msgstr "" -#: ../extras/secure-email.rst:16 +#: ../extras/secure-email.rst:17 msgid "**🤔 Huh? I don't see “Sign” or “Encrypt” options in the ticket view...**" msgstr "" -#: ../extras/secure-email.rst:19 +#: ../extras/secure-email.rst:20 msgid "This feature is **optional**; if you don't see it in the ticket composer, that means your administrator hasn't enabled it yet. Administrators can learn more here:" msgstr "" -#: ../extras/secure-email.rst:24 +#: ../extras/secure-email.rst:25 msgid ":admin-docs:`PGP `" msgstr "" -#: ../extras/secure-email.rst:25 +#: ../extras/secure-email.rst:26 msgid ":admin-docs:`S/MIME `" msgstr "" -#: ../extras/secure-email.rst:28 +#: ../extras/secure-email.rst:29 msgid "Overview" msgstr "" -#: ../extras/secure-email.rst:30 +#: ../extras/secure-email.rst:31 msgid "PGP and S/MIME are the most widely-supported methods for secure email communication. With each of the systems, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../extras/secure-email.rst:37 +#: ../extras/secure-email.rst:38 msgid "Signing" msgstr "" -#: ../extras/secure-email.rst:35 +#: ../extras/secure-email.rst:36 msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../extras/secure-email.rst:37 +#: ../extras/secure-email.rst:38 msgid "In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../extras/secure-email.rst:43 +#: ../extras/secure-email.rst:44 msgid "Encryption" msgstr "" -#: ../extras/secure-email.rst:40 +#: ../extras/secure-email.rst:41 msgid "scrambles a message so that it can only be unscrambled by the intended recipient." msgstr "" -#: ../extras/secure-email.rst:43 +#: ../extras/secure-email.rst:44 msgid "In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../extras/secure-email.rst:45 +#: ../extras/secure-email.rst:46 msgid "🤝 **PGP and S/MIME are only working if the other party is using them too.**" msgstr "" -#: ../extras/secure-email.rst:48 +#: ../extras/secure-email.rst:49 msgid "Your administrator is responsible for adding all the necessary certificates and keys in Zammad's admin panel." msgstr "" -#: ../extras/secure-email.rst:51 +#: ../extras/secure-email.rst:52 msgid "In special cases it is possible that both systems are configured in your system *and* a customer is using both, as well. In this case, you have an additional button to switch between PGP and S/MIME security types. Otherwise, you just see the 🔒 **Encrypt** and ✅ **Sign** buttons." msgstr "" -#: ../extras/secure-email.rst:61 +#: ../extras/secure-email.rst:62 msgid "Screenshot of ticket creation with configured PGP and S/MIME" msgstr "" -#: ../extras/secure-email.rst:61 +#: ../extras/secure-email.rst:62 msgid "Ticket creation with configured PGP *and* S/MIME and available certificates/keys." msgstr "" -#: ../extras/secure-email.rst:65 -#: ../extras/secure-email.rst:158 +#: ../extras/secure-email.rst:66 +#: ../extras/secure-email.rst:159 msgid "📬 Incoming" msgstr "" -#: ../extras/secure-email.rst:67 +#: ../extras/secure-email.rst:68 msgid "The 🔒 and ✅ icons at the top of a message indicate its encryption and signing status." msgstr "" -#: ../extras/secure-email.rst:75 +#: ../extras/secure-email.rst:76 msgid "Screencast showing details of encryption and signing status" msgstr "" -#: ../extras/secure-email.rst:75 +#: ../extras/secure-email.rst:76 msgid "Click on an incoming message to expand its details. Hover over the security status to show more information." msgstr "" -#: ../extras/secure-email.rst:78 +#: ../extras/secure-email.rst:79 msgid "Status Icons (Incoming)" msgstr "" -#: ../extras/secure-email.rst:81 -#: ../extras/secure-email.rst:119 +#: ../extras/secure-email.rst:82 +#: ../extras/secure-email.rst:120 msgid "|lock|" msgstr "" -#: ../extras/secure-email.rst:137 -#: ../extras/secure-email.rst:137 -#: ../extras/secure-email.rst:137 +#: ../extras/secure-email.rst:138 +#: ../extras/secure-email.rst:138 +#: ../extras/secure-email.rst:138 msgid "lock" msgstr "" -#: ../extras/secure-email.rst:82 +#: ../extras/secure-email.rst:83 msgid "This message was **encrypted for you**." msgstr "" -#: ../extras/secure-email.rst:84 +#: ../extras/secure-email.rst:85 msgid "Even if it was intercepted by a third party (hacker, gov't agency, etc.), they won't be able to read it." msgstr "" -#: ../extras/secure-email.rst:87 +#: ../extras/secure-email.rst:88 msgid "|encryption-error|" msgstr "" -#: ../extras/secure-email.rst:150 -#: ../extras/secure-email.rst:150 +#: ../extras/secure-email.rst:151 +#: ../extras/secure-email.rst:151 msgid "encryption-error" msgstr "" -#: ../extras/secure-email.rst:88 +#: ../extras/secure-email.rst:89 msgid "This message can **not be decrypted**." msgstr "" -#: ../extras/secure-email.rst:90 -#: ../extras/secure-email.rst:128 +#: ../extras/secure-email.rst:91 +#: ../extras/secure-email.rst:129 msgid "|signed|" msgstr "" -#: ../extras/secure-email.rst:144 -#: ../extras/secure-email.rst:144 -#: ../extras/secure-email.rst:144 +#: ../extras/secure-email.rst:145 +#: ../extras/secure-email.rst:145 +#: ../extras/secure-email.rst:145 msgid "signed" msgstr "" -#: ../extras/secure-email.rst:91 +#: ../extras/secure-email.rst:92 msgid "This message's signature has been **successfully verified**." msgstr "" -#: ../extras/secure-email.rst:93 +#: ../extras/secure-email.rst:94 msgid "You can be confident that it's authentic and that the content has not been modified." msgstr "" -#: ../extras/secure-email.rst:96 -#: ../extras/secure-email.rst:134 +#: ../extras/secure-email.rst:97 +#: ../extras/secure-email.rst:135 msgid "|not-signed|" msgstr "" -#: ../extras/secure-email.rst:147 -#: ../extras/secure-email.rst:147 -#: ../extras/secure-email.rst:147 +#: ../extras/secure-email.rst:148 +#: ../extras/secure-email.rst:148 +#: ../extras/secure-email.rst:148 msgid "not-signed" msgstr "" -#: ../extras/secure-email.rst:97 +#: ../extras/secure-email.rst:98 msgid "The verification of the signature of this message has **failed**. You can find more information by hovering over the icon." msgstr "" -#: ../extras/secure-email.rst:101 -#: ../extras/secure-email.rst:192 +#: ../extras/secure-email.rst:102 +#: ../extras/secure-email.rst:193 msgid "📮 Outgoing" msgstr "" -#: ../extras/secure-email.rst:103 +#: ../extras/secure-email.rst:104 msgid "Use the 🔒 **Encrypt** and ✅ **Sign** buttons to turn on encryption and signing for outgoing emails." msgstr "" -#: ../extras/secure-email.rst:106 +#: ../extras/secure-email.rst:107 msgid "Outgoing emails can only be encrypted for *a single recipient*." msgstr "" -#: ../extras/secure-email.rst:113 +#: ../extras/secure-email.rst:114 msgid "Screencast showing encryption and signing status for both new tickets and replies" msgstr "" -#: ../extras/secure-email.rst:113 +#: ../extras/secure-email.rst:114 msgid "🔒 **Encrypt** and ✅ **Sign** buttons are present on both new tickets and replies. Hover over the buttons to show details." msgstr "" -#: ../extras/secure-email.rst:116 +#: ../extras/secure-email.rst:117 msgid "Status Icons (Outgoing)" msgstr "" -#: ../extras/secure-email.rst:120 +#: ../extras/secure-email.rst:121 msgid "This message **will be encrypted**." msgstr "" -#: ../extras/secure-email.rst:122 +#: ../extras/secure-email.rst:123 msgid "Even if it's intercepted by a third party (hacker, gov't agency, etc.), they won't be able to read it." msgstr "" -#: ../extras/secure-email.rst:125 +#: ../extras/secure-email.rst:126 msgid "|open-lock|" msgstr "" -#: ../extras/secure-email.rst:141 -#: ../extras/secure-email.rst:141 +#: ../extras/secure-email.rst:142 +#: ../extras/secure-email.rst:142 msgid "open-lock" msgstr "" -#: ../extras/secure-email.rst:126 +#: ../extras/secure-email.rst:127 msgid "This message **will not be encrypted**." msgstr "" -#: ../extras/secure-email.rst:129 +#: ../extras/secure-email.rst:130 msgid "This message **will be signed**." msgstr "" -#: ../extras/secure-email.rst:131 +#: ../extras/secure-email.rst:132 msgid "Recipients can verify that it came from you and that the content has not been modified." msgstr "" -#: ../extras/secure-email.rst:135 +#: ../extras/secure-email.rst:136 msgid "This message **will not be signed**." msgstr "" -#: ../extras/secure-email.rst:155 +#: ../extras/secure-email.rst:156 msgid "Troubleshooting" msgstr "" -#: ../extras/secure-email.rst:173 +#: ../extras/secure-email.rst:174 msgid "“Sign: Unable to find certificate for validation”" msgstr "" @@ -4974,55 +4974,55 @@ msgstr "" msgid "Ticket article shows a warning for failed verification of a signed message" msgstr "" -#: ../extras/secure-email.rst:165 +#: ../extras/secure-email.rst:166 msgid "Without the sender's certificate, Zammad cannot verify the message signature." msgstr "" -#: ../extras/secure-email.rst:167 +#: ../extras/secure-email.rst:168 msgid "Ask your administrator to add the sender's certificate to Zammad's certificate store." msgstr "" -#: ../extras/secure-email.rst:169 +#: ../extras/secure-email.rst:170 msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../extras/secure-email.rst:171 +#: ../extras/secure-email.rst:172 msgid "The whole point of signature verification is to alert you when someone is trying to pretend to be someone they're not. Never accept a certificate from someone online without verifying it first." msgstr "" -#: ../extras/secure-email.rst:189 +#: ../extras/secure-email.rst:190 msgid "“Encryption: Unable to find private key to decrypt”" msgstr "" -#: ../extras/secure-email.rst:180 +#: ../extras/secure-email.rst:181 msgid "This message was encrypted with a certificate that does not match any on file. Without a matching private key, Zammad cannot decrypt the message." msgstr "" -#: ../extras/secure-email.rst:183 +#: ../extras/secure-email.rst:184 msgid "Ask your administrator to verify your organization's private key in Zammad's certificate store, and ask the sender to double-check the public key they used to encrypt the message." msgstr "" -#: ../extras/secure-email.rst:186 +#: ../extras/secure-email.rst:187 msgid "📢 **Your public key can be safely shared with anyone.**" msgstr "" -#: ../extras/secure-email.rst:188 +#: ../extras/secure-email.rst:189 msgid "(But if they're smart, they'll take extra precautions to make sure it really belongs to you.)" msgstr "" -#: ../extras/secure-email.rst:195 +#: ../extras/secure-email.rst:196 msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../extras/secure-email.rst:195 +#: ../extras/secure-email.rst:196 msgid "Ask your administrator to add the recipient's certificate to Zammad's certificate store." msgstr "" -#: ../extras/secure-email.rst:197 +#: ../extras/secure-email.rst:198 msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../extras/secure-email.rst:198 +#: ../extras/secure-email.rst:199 msgid "Ask your administrator to verify your organization's private key in Zammad's certificate store." msgstr "" @@ -5040,15 +5040,15 @@ msgid "Screenshot showing the sub menu of the Update button with macros and an\n msgstr "" #: ../extras/shared-drafts.rst:12 -msgid "By using ᐱ next to the \"Update\" button Zammad will provide you with an option to save your draft (and thus share it) if the option is enabled." +msgid "By using ^ next to the \"Update\" button Zammad will provide you with an option to save your draft (and thus share it) if the option is enabled." msgstr "" #: ../extras/shared-drafts.rst:15 -msgid "**🤔 Huh? I don’t see “Share Draft” option...**" +msgid "**🤔 Huh? I don't see “Share Draft” option...**" msgstr "" #: ../extras/shared-drafts.rst:17 -msgid "This feature is **optional**; if you don’t see it in the menu, that means your administrator disabled this function. Administrators can learn more in our :admin-docs:`admin documentation `." +msgid "This feature is **optional**; if you don't see it in the menu, that means your administrator disabled this function. Administrators can learn more in our :admin-docs:`admin documentation `." msgstr "" #: ../extras/shared-drafts.rst:22 @@ -5196,7 +5196,7 @@ msgid "Existing ticket" msgstr "" #: ../extras/shared-drafts.rst:126 -msgid "Use the ᐱ button next to the update button. If the group of the ticket (or in your selection) allows shared drafts, Zammad will provide the option \"Save Draft\"." +msgid "Use the ^ button next to the update button. If the group of the ticket (or in your selection) allows shared drafts, Zammad will provide the option \"Save Draft\"." msgstr "" #: ../extras/shared-drafts.rst:130 @@ -5228,7 +5228,7 @@ msgid "Set Up Two-Factor Authentication" msgstr "" #: ../extras/two-factor-authentication.rst:18 -msgid "If the system admin has enabled this feature, you can head to \"Avatar -> Profile -> Password & Authentication\" to set it up. Depending on the enabled two-factor methods, you may see one or more options in the table." +msgid "If the system admin has enabled this feature, you can head to \"Avatar > Profile > Password & Authentication\" to set it up. Depending on the enabled two-factor methods, you may see one or more options in the table." msgstr "" #: ../extras/two-factor-authentication.rst:22 @@ -5326,7 +5326,7 @@ msgid "Recovery Codes Modal Dialog" msgstr "" #: ../extras/two-factor-authentication.rst:119 -msgid "You also have an option to regenerate your recovery codes at any time, which invalidates already existing recovery codes and provides you with a list of fresh codes. You can do this by clicking on **Regenerate recovery codes** button in \"Avatar -> Profile -> Password & Authentication\"." +msgid "You also have an option to regenerate your recovery codes at any time, which invalidates already existing recovery codes and provides you with a list of fresh codes. You can do this by clicking on **Regenerate recovery codes** button in \"Avatar > Profile > Password & Authentication\"." msgstr "" #: ../extras/two-factor-authentication.rst:125 @@ -5334,7 +5334,7 @@ msgid "Set a Two-Factor Method as Default" msgstr "" #: ../extras/two-factor-authentication.rst:127 -msgid "To set an already set up two-factor method as default, use the ⋮ **Actions** menu next to it in \"Avatar -> Profile -> Password & Authentication\" and choose **Set as default**." +msgid "To set an already set up two-factor method as default, use the ⋮ **Actions** menu next to it in \"Avatar > Profile > Password & Authentication\" and choose **Set as default**." msgstr "" #: ../extras/two-factor-authentication.rst:None @@ -5355,7 +5355,7 @@ msgid "Edit a Two-Factor Method" msgstr "" #: ../extras/two-factor-authentication.rst:145 -msgid "To edit an already set up two-factor method, use the ⋮ **Actions** menu next to it in \"Avatar -> Profile -> Password & Authentication\" and choose **Edit**." +msgid "To edit an already set up two-factor method, use the ⋮ **Actions** menu next to it in \"Avatar > Profile > Password & Authentication\" and choose **Edit**." msgstr "" #: ../extras/two-factor-authentication.rst:155 @@ -5367,7 +5367,7 @@ msgid "Remove a Two-Factor Method" msgstr "" #: ../extras/two-factor-authentication.rst:163 -msgid "To remove an already set up two-factor method, use the ⋮ **Actions** menu next to it in \"Avatar -> Profile -> Password & Authentication\" and choose **Remove**." +msgid "To remove an already set up two-factor method, use the ⋮ **Actions** menu next to it in \"Avatar > Profile > Password & Authentication\" and choose **Remove**." msgstr "" #: ../extras/two-factor-authentication.rst:None @@ -5388,7 +5388,7 @@ msgid "Your system admin may choose to require you to set up at least one two-fa msgstr "" #: ../extras/two-factor-authentication.rst:185 -msgid "Choose a method of your choice, and then follow its `setup guide`_." +msgid "Choose a method of your choice, and then follow its :ref:`setup guide `." msgstr "" #: ../extras/two-factor-authentication.rst:188 @@ -5428,15 +5428,11 @@ msgstr "" msgid "If your device is not able to scan the QR code, first click on it to reveal your secret. Next, add a manual entry to your authenticator app and enter the provided secret when asked." msgstr "" -#: ../extras/two-factor-authentication/authenticator-app-setup.rst:0 -msgid "Authenticator App Secret Revealed" -msgstr "" - -#: ../extras/two-factor-authentication/authenticator-app-setup.rst:33 +#: ../extras/two-factor-authentication/authenticator-app-setup.rst:29 msgid "Your authenticator app should immediately add the new entry for your Zammad account, and a 6-digit code will be displayed next to it together with a timer." msgstr "" -#: ../extras/two-factor-authentication/authenticator-app-setup.rst:36 +#: ../extras/two-factor-authentication/authenticator-app-setup.rst:32 msgid "Back in Zammad, enter the provided code to the **Security Code** field and click on **Set Up**." msgstr ""