Fixes #1190 - Add 'default for closed tickets' explanation to state object

locale/admin-docs.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Zammad Admin Documentation pre-release\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-06-17 08:42+0200\n"
+"POT-Creation-Date: 2026-06-24 09:57+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -687,8 +687,8 @@ msgstr ""
 #: ../misc/variables/config.rst:1
 #: ../misc/variables/current-user.rst:1
 #: ../misc/variables/ticket.rst:1
-#: ../system/objects.rst:132
-#: ../system/objects.rst:236
+#: ../system/objects.rst:135
+#: ../system/objects.rst:239
 msgid "Name"
 msgstr ""
 
@@ -773,8 +773,8 @@ msgstr ""
 #: ../system/integrations/cti/includes/inbound-calls.include.rst:15
 #: ../system/integrations/cti/includes/inbound-calls.include.rst:15
 #: ../system/integrations/cti/includes/outbound-calls.include.rst:18
-#: ../system/objects.rst:163
-#: ../system/objects.rst:248
+#: ../system/objects.rst:166
+#: ../system/objects.rst:251
 msgid "Note"
 msgstr ""
 
@@ -797,8 +797,8 @@ msgstr ""
 #: ../manage/scheduler.rst:164
 #: ../manage/templates.rst:33
 #: ../manage/webhook/add.rst:134
-#: ../system/objects.rst:170
-#: ../system/objects.rst:250
+#: ../system/objects.rst:173
+#: ../system/objects.rst:253
 msgid "Active"
 msgstr ""
 
@@ -1166,7 +1166,7 @@ msgstr ""
 
 #: ../channels/email/accounts/account-setup.rst:122
 #: ../misc/object-conditions/basics.rst:206
-#: ../system/objects.rst:155
+#: ../system/objects.rst:158
 msgid "Type"
 msgstr ""
 
@@ -22326,7 +22326,7 @@ msgstr ""
 msgid "Screenshot showing highlighted ticket state attribute"
 msgstr ""
 
-#: ../system/objects.rst:124
+#: ../system/objects.rst:127
 msgid "Handling of states"
 msgstr ""
 
@@ -22347,170 +22347,174 @@ msgid "To add a new state, click on the ``New Ticket State`` button in the top r
 msgstr ""
 
 #: ../system/objects.rst:116
-msgid "You can also clone a state or set them to **Default for new tickets** or **Default for follow-ups** by clicking on the ⁝ action button and select the desired function."
+msgid "You can also clone a state or set it as default for certain state types by clicking on the ⁝ action button and select the desired function."
 msgstr ""
 
-#: ../system/objects.rst:120
+#: ../system/objects.rst:119
 msgid "**Default for new tickets** means that this state is used for every newly created ticket."
 msgstr ""
 
-#: ../system/objects.rst:123
+#: ../system/objects.rst:122
 msgid "**Default for follow-ups** means that this state is used if the ticket is re-opened after it was closed."
 msgstr ""
 
-#: ../system/objects.rst:172
+#: ../system/objects.rst:125
+msgid "**Default for closed tickets** means that this state is used when an agent uses the keyboard shortcut to update a ticket as closed (usually you will just have one state of this type anyway)."
+msgstr ""
+
+#: ../system/objects.rst:175
 msgid "Ticket state in detail"
 msgstr ""
 
-#: ../system/objects.rst:127
+#: ../system/objects.rst:130
 msgid "Below you can find a description for each field and option. Please head over to the :ref:`example <example-state>` to see the edit dialog."
 msgstr ""
 
-#: ../system/objects.rst:131
+#: ../system/objects.rst:134
 msgid "This is the name of the state and what you and your agents are seeing when choosing a state somewhere (e.g. in tickets, trigger configuration)."
 msgstr ""
 
-#: ../system/objects.rst:139
+#: ../system/objects.rst:142
 msgid "There are different state types you can choose from. By default, Zammad comes with one state per state type."
 msgstr ""
 
-#: ../system/objects.rst:142
+#: ../system/objects.rst:145
 msgid "**new**: for states for tickets that are new and it hasn't been worked on them"
 msgstr ""
 
-#: ../system/objects.rst:144
+#: ../system/objects.rst:147
 msgid "**open**: for states for tickets that are in progress and agents are working on them"
 msgstr ""
 
-#: ../system/objects.rst:146
+#: ../system/objects.rst:149
 msgid "**pending reminder**: for states for tickets that are in progress and you want to set a reminder. (default example: *pending reminder*)"
 msgstr ""
 
-#: ../system/objects.rst:148
+#: ../system/objects.rst:151
 msgid "**pending action**: for states for tickets that are waiting for a specified time and then change their state (default example: *pending close*)"
 msgstr ""
 
-#: ../system/objects.rst:151
+#: ../system/objects.rst:154
 msgid "**closed**: for states for tickets that are finished and do not need to be processed further"
 msgstr ""
 
-#: ../system/objects.rst:154
+#: ../system/objects.rst:157
 msgid "⚠️ Choosing the correct state type is important! If you are in doubt, have a look on the default states and their types!"
 msgstr ""
 
-#: ../system/objects.rst:159
+#: ../system/objects.rst:162
 msgid "Ignore escalation"
 msgstr ""
 
-#: ../system/objects.rst:158
+#: ../system/objects.rst:161
 msgid "Here you can define whether tickets of this state will count to escalation time or not."
 msgstr ""
 
-#: ../system/objects.rst:162
+#: ../system/objects.rst:165
 msgid "You can create a note for the state to inform other admins about the state. This has no effect on tickets."
 msgstr ""
 
