The view of a ticket mainly consists of the conversation list, supplemented by additional, aggregated information in the header and the ticket extensions.
The header of a ticket always contains a preceding icon followed by a text. The source of both can be changed in the layout settings of the ticket. The header is supplemented by detailed information: the ticket number, creation date and the ticket owner.
On the right side of the core information of the header there are:
Note: The ticket owner has a link to the users data in the Users and Groups application. The prerequisite for this is that the logged in user has the permission Users and Groups.
Note: If a ticket is being processed, this is marked on the icon of the user who is editing it. Only this user has write access at the moment.
Note: If the ticket is part of a bundle, an additional note will be issued.
Note: If the ticket is part of a bundle, an additional note will be issued. It is no longer possible to delete this ticket.
The following options are available to the user via the header:
In the conversation list the sequence of the processing steps of the ticket is being displayed. The list is sorted reverse chronologically (the latest changes are at the top). The most important information of processing steps are:
Most of the processing steps also have an options button, for example to change the description text.
The effort can be updated if the change option is enabled in the configuration. To initiate the change, go to the menu of the editing step or click on the stopwatch icon located in front of the processing time of the step.
Processing steps can be produced by the Task Planner, a Quick Ticket - or both - which is indicated with a visual hint at the left side of the step. Quick Tickets, for example, can produce multiple steps for a ticket at once. In this case the indicator will be grouped over multiple steps. Hovering over the indicator shows additional links to the originating Task Planner tasks or Quick Ticket, if the user has the corresponding permissions.
There is a line with actions between the header of the ticket and the conversation list to process a ticket. Depending on the status of the ticket, this line only contains the allowed actions. The order of the actions changes automatically - for each user individually - with the frequency of their use. For example, if the "Edit" action is used significantly more often than "Close", it will be placed further up in the list of actions.
A conversation, e.g. via email, often contains a lot of duplicate content due to responses from previous emails. This duplicate content is detected in plain text and HTML emails and hidden if it is at the end of the email. This shortens the length of the conversation list. Duplicate content is pointed out to the user by a small button that can be used to show this content again.
Note: Only whole paragraphs can be hidden. If only one paragraph is detected as duplicate content, it must contain at least 50 words or images before it is hidden.
Ticket extensions provide further information about a ticket. The extensions shown can be changed and sorted in the Ticket Layout Settings.
Note: The visual proportions of the conversation and extension list can be changed by dragging and dropping the separator between the two lists.