Statuses
Define statuses and permitted transitions for each ticket type. Configure SLA pauses, automatic closure and reminder rules.
Status configuration
Statuses represent the stages of a ticket’s workflow. Define them for each ticket type: some processes share statuses, while others, such as Incident Management and Problem Management, need different stages.
Select the Ticket Type whose statuses you want to configure.
Click ‘Add new’ to add a status.
Now you have to name each status by adding ‘Value’ (any text) and select ‘Status type’ from the available list. At any moment you can add new status – just click the ‘Add new’ button. To delete any of the positions use the button.
For each status, you can also select a custom color. Click on the button to open a small window where you can choose a desired color from the palette.
Repeat this step for each status that needs a colour.
Those particular colors will be visible for Agent and Client in the ‘Dashboard’ view, on the list of tickets, in the ‘Status’ column.
One of last thing in this part of the system is that for any of the statuses you can select ‘Stops SLA resolution time’ and ‘Stops SLA update time’. It means that when a Ticket enters this particular status (either automatically or manually when an Agent changes the status) SLA timer for this ticket (if there is a Service along with SLA attached) will be stopped. For example, if a status has the checkbox ‘Stops SLA resolution time’ checked
and the status of the ticket is changed, then the resolution time counter will stop
The last option is the ‘Exclude for UI’ checkbox. Checking this option means that the given status will be hidden from the available options on the ticket preview.
Once you finish, in order to save your changes, use the button.
When the button to save is pressed, the option to specify workflow statuses will be unlocked.
This configuration indicates that you can only go from open status to InProgress status. From InProgress status, you can switch to Pending, Closed and ReOpened.
Pending autoclose
In Pending Autoclose you can specify how much time must elapse for a ticket in this status to be closed. It is important that after a timeout, the system will automatically select the first status of type Closed from the list in Admin → Statuses, ignoring the settings in the Statuses Flow field. If there are several statuses of type Closed, the one highest on the list will be selected.
Configure Pending Autoclose for the selected ticket type.
In the Duration field, we set the time that must elapse before the ticket is closed. You can set:
- 1m = 1 minute
- 1h = 1 hour
- 1d = 1 day
- 1w = 1 week
For example: 1w6h30m = 1 week 6 hours 30 minutes. Lets fill this field with 1 day (1d).
We are also able to establish Strike rules, which involve the configuration of notifications for this status as a certain amount of time elapses. To do this, first, we establish the configuration described in the Tickets → Strike rule section (click here to visit). Then we proceed to the Pending Autoclose status we want to set, and after clicking on the Strike rule dropdown menu, we select the configuration we have set.
After clicking the button, the setting is saved.
When a ticket transitions to Pending Autoclose and its status isn’t changed within the predetermined time frame, the ticket will be closed automatically. Additionally, designated recipients will receive reminders according to settings in Notifications and based on the percentage of time elapsed, as configured in the Strike rule. For instance, if we’ve chosen a configuration with three notifications, they will be sent according to the following example schedule saved in Strike rule section:
This means that reminders will be sent respectively after: • 6 hours (first reminder) • 12 hours (second reminder) • 18 hours (third reminder)
The notification configuration is described in the Notifications section (click here to visit).