-#: ../system/objects.rst:166
+#: ../system/objects.rst:169
 msgid "Set the state to **active** or **inactive**."
 msgstr ""
 
-#: ../system/objects.rst:168
+#: ../system/objects.rst:171
 msgid "it is technically possible to set all states to inactive. To keep Zammad working in such a case, the inactive flag of one of the states is ignored."
 msgstr ""
 
-#: ../system/objects.rst:195
+#: ../system/objects.rst:198
 msgid "Ticket state example"
 msgstr ""
 
-#: ../system/objects.rst:175
+#: ../system/objects.rst:178
 msgid "Let's assume we want to create a new state which indicates that the ticket has to wait for a response of a third party (e.g. service contractor or manufacturer) and we want to to be able to set a reminder."
 msgstr ""
 
-#: ../system/objects.rst:179
+#: ../system/objects.rst:182
 msgid "First we give the new state a proper name. In this example we call it \"waiting for manufacturer\"."
 msgstr ""
 
-#: ../system/objects.rst:182
+#: ../system/objects.rst:185
 msgid "As state type we choose \"pending reminder\". This indicates that the ticket is still open and we can set a reminder. This reminder can be useful if our manufacturer sometimes isn't responding or we want to remind him to give us an answer."
 msgstr ""
 
-#: ../system/objects.rst:187
+#: ../system/objects.rst:190
 msgid "We choose \"no\" for **ignore escalation** because we want to escalate the tickets even if we are waiting on the manufacturer's feedback."
 msgstr ""
 
-#: ../system/objects.rst:190
+#: ../system/objects.rst:193
 msgid "The **result** in the creation dialog will look like this:"
 msgstr ""
 
 #: ../system/objects.rst:0
 msgid "Screenshot showing ticket state creation dialog with example"
 msgstr ""
 
-#: ../system/objects.rst:200
+#: ../system/objects.rst:203
 msgid "Ticket Priority"
 msgstr ""
 
-#: ../system/objects.rst:202
+#: ../system/objects.rst:205
 msgid "If the pre-configured priorities aren't enough for you or you want to change them, you can do so by clicking on the cogwheel icon in the priority row in the ticket tab:"
 msgstr ""
 
 #: ../system/objects.rst:None
 msgid "Screenshot showing highlighted ticket priority attribute"
 msgstr ""
 
-#: ../system/objects.rst:228
+#: ../system/objects.rst:231
 msgid "Handling of priorities"
 msgstr ""
 
-#: ../system/objects.rst:212
+#: ../system/objects.rst:215
 msgid "In the priority configuration screen, you can add new priorities, disable priorities or change priorities."
 msgstr ""
 
 #: ../system/objects.rst:0
 msgid "Screenshot showing table of default ticket priorities"
 msgstr ""
 
-#: ../system/objects.rst:220
+#: ../system/objects.rst:223
 msgid "To add a new priority, click on the ``New Priority`` button in the top right corner. To change an existing priority, simply click on the affected priority. This opens an edit dialog."
 msgstr ""
 
-#: ../system/objects.rst:224
+#: ../system/objects.rst:227
 msgid "You can also clone a priority or set them to **Default for new tickets** by clicking on the ⁝ action button and select the desired function."
 msgstr ""
 
-#: ../system/objects.rst:227
+#: ../system/objects.rst:230
 msgid "**Default for new tickets** means that this priority is used for every newly created ticket."
 msgstr ""
 
-#: ../system/objects.rst:250
+#: ../system/objects.rst:253
 msgid "Priorities in detail"
 msgstr ""
 
-#: ../system/objects.rst:231
+#: ../system/objects.rst:234
 msgid "Below you can find a description for each field and option."
 msgstr ""
 
-#: ../system/objects.rst:234
+#: ../system/objects.rst:237
 msgid "This is the name of the priority and what you and your agents are seeing when choosing a priority somewhere (e.g. in tickets, trigger configuration)."
 msgstr ""
 
-#: ../system/objects.rst:244
+#: ../system/objects.rst:247
 msgid "Highlight color"
 msgstr ""
 
-#: ../system/objects.rst:239
+#: ../system/objects.rst:242
 msgid "Switch between **Low priority** (light blue), **High priority** (red) and - (default). This affects the displayed color for ticket titles in overviews."
 msgstr ""
 
-#: ../system/objects.rst:243
+#: ../system/objects.rst:246
 msgid "The color options are currently limited to the mentioned options."
 msgstr ""
 
-#: ../system/objects.rst:247
+#: ../system/objects.rst:250
 msgid "You can create a note for the priority to inform other admins about the priority. This has no effect on tickets."
 msgstr ""
 
-#: ../system/objects.rst:251
+#: ../system/objects.rst:254
 msgid "Set the priority to **active** or **inactive**."
 msgstr ""
 

system/objects.rst

@@ -113,16 +113,19 @@ Handling of states
    corner. To change an existing state, simply click on the affected state. This
    opens an edit dialog.
 
-   You can also clone a state or set them to **Default for new tickets** or
-   **Default for follow-ups** by clicking on the ⁝ action button and select the
-   desired function.
+   You can also clone a state or set it as default for certain state types by
+   clicking on the ⁝ action button and select the desired function.
 
    **Default for new tickets** means that this state is used for every newly
    created ticket.
 
    **Default for follow-ups** means that this state is used if the ticket is
    re-opened after it was closed.
 
+   **Default for closed tickets** means that this state is used when an agent
+   uses the keyboard shortcut to update a ticket as closed (usually you will
+   just have one state of this type anyway).
+
 Ticket state in detail
    Below you can find a description for each field and option. Please head over
    to the :ref:`example <example-state>` to see the edit dialog.