Event
Mint Service Desk 3.4.2 user manual.
General Settings
In General settings, enter the automation’s name and, optionally, a signature. Select ‘Is active’ to enable it immediately, or enable it later by editing the automation.
Events
In Events, select the type of item that triggers the automation:
- ticket
- article
After choosing a type, select its triggering event from the ‘events’ list. Ticket and article events differ.
ticket:
- Assignee changed
- New ticket
- Queue changed
- Status change
- Value changed
- Ticket type change
article:
- New article
- New comment
Filters
In Filters, choose which tickets or articles the automation applies to. Available filters depend on the event type.
For tickets:
- ticket.assignee - filters by the agents assigned to the ticket.
- ticket.company - filters by the company assigned to the ticket.
- ticket.customer - filters by customer.
- ticket.queue - filters by the queue in which the ticket is created.
- ticket.service - filters by the service in which the ticket is created.
- ticket.status - filters by the status in which the ticket is created.
- ticket.ticket_type - filters by ticket type in which the ticket is created.
- ticket.attribute_id - filters by the attribute created in custom fields.
- ticket.first_attribute_dictionary_value - filters by the attribute created in dictionary.
- ticket.second_attribute_dictionary_value - filters by the attribute created in dictionary.
- ticket.article_author - filters by article author.
For articles:
- ticket.assignee - filters by the agents assigned to the ticket.
- ticket.company - filters by the company assigned to the ticket.
- ticket.customer - filters by customer.
- ticket.queue - filters by the queue in which the ticket is created.
- ticket.service - filters by the service in which the ticket is created.
- ticket.status - filters by the status in which the ticket is created.
- ticket.ticket_type - filters by ticket type in which the ticket is created.
- ticket.attribute_id - filters by the custom field.
- ticket.first_attribute_dictionary_value - filters by dictionary value.
- ticket.article_author - filters by article author.
Actions
In Actions, choose what happens to a ticket or article when the automation’s event and filter conditions are met.
To start the configuration you need to press button. Then a dropdown menu will appear from which you can select the option you are interested in by pressing the button.
Available actions are described below.
CREATE TICKET
The Create Ticket action is available only when the selected Event type is Ticket. When the conditions defined in the Events and Filters sections are met, this action automatically creates a new ticket.
In the Subject and Description fields, we can use snippets (scissors icon), which are placeholders for values that will be filled in after the ticket is created.
Example: We want our ticket to have the title “Ticket created on:” followed by the creation date. To do this, fill in the title with “Ticket created on:” and then click on the scissors icon located below this field. Next, from the “Ticket” section, select the “Creation date” option. When creating a ticket, our title will take the form: “Ticket created on: {{TicketCreationDate}}”. After its creation, the snippet {{TicketCreationDate}} will be replaced with the actual ticket creation date.
You can use multiple types of snippets, including those related to custom fields.
After selecting Create Ticket, you can configure the newly created ticket in two ways:
- Manual Field Configuration
You can manually complete all fields available in the ticket creation form. All fields configured in this section will define the values of the newly created ticket.
- Inherit Values
The Inherit values section allows the new ticket to inherit selected values from the ticket that triggered the automation.
You can configure inheritance for the following fields:
- Subject
- Assignee
- Queue
- Service
- Contract
- Ticket type
- Company user
- Company
- Priority
- Pinned Assets
- Pinned Related Tickets
- Custom Fields
For custom fields, map a field in the triggering ticket type to a field in the new ticket type. Configure each mapping separately to transfer values between different ticket types.
Example
We want the system to automatically create a new ticket of type “Complaint Step 2” when a ticket of type “Complaint Step 1” is closed.
The newly created ticket should:
- Inherit the Company
- Inherit the Company User
- Inherit the Subject
- Inherit the Queue
- Copy the value from the custom text field “Text field from Step 1” (in the closed ticket) and map it to the custom text field “Text field from Step 2” in the newly created ticket
First we set Event type: Ticket and select Status change from Events field. Next in filters we choose status: Closed and Ticket type: Complaint Step 1.
Now select the Create ticket action from the Actions section and then select the following items from the “Inherit ticket field” field: Company, Company User, Subject, Queue, adding each field individually with the button.
Next select and add the Custom fields item. A new New row button will appear. Click it to add a new row with two drop-down lists. In the list on the left, select the text field from the Complaint Step 1 ticket type, and in the list on the right, select the field from the Complaint Step 2 ticket type.
Finally, in the ticket form, fill in Ticket type: Complaint Stage 2 and Description, and save the configuration with the Save button.
The configuration is ready to use. Log in to the Agent profile and close the ticket of the Complaint Stage 1 type.
A new ticket will be created in the system after ticket closing action, according to the automatic action configuration, and the inherited values will be shown.
TICKET PROPERTY CHANGE
The Ticket Property Change action allows you to automatically modify selected properties of a ticket that triggered the automation. If the conditions defined in the Events and Filters sections are met, the system will update the selected fields in the same ticket that initiated the action.
Within this action, you can configure automatic changes to the following ticket parameters:
- Company
- Company User
- Ticket Type
- Status
- Queue
- Assignee
- Priority
- Service
- Contract
Some fields appear only after you select a related field.
When configuring the action, the following fields are available first:
- Company
- Company User
- Ticket Type
- Queue
- Priority
The following fields become visible only after selecting a Ticket Type:
- Status
- Service
- Contract
This dependency exists because available statuses, services, and contracts may vary depending on the selected ticket type.
The Assignee field becomes visible only after selecting a Queue. This ensures that only agents assigned to the selected queue can be chosen as the assignee.
TICKET DYNAMIC FIELDS CHANGE
This option allows you to automatically change the custom fields in the selected Ticket Type.
TICKET PROPERTY CHANGE BY DYNAMIC FIELD VALUE
This option allows you to change ticket properties based on the value of a dynamic field.