Changes for page Helpdesk

Last modified by Sabrina V. on 2026/10/06 10:13

From version 3.1
edited by Sabrina V.
on 2026/07/27 06:17
Change comment: There is no comment for this version
To version 5.1
edited by Sabrina V.
on 2026/10/06 10:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -20,7 +20,7 @@
20 20  
21 21  
22 22  {{figure}}
23 -[[image:68_System_Einstellungen_HelpdeskE-Mail_1404.png||alt="63_System_Einstellungen_HelpdeskE-Mail_1434.png" data-xwiki-image-style-alignment="center"]]
23 +[[image:68_System_Einstellungen_HelpdeskE-Mail_1404.png||alt="63_System_Einstellungen_HelpdeskE-Mail_1434.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
24 24  
25 25  {{figureCaption}}
26 26  Settings (Email)
... ... @@ -31,7 +31,7 @@
31 31  |Template language|First, select the language in which the email templates will be used. Choose either English or German.
32 32  |Behavior of Pending Tickets|In this section, specify whether a ticket's status should change as soon as an email arrives that can be assigned to a specific ticket based on the ticket ID in the subject line. The status can be updated if the ticket's current status is “Pending.”
33 33  |Default Font/Size|You can define a default for ticket comments here.
34 -|Email Signature|Enter a signature. It will be included in every email sent by ACMP.
34 +|Email Signature|Enter a signature. It will be included in every email sent by acmp.
35 35  |Maximum size of an attachment|Specify the size threshold above which email attachments should not be automatically added. This setting applies to each individual attachment and can be specified in KiB, MiB, and GiB.
36 36  If you do not want to import any email attachments, enter 0 KB.
37 37  |Excluded Attachment Extensions|(((
... ... @@ -53,7 +53,7 @@
53 53  On this page, you'll find email templates that can be sent automatically when a specific escalation level is reached. You'll also find a template for the “Notify Assignee” option for an escalation level.
54 54  
55 55  {{figure}}
56 -[[image:68_System_Einstellungen_Helpdesk_E-MailVorlagenfürEskalationen_1278.png||alt="63_System_Einstellungen_Helpdesk_E-MailVorlagenfürEskalationen_1278.png" data-xwiki-image-style-alignment="center"]]
56 +[[image:68_System_Einstellungen_Helpdesk_E-MailVorlagenfürEskalationen_1278.png||alt="63_System_Einstellungen_Helpdesk_E-MailVorlagenfürEskalationen_1278.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
57 57  
58 58  {{figureCaption}}
59 59  Email Templates for Escalations
... ... @@ -61,7 +61,7 @@
61 61  {{/figure}}
62 62  
63 63  
64 -These templates correspond to the various escalation levels that you can define in an escalation (see [[Escalations>>doc:||anchor="HEskalationen"]]) and are visible to all ACMP Users with the Helpdesk role.
64 +These templates correspond to the various escalation levels that you can define in an escalation (see [[Escalations>>doc:||anchor="HEscalations"]]) and are visible to all acmp Users with the Helpdesk role.
65 65  
66 66  To change a template, select it from the drop-down list. The template’s current content will then be displayed in the two fields below. By default, the most important information is automatically inserted via variables. You can now change this content as needed, for example, by having the ticket ID and subject line inserted automatically.
67 67  
... ... @@ -72,7 +72,7 @@
72 72  This window displays your existing escalations. Escalations are used to highlight tickets with specific properties so that they can be edited quickly. For example, escalations can be used to raise the status of tickets, automatically send emails, or send notifications to the current editor.
73 73  
74 74  {{figure}}
75 -[[image:68_System_Einstellungen_Helpdesk_Eskalationen_1280.png||alt="63_System_Einstellungen_Helpdesk_Eskalationen_1280.png" data-xwiki-image-style-alignment="center"]]
75 +[[image:68_System_Einstellungen_Helpdesk_Eskalationen_1280.png||alt="63_System_Einstellungen_Helpdesk_Eskalationen_1280.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
76 76  
77 77  {{figureCaption}}
78 78  Settings: Escalations
... ... @@ -79,7 +79,7 @@
79 79  {{/figureCaption}}
80 80  {{/figure}}
81 81  
82 -You can [[manage>>doc:||anchor="HEskalationenverwalten"]] existing escalations using the Add, Edit, and Delete buttons. If you click on an existing escalation in the list on the left, its properties will be displayed in the corresponding fields on the right. This allows you to get a quick overview.
82 +You can [[manage>>doc:||anchor="HManageEscalations"]] existing escalations using the Add, Edit, and Delete buttons. If you click on an existing escalation in the list on the left, its properties will be displayed in the corresponding fields on the right. This allows you to get a quick overview.
83 83  
84 84  {{aagon.warnungsbox}}
85 85  For example, if a ticket has reached escalation level 3 and the corresponding escalation is subsequently changed to disable escalation level 3, the ticket will still retain escalation level 3, since tickets are not downgraded. Similarly, escalation levels are retained even if the corresponding escalation is disabled. Only when an escalation is deleted do the corresponding tickets lose their escalation levels.
... ... @@ -98,7 +98,7 @@
98 98  To create a new escalation, click the Add button. In the wizard that opens, enter a caption and a description for the escalation in the first step. Using the “Escalation is enabled” checkbox, you can decide whether this escalation should be used immediately or saved as a draft for now.
99 99  
100 100  (% style="text-align:center" %)
101 -[[image:XWiki.Images.WebHome@hmfile_hash_a20ddad0.png||alt="7.5.5.2.1 - EskalationHinzufuegen" height="599" width="712"]]
101 +[[image:XWiki.Images.WebHome@hmfile_hash_a20ddad0.png||alt="7.5.5.2.1 - EskalationHinzufuegen" data-cmp-info="10" height="599" width="712"]]
102 102  Settings: Add escalation
103 103  
104 104  In the next step, you can use filters to select which tickets this escalation should apply to. All fields in a ticket are available as possible filters. These filters work similarly to those used in Queries. For information on how to use filters, see [[Creating a New Query>>doc:ACMP.610.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen erstellen.WebHome]].
... ... @@ -109,11 +109,11 @@
109 109  
110 110  In the final step, you can assign one or more actions to escalated tickets for each escalation level. The escalation levels are based on the ticket's creation date or the date of its last change. A maximum of five levels are provided:
111 111  
112 -|(% style="width:145px" %)[[image:ticketescalationlevel_1_zoom50.png||alt="TicketEscalationLevel_1" height="16" width="16"]]|(% style="width:1216px" %)Escalation Levels 1
113 -|(% style="width:145px" %)[[image:ticketescalationlevel_2_zoom50.png||alt="TicketEscalationLevel_2" height="16" width="16"]]|(% style="width:1216px" %)Escalation Levels 2
114 -|(% style="width:145px" %)[[image:ticketescalationlevel_3_zoom50.png||alt="TicketEscalationLevel_3" height="16" width="16"]]|(% style="width:1216px" %)Escalation Levels 3
115 -|(% style="width:145px" %)[[image:ticketescalationlevel_4_zoom50.png||alt="TicketEscalationLevel_4" height="16" width="16"]]|(% style="width:1216px" %)Escalation Levels 4
116 -|(% style="width:145px" %)[[image:ticketescalationlevel_5_zoom50.png||alt="TicketEscalationLevel_5" height="16" width="16"]]|(% style="width:1216px" %)Escalation Levels 5
112 +|(% style="width:145px" %)[[image:ticketescalationlevel_1_zoom50.png||alt="TicketEscalationLevel_1" data-cmp-info="10" height="16" width="16"]]|(% style="width:1216px" %)Escalation Levels 1
113 +|(% style="width:145px" %)[[image:ticketescalationlevel_2_zoom50.png||alt="TicketEscalationLevel_2" data-cmp-info="10" height="16" width="16"]]|(% style="width:1216px" %)Escalation Levels 2
114 +|(% style="width:145px" %)[[image:ticketescalationlevel_3_zoom50.png||alt="TicketEscalationLevel_3" data-cmp-info="10" height="16" width="16"]]|(% style="width:1216px" %)Escalation Levels 3
115 +|(% style="width:145px" %)[[image:ticketescalationlevel_4_zoom50.png||alt="TicketEscalationLevel_4" data-cmp-info="10" height="16" width="16"]]|(% style="width:1216px" %)Escalation Levels 4
116 +|(% style="width:145px" %)[[image:ticketescalationlevel_5_zoom50.png||alt="TicketEscalationLevel_5" data-cmp-info="10" height="16" width="16"]]|(% style="width:1216px" %)Escalation Levels 5
117 117  
118 118  By default, only the first level is active. To use additional levels, enable them using the “Active” checkbox. Higher levels can only be enabled if all lower levels are also enabled.
119 119  Please note that when combining the “Creation Date” and “Last Modified” options, you must ensure a logical sequence; otherwise, you could, for example, reach Escalation Level 3 before Escalation Level 2.
... ... @@ -120,7 +120,7 @@
120 120  First, specify after how many hours/days and based on the “Creation Date” or “Last Modified” date this escalation level is reached. You can then choose various actions: Notify Editor, Send Email To, and Set Priority. Choose the actions using the checkboxes in the corresponding drop-down field. Depending on your selection, the fields associated with the action will be displayed.
121 121  
122 122  (% style="text-align:center" %)
123 -[[image:XWiki.Images.WebHome@hmfile_hash_e2f2d636.png||alt="7.5.5.2.1 - Levels" height="598" width="714"]]
123 +[[image:XWiki.Images.WebHome@hmfile_hash_e2f2d636.png||alt="7.5.5.2.1 - Levels" data-cmp-info="10" height="598" width="714"]]
124 124  Settings: Add an escalation level
125 125  
126 126  You can use “Change Priority” to set the priority so that this ticket, for example, appears in a relevant Query or so that another defined escalation can take over this ticket.
... ... @@ -127,14 +127,13 @@
127 127  
128 128  Using the “Email to” option, you can set up an automatic email to be sent when this escalation level is reached. To do this, enter the recipients’ email addresses in the corresponding field. If multiple people are to receive this email, separate the individual addresses with semicolons.
129 129  
130 -You can use the “Use Custom Email” checkbox to send a predefined email (see [[Email templates>>doc:||anchor="HE-MailVorlagenfFCrEskalationen"]]). If you disable this checkbox, two additional fields will appear below where you can assign a custom subject line and body text to the email to be sent. You can use ACMP-specific variables in your email.
130 +You can use the “Use Custom Email” checkbox to send a predefined email (see [[Email templates>>doc:||anchor="HEmailTemplatesforEscalations"]]). If you disable this checkbox, two additional fields will appear below where you can assign a custom subject line and body text to the email to be sent. You can use acmp -specific variables in your email.
131 131  
132 -“Notify Editor,” “Notify User,” and “Notify Group” are additional options. Standard emails are sent in these cases (see [[Email templates>>doc:||anchor="HE-MailVorlagenfFCrEskalationen"]]). For the “Notify User/Group” option, you must also select the recipients.
132 +“Notify Editor,” “Notify User,” and “Notify Group” are additional options. Standard emails are sent in these cases (see [[Email templates>>doc:||anchor="HEmailTemplatesforEscalations"]]). For the “Notify User/Group” option, you must also select the recipients.
133 133  
134 134  After the configuration of the escalation levels, click “Done” to create this escalation.
135 135  
136 136  
137 -
138 138  === **Edit Escalation** ===
139 139  
140 140  To edit an existing escalation, select it and click the corresponding button. The same wizard that appears when creating an escalation will open, with the existing parameters already filled in. Navigate through the wizard and change the relevant sections. Then save your changes by clicking the Save icon.
... ... @@ -186,7 +186,7 @@
186 186  Using the radio buttons next to the solutions, you can select a default value that will be automatically applied to every new ticket. Keep in mind that a ticket can only be closed if its solution status is something other than “No Solution.”
187 187  
188 188  {{figure}}
189 -[[image:68_System_Einstellungen_Helpdesk_Lösungen_1039.png||alt="63_System_Einstellungen_Helpdesk_Lösungen_1039.png" data-xwiki-image-style-alignment="center"]]
188 +[[image:68_System_Einstellungen_Helpdesk_Lösungen_1039.png||alt="63_System_Einstellungen_Helpdesk_Lösungen_1039.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
190 190  
191 191  {{figureCaption}}
192 192  Settings (Solutions)
... ... @@ -201,7 +201,7 @@
201 201  
202 202  In this section, you can specify the languages to be included in the spell check.
203 203  
204 -During the installation of ACMP 5.4, the German and English dictionaries are already included.
203 +During the installation of acmp 5.4, the German and English dictionaries are already included.
205 205  
206 206  === **Add Language** ===
207 207  
... ... @@ -235,7 +235,7 @@
235 235  Please note that the adjustments are saved in the local profile and are therefore available on other clients.
236 236  Storage location of the local dictionary:
237 237  %LOCALAPPDATA%\Aagon\ACMPConsole
238 -We recommend that you add all the terms you use to the dictionary and then distribute them via Client Command to the clients on which ACMP Helpdesk is running.
237 +We recommend that you add all the terms you use to the dictionary and then distribute them via Client Command to the clients on which acmp Helpdesk is running.
239 239  {{/aagon.infobox}}
240 240  
241 241  = Rules =
... ... @@ -243,7 +243,7 @@
243 243  In this section, you can configure rules that are triggered by specific Events.
244 244  
245 245  {{figure}}
246 -[[image:68_System_Einstellungen_Helpdesk_Regeln_1039.png||alt="63_System_Einstellungen_Helpdesk_Regeln_1039.png" data-xwiki-image-style-alignment="center"]]
245 +[[image:68_System_Einstellungen_Helpdesk_Regeln_1039.png||alt="63_System_Einstellungen_Helpdesk_Regeln_1039.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
247 247  
248 248  {{figureCaption}}
249 249  Configure Rules
... ... @@ -254,25 +254,25 @@
254 254  You have the following options for editing rules:
255 255  
256 256  |(((
257 -[[image:ACMP.63.ACMP-Solutions.Client-Management.Managed Software.Managed Software einrichten.System-Einstellungen für Managed Software anpassen.WebHome@Add.ico||alt="add" data-xwiki-image-style-alignment="center" height="32" width="32"]]
256 +[[image:ACMP.63.ACMP-Solutions.Client-Management.Managed Software.Managed Software einrichten.System-Einstellungen für Managed Software anpassen.WebHome@Add.ico||alt="add" data-cmp-info="10" data-xwiki-image-style-alignment="center" height="32" width="32"]]
258 258  )))|Opens a wizard for adding a new rule to the selected event.
259 259  |(((
260 -[[image:XWiki.Images.WebHome@edit.png||alt="Edit" data-xwiki-image-style-alignment="center" height="32" width="32"]]
259 +[[image:XWiki.Images.WebHome@edit.png||alt="Edit" data-cmp-info="10" data-xwiki-image-style-alignment="center" height="32" width="32"]]
261 261  )))|Opens a wizard for editing the selected rule.
262 262  |(((
263 -[[image:XWiki.Images.WebHome@delete.png||alt="Delete" data-xwiki-image-style-alignment="center" height="32" width="32"]]
262 +[[image:XWiki.Images.WebHome@delete.png||alt="Delete" data-cmp-info="10" data-xwiki-image-style-alignment="center" height="32" width="32"]]
264 264  )))|Deletes the selected rule.
265 265  |(((
266 -[[image:XWiki.Images.WebHome@priority_first.png||alt="Priority_First" data-xwiki-image-style-alignment="center" height="32" width="32"]]
265 +[[image:XWiki.Images.WebHome@priority_first.png||alt="Priority_First" data-cmp-info="10" data-xwiki-image-style-alignment="center" height="32" width="32"]]
267 267  )))|Moves the selected rule to the top of the Event.
268 268  |(((
269 -[[image:ACMP.63.First Steps im ACMP.Aufbau der Console.Ribbonleiste.WebHome@Priority_Up.svg||alt="Priority_Up" data-xwiki-image-style-alignment="center" height="32" width="32"]]
268 +[[image:ACMP.63.First Steps im ACMP.Aufbau der Console.Ribbonleiste.WebHome@Priority_Up.svg||alt="Priority_Up" data-cmp-info="10" data-xwiki-image-style-alignment="center" height="32" width="32"]]
270 270  )))|Moves the selected rule up one position within the Event.
271 271  |(((
272 -[[image:XWiki.Images.WebHome@priority_down.png||alt="Priority_Down" data-xwiki-image-style-alignment="center" height="32" width="32"]]
271 +[[image:XWiki.Images.WebHome@priority_down.png||alt="Priority_Down" data-cmp-info="10" data-xwiki-image-style-alignment="center" height="32" width="32"]]
273 273  )))|Moves the selected rule down one position within the Event.
274 274  |(((
275 -[[image:XWiki.Images.WebHome@priority_last.png||alt="Priority_Last" data-xwiki-image-style-alignment="center" height="32" width="32"]]
274 +[[image:XWiki.Images.WebHome@priority_last.png||alt="Priority_Last" data-cmp-info="10" data-xwiki-image-style-alignment="center" height="32" width="32"]]
276 276  )))|Moves the selected rule to the end of the event.
277 277  
278 278  Moves the selected rule to the end of the event.
... ... @@ -279,7 +279,7 @@
279 279  
280 280  |=Event|=The rule applies when...
281 281  |Ticket created|a ticket is created.
282 -|Ticket created by ACMP Console|a ticket is created from the ACMP Console.
281 +|Ticket created by acmp Console|a ticket is created from the acmp Console.
283 283  |Ticket created by SelfService|a ticket is created via Self Service.
284 284  |Ticket Created from Email|a ticket is created via email.
285 285  |Ticket created by Client Command|a ticket is created by a Client Command.
... ... @@ -306,7 +306,7 @@
306 306  After selecting the event to which the rule should apply, click the //Add Rule// button. This will open the wizard for creating the rule.
307 307  
308 308  {{figure}}
309 -[[image:63_System_Einstellungen_Helpdesk_Regelnhinzufügen_713.png||data-xwiki-image-style-alignment="center"]]
308 +[[image:63_System_Einstellungen_Helpdesk_Regelnhinzufügen_713.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
310 310  
311 311  {{figureCaption}}
312 312  Add rule
... ... @@ -317,7 +317,7 @@
317 317  By default, every new rule you add is enabled. If you do not want to enable the rule, disable the “Rule is active” checkbox. The second checkbox prevents all subsequent rules for this event from being executed. However, any actions executed up to that point may still trigger continuing events. This option is disabled by default. In the lower section, you can enter an optional description of the rule. On the following page, you can specify the conditions that must be met for the rule to be executed. You can access all contact and ticket fields.
318 318  
319 319  {{figure}}
320 -[[image:63_System_Einstellungen_Helpdesk_Regeln_Bedingungen_720.png||data-xwiki-image-style-alignment="center"]]
319 +[[image:63_System_Einstellungen_Helpdesk_Regeln_Bedingungen_720.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
321 321  
322 322  {{figureCaption}}
323 323  Configure Conditions
... ... @@ -325,7 +325,7 @@
325 325  {{/figure}}
326 326  
327 327  
328 -You can copy and remove conditions that have already been added using the context menu. Once you have specified all the conditions, click Next to proceed to the [[actions>>doc:||anchor="HAktionen"]] to be performed by the rule.
327 +You can copy and remove conditions that have already been added using the context menu. Once you have specified all the conditions, click Next to proceed to the [[actions>>doc:||anchor="HActions"]] to be performed by the rule.
329 329  
330 330  {{aagon.infobox}}
331 331  If you want the rule to be triggered for every event, you can also clear the conditions and use “Next” to specify the action right away.
... ... @@ -348,7 +348,7 @@
348 348  
349 349  To add an action to a rule, double-click the rule or drag and drop it into the Selected Actions window. A dialog box will then open, allowing you to configure the action.
350 350  
351 -[[Add an action>>image:Aktionen_Übersicht.png||alt="Aktion hinzufügen"]]
350 +[[Add an action>>image:Aktionen_Übersicht.png||alt="Aktion hinzufügen" data-cmp-info="10"]]
352 352  
353 353  You can choose from the following actions:
354 354  
... ... @@ -361,9 +361,9 @@
361 361  )))
362 362  |Send email|You can create a free-form email that will be sent as part of this action. You can specify a recipient and add recipients to the CC and BCC fields. You are not limited to existing contacts; you can also enter new email addresses.
363 363  
364 -|Send email template|First, choose whether you want to use an [[internal email template>>doc:||anchor="HInterneE-MailVorlagen"]] or a [[contact email template>>doc:||anchor="HKontaktE-MailVorlagen"]]. Then specify who the recipients of the email should be.
365 -|Change category|Change the tickets category. You can select one of your defined [[categories>>doc:||anchor="HKategorien"]].
366 -|Change solution|Change the resolution of the ticket. You can select one of your defined [[resolutions>>doc:||anchor="HLF6sungen"]].
363 +|Send email template|First, choose whether you want to use an [[internal email template>>doc:||anchor="HInternalEmailTemplates"]] or a [[contact email template>>doc:||anchor="HEmailTemplateContact"]]. Then specify who the recipients of the email should be.
364 +|Change category|Change the tickets category. You can select one of your defined [[categories>>doc:||anchor="HCategories"]].
365 +|Change solution|Change the resolution of the ticket. You can select one of your defined [[resolutions>>doc:||anchor="HSolutions"]].
367 367  |Change priority|(((
368 368  Change the ticket's priority. You can choose between //Minor, Normal, Important, and Critical//.
369 369  )))
... ... @@ -379,7 +379,7 @@
379 379  In this section, you can define text modules for creating Helpdesk tickets.
380 380  
381 381  {{figure}}
382 -[[image:68_System_Einstellungen_Helpdesk_Textbausteine_1280.png||alt="63_System_Einstellungen_Helpdesk_Textbausteine_1280.png" data-xwiki-image-style-alignment="center"]]
381 +[[image:68_System_Einstellungen_Helpdesk_Textbausteine_1280.png||alt="63_System_Einstellungen_Helpdesk_Textbausteine_1280.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
383 383  
384 384  {{figureCaption}}
385 385  Configure text moduls
... ... @@ -395,7 +395,7 @@
395 395  On this page, you can select various fields that can or must be filled out when creating a new ticket. You can specify which fields are available here in addition to the basic fields under [[Custom Fields>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.Benutzerdefinierte Felder.WebHome]]. After making a change, save it by clicking Save in the ribbon.
396 396  
397 397  {{figure}}
398 -[[image:68_System_Einstellungen_Helpdesk_Ticketfelder_1812.png||alt="63_System_Einstellungen_Helpdesk_Ticketfelder_1812.png" data-xwiki-image-style-alignment="center"]]
397 +[[image:68_System_Einstellungen_Helpdesk_Ticketfelder_1812.png||alt="63_System_Einstellungen_Helpdesk_Ticketfelder_1812.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
399 399  
400 400  {{figureCaption}}
401 401  Settings (Ticket fields)
... ... @@ -425,10 +425,10 @@
425 425  
426 426  = Print Tickets =
427 427  
428 -Using the //Print Tickets// setting, you can select the ACMP reports you want to use for the printout. The available reports are listed here in both German and English. The report marked as “Default” is used when you select the Print button in the Helpdesk. All other selected reports are available in the drop-down menu. You can only select one report at a time, which is preselected and suggested to you in the Helpdesk.
427 +Using the //Print Tickets// setting, you can select the acmp reports you want to use for the printout. The available reports are listed here in both German and English. The report marked as “Default” is used when you select the Print button in the Helpdesk. All other selected reports are available in the drop-down menu. You can only select one report at a time, which is preselected and suggested to you in the Helpdesk.
429 429  
430 430  {{figure}}
431 -[[image:68_Einstellungen_Tickets drucken_879.png||alt="68_Einstellungen_Helpdesk_Ausdruck_1220.png" data-xwiki-image-style-alignment="center"]]
430 +[[image:68_Einstellungen_Tickets drucken_879.png||alt="68_Einstellungen_Helpdesk_Ausdruck_1220.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
432 432  
433 433  {{figureCaption}}
434 434  Ticket Printouts
... ... @@ -448,7 +448,7 @@
448 448  If the “Require entry of working times when closing a ticket” checkbox is selected, a dialog box will automatically open when the ticket is closed, allowing you to record the working times.
449 449  
450 450  {{figure}}
451 -[[image:68_System_Einstellungen_Helpdesk_Zeiterfassung_612.PNG||data-xwiki-image-style-alignment="center"]]
450 +[[image:68_System_Einstellungen_Helpdesk_Zeiterfassung_612.PNG||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
452 452  
453 453  {{figureCaption}}
454 454  Settings (Time Tracking)
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community