Statuses
Mint Service Desk 3.4.2 user manual.
Configuration
An administrator can create statuses of type ‘Pending approval’ and assign a configuration prepared in the Approvals tab. For each status, choose where the ticket moves after approval and after rejection. You can name the status freely and create several Pending Approval statuses using the same or different configurations.
The general status fields are described in Ticket statuses. The procedure below explains the fields specific to approvals.
Creating an approval status
Open Tickets > Statuses and select the ticket type, such as Complaints.
The existing statuses for that ticket type appear.
Click Add New, enter the display name in Value, and select Pending Approval in Type. The name identifies the status in tickets; the type enables the approval settings.
Decision rule and outcome statuses
Selecting the Pending Approval type reveals the fields for the approval configuration and the two outcome statuses:
Select approval configuration: choose the decision rule prepared in the Approvals tab. This rule determines who decides and how the decisions are combined.
Select status after approve: choose the status assigned to the ticket when the configured approval conditions are met.
Select status after reject: choose the status assigned to the ticket when the configured rejection conditions are met.
Click Save after selecting the configuration and outcome statuses. The new status is then available in tickets.
Important: If you want to use new, custom statuses in the Select status after approve and Select status after reject fields during configuration, you must configure and save them before adding the Pending Approval status.
Example
To use custom statuses named Approved and Rejected with a Pending Approval status:
First create Approved and Rejected with the type Closed, then click Save.
Now create the Pending Approval status. The new statuses are available in the outcome lists.
Configuration Change
The administrator can change the saved configuration in the Select approval configuration field to another configuration. The exceptions are those configurations that include To Be Selected and Line Manager in the decision tree - such configurations will then be greyed out and not selectable.
If tickets already use this status, existing decisions carry over to the new configuration only when their decision-makers also participate in it.
Example
A ticket in Pending Approval requires decisions from Agent 1 and Agent 2. After Agent 2 decides, the administrator changes the configuration to require Agent 2 and Agent 3. Agent 2 does not need to decide again: their existing decision carries over. If the configuration changes several times, only decisions from the configuration immediately before the latest change are carried over.
Deleting Statuses
Deleting an approval outcome status clears the corresponding Select status after approve or Select status after reject field. Select a replacement before saving; otherwise, the system highlights the required field and prevents the save.
Example
The Pending Approval status uses Approve and Reject as its outcome statuses.
After Reject is deleted, saving highlights Select status after reject. Select a replacement status to continue.
Deleting the Pending Approval status
The administrator can delete any status of type Pending Approval. After deleting, all tickets on that status are moved to the status that has been set before in the Select status after reject field.