# Statuses · Tickets · Admin Portal

Define statuses and permitted transitions for each ticket type. Configure SLA pauses, automatic closure and reminder rules.

Canonical: https://docs.mintsd.com/docs/mint-service-desk/admin-portal-admin-statuses
Language: en-GB
Revision: 2a2d39f1e31deba465d9905cd685a5a3416966a588eb6151bba19ba5bc3c7cc9

<a id="element-01a1452d-fd2b-7273-b012-f7341f495e96"></a>

## 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.

<a id="element-01a1452d-fd2b-7b55-b4db-0660697cee15"></a>

![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.](https://docs.mintsd.com/api/reader/assets/assets/images/image333.png?v=d482ff39c25cbc5f2e9d9b978ddef930e5c522d654e5aae1a3a1582acf04cc24)

<a id="element-01a1452d-fd2c-7fd9-8329-ffb7e5e4c573"></a>

Select the Ticket Type whose statuses you want to configure.

<a id="element-01a1452d-fd2c-7cb2-b921-8f724a85d83d"></a>

![Statuses: Select the Ticket Type whose statuses you want to configure.](https://docs.mintsd.com/api/reader/assets/assets/images/image334.png?v=82df9653f1afe7d9bf840c2a4be08592a44b4e374b8e8bc3270d687809adcc00)

<a id="element-01a1452d-fd2d-7766-929c-6ef0be89899f"></a>

Click ‘Add new’ to add a status.

<a id="element-01a1452d-fd2d-7eab-8b14-f7ef2e59edb4"></a>

![Statuses: Click ‘Add new’ to add a status.](https://docs.mintsd.com/api/reader/assets/assets/images/image335.png?v=1a443eb35048663186582606ae49592e2ceb4e3bc585ad9de161fa77f4f52133)

<a id="element-01a1452d-fd2e-7459-87f0-0945c0e2a1e7"></a>

![Statuses: Click ‘Add new’ to add a status.](https://docs.mintsd.com/api/reader/assets/assets/images/image336.png?v=e19eaf01dc3c726841eec2f5a69b1f78bff24005a429fbfb49be103d7b18585b)

<a id="element-01a1452d-fd2e-7bbb-81a4-5e0f6493754b"></a>

<a id="element-01a1452d-fd2f-76ba-9849-58ed07864bb0"></a>

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 ![Delete](https://docs.mintsd.com/api/reader/assets/assets/images/image228.png?v=b49c174f13ec30cdd023f322f43c60d2f2e16a16d3f207ccbfa119b0906a0fe2#element-01a1452d-fd2e-7bbb-81a4-5e0f6493754b) button.

<a id="element-01a1452d-fd2f-712e-b372-9ab7c6912561"></a>

<a id="element-01a1452d-fd2f-7990-bd67-e16f47c24a93"></a>

For each status, you can also select a custom color. Click on the
![Color palette](https://docs.mintsd.com/api/reader/assets/assets/images/image338.JPG?v=16f6175b36499e9871e64f5b5ea4d2e5acf37a19d9876e54afdc0959c84bacc4#element-01a1452d-fd2f-712e-b372-9ab7c6912561) button to open a small window where you can choose a desired
color from the palette.

<a id="element-01a1452d-fd30-7c81-805f-ec2d198c7520"></a>

![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.](https://docs.mintsd.com/api/reader/assets/assets/images/image339.png?v=01d5e707df5b007081f050511308f0aedf3bb727ad4fef18dabd89db4a1cfb32)

<a id="element-01a1452d-fd30-71d8-bd87-0741f84a6797"></a>

Repeat this step for each status that needs a colour.

<a id="element-01a1452d-fd30-7037-8c01-84a19c6f38f0"></a>

![Statuses: Repeat this step for each status that needs a colour.](https://docs.mintsd.com/api/reader/assets/assets/images/image340.png?v=5c468f874a24a55b180ba709a6d4f5bb38ba3b328dc25c032652777f99d4ef20)

<a id="element-01a1452d-fd31-741a-b887-463dbb4cddb6"></a>

Those particular colors will be visible for Agent and Client in the
‘Dashboard’ view, on the list of tickets, in the ‘Status’ column.

<a id="element-01a1452d-fd32-78d8-824c-ecc407d86545"></a>

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

<a id="element-01a1452d-fd32-7f05-a2f6-978d5ce68f40"></a>

![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’.](https://docs.mintsd.com/api/reader/assets/assets/images/image341.png?v=79637344c0ebfa02e48dbff9b6ab1b69b311ee8812ee28efe73adb2cc6c7ca5f)

<a id="element-01a1452d-fd33-7d27-8cd6-db225121b187"></a>

and the status of the ticket is changed, then the resolution time counter will stop

<a id="element-01a1452d-fd33-7b2f-87b2-e6d12251e012"></a>

![Statuses: and the status of the ticket is changed, then the resolution time counter will stop.](https://docs.mintsd.com/api/reader/assets/assets/images/image348.png?v=aca60117039857f5cafaa81d956aa3a2f46a5af43fbaff06456693b7c0db6623)

<a id="element-01a1452d-fd50-7a0e-bc0d-d96d968c5512"></a>

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.

<a id="element-01a1452d-fd50-79e2-847d-fd36bac68025"></a>

![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.](https://docs.mintsd.com/api/reader/assets/assets/images/image917.png?v=9cdb2190be3a01bce603b3afbf31a4fa5b18d472fd01fdbf9191935c2ab84970)

<a id="element-01a1452d-fd51-7f30-890a-cecbda5afea9"></a>

<a id="element-01a1452d-fd51-736b-b916-08acc2c0762d"></a>

Once you finish, in order to save your changes, use the ![Save](https://docs.mintsd.com/api/reader/assets/assets/images/image8.png?v=c6dfcae62b1da5a56376cb98f40e0a593d8d731e458977d27180f6380454b49d#element-01a1452d-fd51-7f30-890a-cecbda5afea9) button.

<a id="element-01a1452d-fd51-75c6-b190-1ecf42e87f7d"></a>

When the button to save is pressed, the option to specify workflow statuses will be unlocked.

<a id="element-01a1452d-fd52-716d-b951-533b4e571734"></a>

![When the button to save is pressed, the option to specify workflow statuses will be unlocked.](https://docs.mintsd.com/api/reader/assets/assets/images/image969.png?v=8d0fc5b1252246f40993d007c3bc0c777e6037c696afb8b94affd40161c069b8)

<a id="element-01a1452d-fd52-7b79-af41-8c8910f8ef0f"></a>

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.

<a id="element-01a1452d-fd53-7c1e-914a-5d403164e39c"></a>

## Pending autoclose

<a id="element-01a1452d-fd53-718a-a183-6b82f91a36f1"></a>

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.

<a id="element-01a1452d-fd54-7104-a761-5aee5a82262b"></a>

Configure Pending Autoclose for the selected ticket type.

<a id="element-01a1452d-fd54-74a8-97c9-ebcd4d6fd674"></a>

![Statuses: Configure Pending Autoclose for the selected ticket type.](https://docs.mintsd.com/api/reader/assets/assets/images/image1127.png?v=15197a929a15d58243b5988c19d4e179e7fbcd7524138652296267c6abf8c3b7)

<a id="element-01a1452d-fd55-7b96-8fe9-44ff1def4744"></a>

In the Duration field, we set the time that must elapse before the ticket is closed. You can set:

<a id="element-01a1452d-fd57-7093-bbb0-ad6e797e418f"></a>

- 1m = 1 minute
- 1h = 1 hour
- 1d = 1 day
- 1w = 1 week

<a id="element-01a1452d-fd58-7c9d-a604-ab9c3307187e"></a>

For example: 1w6h30m = 1 week 6 hours 30 minutes. Lets fill this field with 1 day (1d).

<a id="element-01a1452d-fd58-775c-8759-30f9e63f5826"></a>

![Statuses: For example: 1w6h30m = 1 week 6 hours 30 minutes. Lets fill this field with 1 day (1d).](https://docs.mintsd.com/api/reader/assets/assets/images/image1128.png?v=8c181c3827f3ad040568802bcdb66b2669ebe2202d84d3a08e8414e96186bbfb)

<a id="element-01a1452d-fd5a-7b41-b7ac-17487ffda3e7"></a>

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)](https://docs.mintsd.com/docs/mint-service-desk/admin-portal-strike-rules#element-01a1452e-0297-7c53-8bf1-232a91c31eed). 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.

<a id="element-01a1452d-fd5b-7262-8714-dbeb52b18473"></a>

![We are also able to establish Strike rules , which involve the configuration of notifications for this status as a certain amount of time elapses.](https://docs.mintsd.com/api/reader/assets/assets/images/image1129.png?v=1d689c951aa6871e2b576ace9d24915e8ad24b04eafb94c03e3ebca49c8b992d)

<a id="element-01a1452d-fd5c-7a60-a3f0-0057339c2814"></a>

<a id="element-01a1452d-fd5c-7a1f-be0d-49eddbebf066"></a>

After clicking the ![Save](https://docs.mintsd.com/api/reader/assets/assets/images/image8.png?v=c6dfcae62b1da5a56376cb98f40e0a593d8d731e458977d27180f6380454b49d#element-01a1452d-fd5c-7a60-a3f0-0057339c2814) button, the setting is saved.

<a id="element-01a1452d-fd5d-7adf-bf9e-75e11a46f281"></a>

![Statuses: After clicking the button, the setting is saved.](https://docs.mintsd.com/api/reader/assets/assets/images/image1130.png?v=5a71a4fda138b0b96f5aad89f9972542c0fdd067dc8837797e033415ae9145e8)

<a id="element-01a1452d-fd5e-7e48-9c23-8cccf17650e9"></a>

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:

<a id="element-01a1452d-fd5e-7339-9329-cd378b3a01f5"></a>

![When a ticket transitions to Pending Autoclose and its status isn’t changed within the predetermined time frame, the ticket will be closed automatically.](https://docs.mintsd.com/api/reader/assets/assets/images/image1125.png?v=641bd9b5cbcb2240ab908ba732be678b2229832643549b5f70a383685c2afbbc)

<a id="element-01a1452d-fd5f-7510-8e9c-7e4b05adc478"></a>

This means that reminders will be sent respectively after:
• 6 hours (first reminder)
• 12 hours (second reminder)
• 18 hours (third reminder)

<a id="element-01a1452d-fd61-7ed0-9c3f-bbd940a3a5cb"></a>

The notification configuration is described in the **Notifications** section [(click here to visit)](https://docs.mintsd.com/docs/mint-service-desk/admin-portal-id11#element-01a1452e-0f2b-7b73-b28f-d6ac139d1af5).

