Tickets
Mint Service Desk 3.4.2 user manual.
Queues And Permissions
Queues group tickets by team, department, process or another division of work. Define the structure in “Queues”.
‘Queue structure’ opens by default. Use ‘Queues permissions’ to manage role access.
Related articles
Queue structure
Queues and subqueues
Click at the bottom of the view to add a queue below the existing entries.
Now, you only need to type the right name for this queue and either hit ‘enter’ on your keyboard or click on the button.
You can now add subqueues or configure the queue’s settings.
The first one is that you can add a sub-queue by clicking on the button and adding a sub-queue in the same way as you did it with the main queue.
Subqueues are hidden by default. Click to expand the queue and show them.
If you want to change the name of any queue, just click the button, change the name, and hit ‘Enter’ or click the button.
To delete a queue, click on the button, and in the new window click ‘Yes’.
Remember that you can always change the position of each queue and sub-queue in the structure. To do that just click the button next to the position you want to move. Now, while holding the Left Mouse Button just drag and drop this position to the plane you want it to be. Releasing the Left Mouse button will put this position in the newly chosen place.
Parameters and automatic replies
To assign parameters to queue, click the button. In the new window select one of the parameters available from the list and click on the button.
To create new parameters click on , fill in the required fields (Parameters name, Calendar, Response time, Resolution time) and any other if you want, then click on the button.
For each queue and sub-queue, you can configure ‘auto-responses’. Those are the automated messages that will be sent by the system in the Ticket Details communication section.
To do that, click the button. In the new window select one of the auto-responses available from the list and click on the button.
The detailed information on how to create custom auto responses will be described later in this guide, in the Tickets > Templates section.
Default assignee and signature
To configure the default agent assigned to the queue click the button.
Clicking on the drop-down list will display a list of agents with permissions to the selected queue (see Queue permissions in this section). You can select the default agent and decide when this agent will be assigned. To do that you only need to check one (or both) of available options: ‘Created new ticket’ and ‘Queue changed’. For ‘Queue changed’ the default agent will only be assigned if no agent is assigned to the ticket.
To configure the default signature, press the button. After pressing this button, a modal will be displayed with the signature selection.
In the ‘Preview’ field, the admin can select a signature of interest and preview what the selection will look like. (Signature creation is found later in the documentation under ‘Signatures’) When the admin has decided which signatures he wants to assign to a queue he selects them in the ‘Queue signatures’ field.
Counter and description
To configure the ticket counter, press the button. After pressing this button, a dropdown menu will be displayed with the ticket number selection. (Ticket number creation is found later in the documentation under ‘Ticket number counter’) After selecting an interesting counter, confirm the action by pressing the button.
Click to edit the queue description.
In ‘Value’ field enter the description text and click the button to apply changes.
Queue permissions
Use Queue permissions to control access to tickets in each queue and subqueue.
If you want to change rights, first you need to select one position from the list of available General types of roles. They can be e.g. ‘Agent Roles’ (if you have more than one created in the Agent Roles section) or ‘Company Roles’ (located in Companies > Company users section, separately for each company in ‘Role management’ > Company users tab.
After you do that, from the second list you need to select a particular type of Role for which you want to change the right.
The screen below shows the situation when we’ve decided to select ‘Agent roles’ and then one particular role: ‘Service Desk Agent’, which means that we will be able to change the rights for this particular role.
Now we can change the rights by selecting some check-boxes located on the right side of each queue.
Available permissions:
- Read – allows the user only to view the content of the Tickets on a queue
- Update – allows the user to make changes in the content of a Ticket on a queue. For example, Agent will be allowed to answer the client (to create a message in the communication section, change the ticket parameters).
- Create – allows the user to create tickets. The user can have Create but not Update and Read rights.
Selecting ‘Read’ does not select ‘Update’.
Selecting ‘Update’ also selects ‘Read’, allowing the user to view and change ticket content.
Once you finish making the changes, you need to click button, otherwise, when you try to leave this part of the system it will inform you that you have some unsaved changes.
In this section, you can configure the whole structure for Tickets. Step by step you can create, edit or delete: ‘Ticket types’, ‘Groups’ (of attributes), as well as single ‘Attributes’ along with their values. You will also set custom Statuses for your Ticket Types and unique Ticket number pattern.
Types
Define ticket types and configure permissions to view or change them and their attributes.
Related articles
Ticket Types
Ticket Types opens by default in the ‘Types’ section.
At the bottom of this view, you will find one button . It is used for creating and adding a new ticket type to the structure. Once you click on this button a new section will appear
Here you can type the right name for this ticket type and also select a custom color. See ‘Tickets – Custom fields’ in the Admin section to learn more about setting custom colours. You can also enable the ‘Resolution note’ option and select attributes that will be required to close tickets of this type. These options are described below.
If you want to change the name of any already existing ticket type, just click the button. In order to delete a ticket type, click on the button, and in the new window click ‘Yes’.
Resolution note
This option is available for each ticket type. When enabled, a modal dialog is displayed in ticket details whenever an agent changes the ticket status to Pending Autoclose or Closed.
The agent is required to fill in a resolution note explaining the reason for closure. The modal appears every time the ticket transitions to one of the statuses mentioned above. All resolution notes are recorded in the ticket history, and if the ticket is closed by a mechanism other than a direct agent action (e.g., an automatic process or a bulk status update), the note content is automatically set to: “Ticket closed automatically.”
Attributes required to close a ticket
Select the custom fields that must be completed before a ticket of this type can move to Closed.
Ticket Types Permissions
Use the second tab to set viewing and editing permissions separately for each ticket type.
Selecting a role
If you want to change rights, first you need to select one position from the list of available General types of roles.
They can be e.g. ‘Agent Roles’ (if you have more than one created in Admin > Agents > Roles section) or ‘Company Roles’ (located in Admin > Companies > Company Manager section.
After you do that, from the second list you need to select a particular type of Role for which you want to change the rights.
The screen below shows the situation when we’ve decided to select ‘Agent roles’ and then one particular role: ‘Service Desk Agent’, which means that we will be able to change the rights for this particular role.
Read and update permissions
Now we can change the rights by selecting some check-boxes located on the right side of each Ticket type.
There are two types of rights in the Mint Service Desk:
- Read – allows the user only to view the content of the Tickets
- Update – allows the user to make changes in the content of a Ticket. For example, Agent will be allowed to answer the client (to create a message in the communication section)
Selecting ‘Read’ does not select ‘Update’.
Selecting ‘Update’ also selects ‘Read’, allowing the user to view and change ticket content.
Once you finish making the changes, you need to click button, otherwise, when you try to leave this part of the system it will inform you that you have some unsaved changes.
Statuses
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).
Priorities
Create and manage priorities used in tickets and SLA rules.
Editing and creating priorities
If you want to change the name of the priority press the button. If your priority needs a description, you can add one by pressing the button. By pressing the button, you can assign the appropriate priority to the ticket type.
At the bottom of this view, you will find one button . It is used for creating and adding a new priority to the structure. Once you click on this button a new position will appear right below the last one already existing.
Now, you only need to type the right name for this queue. If you want to delete the name of the parameter you’re creating, click on the button.
Deleting, saving and ordering
To delete any of the positions use the button on the right side.
If you want to save your changes, make sure you are done with everything and use the button located in the bottom right corner of the view.
Changing the order the priorities are displayed is done in the same way as it was in the Queue section. Just use the button and move (drag & drop) the desired priority to the new place.
Ticket Number Format
Define the pattern used for ticket numbers.
Configure these parts of the ticket number:
- Name: This is where the admin enters the name of the ticket number format
- Count from: This field shows at which number the countdown will start, which is configured in the Ticket number counter tab
- Counter name: In this field, the admin selects one of the options created in Ticket number counter tab. A preview of the selected option can be found in Count from
- Prefix: a unique identifier for your company, for example for Mint it can be MT or MINT
- Date format: means date when the ticket was created, for example in year/month/format
- Tickets counter size: means how long the ticket counter should be. Please take notice that this number will be incrementing from 1 to xxx (the newest ticket) and it will not be reset each day. When you notice that the pull of available numbers is close to ending you can change it simply by changing the value of the Ticket counter size.
In addition to these three fields, you can add two more by selecting them from the list and then clicking button. Additional fields:
- Pin: In this field you select how long you want the pin to be. The possible length starts at 4 and ends at 10. These numbers are a random number.
- Separator: Here you can add a separator consisting of three values. There can be special characters like ‘/’, ‘-’, ‘|’ etc. You can add up to 6 separators to your configuration.
When you make too many changes and want to go back to the default settings just press the button.
The preview updates as you change the configuration.
Ticket Number Counter
The list shows all ticket number counters. Click to add one.
Two fields must be completed on this view:
- Name: This is where the admin enters the name of the ticket number format
- Count from: In this field, the admin determines at what number the request number will start counting down.
To complete the counter configuration, press the button.
Custom Fields
Related articles
Tickets Structure
Define ticket types, attribute groups and individual fields.
By default, the content of each Ticket Type is hidden and you only see the Ticket type name.
If you want to see the full content of a Ticket Type you need to click the button, located on the left side of the ticket type name.
Ticket types
You can create different ticket types like “Question” or “Complaint”, ‘1st level of support’ and also types for ITSM processes like: “Service Request”, “Incident”, “Problem” and “RFC” (Request For Change).
To add a new Ticket type just click on the empty field ‘Add ticket name’, type the desired name, and hit ‘Enter’ on your keyboard.
You can also look for a specific Ticket type by using the search field. Just type the name of the ticket Type you’re looking for and hit ‘enter’ on your keyboard.
To select a service, press the button. Then the whole list of services will be displayed, just select one of them.
To expand services on a ticket type press the checkmark next to ‘Expand Services lists’.
Effect before selection:
Effect after selection:
You can now restrict the field for the service of your choice by clicking on the button and selecting the appropriate service.
If you want to rename already existing ticket Type just click on its name, make some changes and click Enter.
If you want to remove it just click on a trashcan icon located on the right side. In the new window, you will be asked to confirm the action.
Click ‘Yes’ and the Ticket Type will be removed. Remember that deleting a ticket type means also deleting all custom Groups of attributes and single attributes that you have added to this Ticket type.
For each ticket type, 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 ticket type that needs a colour.
Groups
Creating and editing groups works almost the same as it is for Ticket types. In order to create a new group click on an empty field ‘Add group’ and type the desired name.
Now click enter on your keyboard. Try to save the changes by clicking on the right side of the screen. You will see information saying “Group must have at least one attribute”. Before you’ll be able to save a group you need to create at least one attribute.
To change the name of the group just click on it, type a new one, and accept the change by clicking enter.
To remove the group use the trashcan icon on the right side. Please notice that along with a group you will delete attributes that are inside this group.
Fields
Attributes store detailed ticket information. Each group must contain at least one attribute before it can be saved.
Adding and modifying attribute name as well as removing the whole attribute works the same way as for ticket types and groups.
However, after typing and accepting a name for the attribute you will have to choose attribute type, decide if you want to be able to search by this attribute in the list of tickets (‘Search filter’ check-box) or be able to select more than one value of the attribute (‘Multichoice’ check-box).
Select a type from the ‘Attribute type’ list.
Related articles
Pool
A Pool field contains a repeatable group of attributes.
For example: if you want to be able to add additional information (Place of the incident and incident description) about more than one incident, you can add a new attribute, rename it to ‘Description’ and mark ‘MultiChoice’, then select ‘Pool’ from the list of available types.
Now add two attributes, name them ‘Place of the incident” and ‘Impact level’ and as a type choose ‘Geolocalization’ and ‘Text area’.
Agents and Clients can then add several incident entries using these attributes.
To add another (second/third etc.) incident just click the button and a new empty page will be opened allowing you to type those attributes once again but this time for the second incident. You can also delete any of them with the button.
If you want to move between those ‘incidents’ use the navigation options .
Integer
An Integer field accepts whole numbers, such as 1, 6 and 77. It does not accept fractional values such as 1.2, 6.5 or 7.6.
Date
A Date field displays its value as “dd.mm.yyyy hh.mm”. To hide hours and minutes, press and select “No Time”.
Real Number
A Real Number field accepts fractional values, such as 1.44 or 23.95.
If you want your number to have more numbers after the decimal point, for example, 5, then press the button and enter the number you want in the step field.
Text
A Text field displays a single line. To set the maximum number of characters, press and enter a value between 1 and 150.
Relation
Use Relation to link an attribute to a ticket type or asset category.
If you add a ‘Relation’ type attribute while creating the structure for Ticket Types (Admin > Tickets > Custom fields > Tickets structure) you will have to select one from already existing Ticket Types.
If, on the other hand, you add a ‘Relation’ type attribute while creating the structure for Assets categories (Admin > Assets > Assets definition > Assets structure) you will have to select one from already existing Assets categories.
Also, while doing that, you can select one of two available types of relations:
- One to many
- Many to many
Date Scope
A Date Scope field stores “Date from” and “Date to”. Select each date from the calendar.
Num Scope
Use Num Scope to select a value from a defined numeric range.
You won’t be able to save any changes until you specify all of the information: minimum and maximum value, as well as a ‘Step’. To do that click the button. Now, in the new window define those values and click .
The Agent or Client selects a value by moving the slider left or right.
Geolocalization
A Geolocalization field stores an address, longitude and latitude. The Agent or Client enters the place name in ‘Address’ and the coordinates in the following fields.
Example: a location in Los Angeles.
Click to open the location in Google Maps.
Text Area
A Text Area field accepts multiline text without a character limit.
Drag the bottom-right corner down to enlarge the field.
Attachment
Use the Attachment field to attach files. The default extensions are pdf, doc, docx, odt, rtf, txt and jpg. Press to add more extensions.
Radio
A Radio field offers true and false choices.
Only one option can be selected at a time.
Checkbox
A Checkbox field is unchecked by default. Press to make it checked by default.
Label
Use a Label field to separate custom fields.
If you need a different font size then press the button. You can choose from these sizes: 12, 14, 16, 18, 20, 24.
Additionally, you can enter text in the Content field. This text can be formatted to a basic extent, just as when creating a ticket.
After saving and assigning permissions to the field, the entered text will appear in the field in the ticket details
Hypertext
Enter a URL, path or other text to display it as a hyperlink.
Enter the text in the field:
The saved value appears as a link:
Click the link to open its target page, if one exists.
Existing
An Existing field inherits the properties and value of another custom field. The source attribute must have “Shared” selected.
The following example reuses the attribute shown above in a field of type “Existing”.
Create an attribute, for example named “Existing”, and choose the Existing type. The “Pattern…” field appears.
Click on it and you will see the list of available attributes (with “Shared” checkbox selected) that you can inherit
Select the source attribute and save. The new field inherits its type and values. In this example, it has the Dictionary type and uses “Computer types”. When an Agent or Customer changes either field in ticket details and saves, the other field receives the same change.
You can choose any other attribute types like “text”, “date” etc.
Countdown
Countdown field displays in the ticket details how much time remains between two dates. These can be values from “Date” type field or system values (such as Ticket Creation Date).
Configuring the date range
To configure this field, add it to the chosen ticket type and click the button. The following modal appears:
- Date from - Here we can select: “Now”, “Creation Date”, “Modification Date” or assign a value from a custom field of type “Date”
- Date to - Here we can select: “Creation Date”, “Modification Date” or assign a value from a custom field of type “Date”
- Count below zero - Check this box if you want the field to also show negative values, e.g. when the end time has already passed
- Display absolute value - Check this box if you want the displayed values to be non-negative
Example: time remaining until a deadline
For example, configure each ticket to show the time remaining until a deadline:
Create a custom field of type Date.
Add a Countdown field.
click , then assign “NOW” in the “Date from” and a custom field Date type in the “Date to” field.
Finally, we save the entire configuration.
Next, we grant the agent permissions for the ticket type and the created fields. The agent then creates a ticket, filling in the “Date” field with a chosen future date.
After creating the ticket, the Countdown field displays the time remaining until the selected date.
This field can also be displayed on the dashboard. To do this, an agent can add it as an additional column, or an administrator can set this column a default in the Searchable Columns under Settings -> General -> Tickets -> Ticket search default settings.
Subscribed Receiver
A Subscribed Receiver field contains the subscriber’s Language and Email address.
Select the notification language and enter the email address that should receive notifications.
Remember that for the field to work you must add the ticket.subscribed.reciever field to the selected notification in the Receivers field.
Link Button
Link Button is a configurable button that an administrator can make available to system users. When clicked, the button performs an action defined in its configuration.
The button can simplify everyday tasks, such as opening a map, accessing another system, retrieving ticket information, or sending data to an external application. This allows users to perform specific actions without manually searching for addresses or copying data.
Link Button supports two action types: Link and Request. These settings are available after pressing the button.
Link button sections:
1. Purpose
Action types
Link
The Link action opens specified web addresses or launches supported external applications.
Example use cases:
- opening a map showing a location;
- navigating to a website or a tool used at work;
- opening an application such as TeamViewer or AnyDesk.
The administrator specifies the address to open and chooses whether it should open in the same browser window or in a new tab.
Request
The Request action sends requests to other systems, for example, to retrieve information or transfer data. It can be used to communicate with an API, an interface that allows applications to exchange data.
Example use cases:
- retrieving the current status of a ticket;
- sending ticket data to another system;
- updating selected information in an external application;
- displaying the result of an operation.
In this mode, the administrator can specify the request method, destination address, and data sent to the external system.
Using system data
In Request mode, snippets can be used to reference data available in the system. This allows the button to send information related to a specific ticket, user, asset, or contract.
Snippets can be added using the snippet builder, opened by clicking the scissors icon. Instead of entering the snippet syntax manually, the administrator selects a category and a field from which to retrieve a value. The system automatically inserts the appropriate expression.
Available categories include:
- system data;
- user data;
- ticket data;
- asset data;
- contract data.
Categories may also contain custom fields created for a specific system configuration.
For example, a button can send a ticket ID or the value of one of its fields to an external system. Values are retrieved from the relevant system data, allowing the same button configuration to be used for different records.
Displaying responses
In Request mode, the Wait for response option can be enabled to configure how a response from an external system is displayed.
When this option is enabled, the Response modal HTML template field becomes available. It allows the administrator to define the appearance of the response.
The template uses HTML and can also use AngularJS. The response is
available through the {{response}} variable.
This allows the administrator to present the result in a clear and readable format, for example, in a window with a heading and formatted content. The template can be adapted to the type of data returned by the external system.
Example use cases
Link Button can simplify many everyday tasks, for example:
- Opening a map — a Link button opens a map address in a new browser tab.
- Retrieving ticket status — a Request button sends a GET request to an external API.
- Sending ticket data — a Request button sends data to another system, for example, using the POST method.
- Updating information — a Request button sends data required to update a record in an external system, for example, using the PATCH method.
- Sending data automatically — snippets allow the request to include a ticket ID or the value of a custom field.
- Displaying operation results — the Wait for response option and the Response modal HTML template allow the user to view the response received from an external system.
The button’s behavior depends on its configuration and the capabilities of the system it communicates with.
2. Configuration
The button is configured in the administration panel after pressing the button. Under Action type, select the Link or Request tab, depending on what the button should do.
After selecting the appropriate tab, complete the required fields and adjust the remaining settings as needed.
2.1. Link configuration
The Link tab allows you to configure a button that opens a specified address. Below are the options you can or should select for proper configuration.
Show warning before opening the link
This option displays a warning before opening the link.
Select this option if users should receive a warning before navigating to the specified address.
Button
This section allows you to specify the text displayed on the button.
Button text
Here you can enter the button label which will be visible for the user. This field is required. For good responsiveness please use short, clear labels that indicate what will happen when the button is clicked.
Link settings
This section allows you to configure the link address and how it is opened.
Link address
Enter the address that will be opened when the button is clicked. This field is required.
The Allowed formats information below the field provides examples of supported address formats:
google.comhttps://google.comhttp://google.comwww.google.comTeamViewerAnyDesk
The field can be used to open websites and addresses associated with external applications. Launching an external application depends on whether it is installed and correctly configured on the user’s system.
For websites, HTTPS addresses are recommended.
Where to open the link
Select how the address should be opened.
Available options:
- In the same window — opens the address in the current browser window.
- In a new tab — opens the address in a new browser tab.
Saving the configuration
After completing the required fields, you can save the button configuration.
- Save — saves the configuration.
- Cancel — cancels editing.
Before saving, check that the Button text and Link address fields have been completed.
2.2. Request configuration
The Request tab allows you to configure a button that sends a request to a specified address. This can be used to communicate with other systems, for example, to retrieve information, send data, or perform an operation using ticket data.
In this tab, you can specify the request method, where the request is executed, the destination address, and additional options for handling the request and its response.
Show warning before executing the request
This option displays a warning before the request is sent.
Select this option if users should receive a warning before an operation is performed. This can be useful when a request sends data to another system or changes existing data.
Button
This section allows you to specify the text displayed on the button.
Button text
Here you can enter the button label which will be visible for the user. This field is required. For good responsiveness please use short, clear labels that indicate what will happen when the button
Request settings
This section allows you to specify how the request is sent and where it is sent.
Method
Select the HTTP method that defines the type of operation to perform.
Available methods:
- GET — retrieves information from the target system.
- POST — sends data to the target system, for example, to create a new record or initiate an operation.
- PUT — sends data to create or replace a resource, depending on how the target system works.
- PATCH — sends data to update selected information.
- DELETE — sends a request to delete a resource in the target system.
Choose a method that matches the requirements of the system receiving the request.
Where to execute the request
Select where the request should be executed.
Available options:
- Frontend — the request is executed in the user’s browser.
- Backend — the request is executed on the server side.
The appropriate option depends on the integration method and the requirements of the operation.
Request address
Enter the address to which the request will be sent. This field is required.
Example address:
https://api.example.com/resource/123
The address should point to an API endpoint or another service that supports the selected request method.
Below the field, a button with a scissors icon opens the snippet builder. It allows you to insert values from system data, such as a ticket ID or a custom field value.
This allows the address to be adapted to the record for which the user clicks the button.
JSON body
This field specifies the request body in JSON format. It is available for the POST, PUT, and PATCH methods.
The JSON body can contain data sent to the target system. Snippets can also be used to populate the request body with values from the system.
For example, you can send a ticket ID and its status to an external system.
The JSON body field is not displayed for the GET and DELETE methods.
Additional options
Trust all certificates
This option relates to the verification of certificates used when connecting to the target system.
Use this option with caution. In production environments, it is recommended to leave it disabled unless there is a specific reason to change how certificates are verified.
Wait for response
Select this option if the button should wait for a response from the target system and make it available for display to the user.
When this option is enabled, the Response modal HTML template field becomes available, allowing you to define how the response is displayed.
Response modal HTML template
This field appears when Wait for response is enabled. It allows you to create an HTML template that defines how the response from the target system is presented.
The template can use AngularJS, and the response is available through
the {{response}} variable.
Example of a simple template:
<div>
<h3>Operation result</h3>
<pre>{{response}}</pre>
</div>
In this example, the response is displayed under the heading
“Operation result”. The pre element preserves the formatting of
the displayed text.
The template can be adapted to the type of data returned by the API.
Saving the configuration
After completing the required fields, you can save the button configuration.
- Save — saves the configuration.
- Cancel — cancels editing without saving the changes.
Before saving, check that the Button text and Request address fields have been completed. Adjust the remaining settings to meet the requirements of the operation.
3. Configuration examples
3.1. Opening a map — Link
To create a button that opens a map, configure it as follows:
| Field | Value |
|---|---|
| Action type | Link |
| Button text | Open map |
| Link address | Address of the selected map |
| Where to open the link | In a new tab |
You can enable Show warning before opening the link if a warning should be displayed before opening the address.
After completing the fields, click Save to save the configuration.
When the user clicks the Open map button, the configured address opens in a new browser tab.
After clicking, if Show warning before opening the link was checked, the warning modal will appear
If the address needs to be generated using ticket or asset data, check whether the Link address field supports dynamic value substitution mechanisms such as snippets.
3.2. Retrieving ticket name — Request
The administrator wants to provide users with a button that retrieves a ticket name from the specified ticket that user is checking at the moment. When the button is clicked, the system sends a request to an API and then displays the response.
Example configuration:
| Field | Value |
|---|---|
| Action type | Request |
| Button text | Get ticket name |
| Method | GET |
| Where to execute the request | Frontend |
| Request address | API address containing the ticket ID |
| Trust all certificates | Disabled |
| Wait for response | Enabled |
In the Request address field, enter the appropriate API endpoint.
If the address needs to include the current ticket ID, you can insert
it using the snippet builder, available by clicking the scissors icon.
In this particular example, if a user is viewing a specific ticket, the
{{TicketId}} snippet will be replaced with the ID of the ticket the user is currently viewing
For example, the address could look like this:
https://mintsd.opgksoftware.com/api/tickets/{{TicketId}}
To display the response received from the target system, enable Wait for response. Then use the Response modal HTML template field to create a template for displaying the returned data - in our example we want only the name parameter.
Example template:
<div>
<strong>Ticket name:</strong> {{response.data.name}}
</div>
You can easily manage the response view by entering HTML code along with styling.
Example configuration below:
After saving the configuration, users can click the Get ticket status button.
The system sends a GET request to the specified address, and the response is made available in the configured window.
The actual result depends on the data returned by the API and the configuration of the target system.
Regex
Select a predefined regular expression. Values entered in this field must match it.
For example, if you choose ‘email’ Regex, a user (Client or agent) will have to type the correct email address.
Dictionary
A Dictionary field lets users select from a predefined list. Manage the list in the ‘Dictionaries’ section.
In the following example, we have chosen a custom-made ‘Software types’ Dictionary.
Now the user (Agent, Client) has to choose the desired position from the list. He is able to do this either while creating a Ticket in ‘Create new ticket’ view (if he chooses a ticket type that has a ‘Dictionary’ type attribute) or (if he has the appropriate rights given by the admin) in ‘Ticket Details’ view. Also, you can do this as well when creating (or editing) an asset if the Dictionary type attribute is attached to the selected Asset category.
If you want to allow the agents to add new dictionary values while creating or editing a ticket, click the button, and then check the checkbox Adding dictionary values.
The agent role also needs “Expanding dictionary values” enabled in Users -> Roles.
From now on, the agent has the ability to add new values to the selected dictionary.
Relation Asset
This field is used to determine the relation to the asset. After selecting this field as in the case of a regular relation, it is possible to choose between two:
- One to many
- Many to many
Then, in the Pattern field, you select what you want the relation to be for.
Relation Contract
Use this field to relate contracts. Choose a relation type:
- One to many
- Many to many
Then, in the Pattern field, you select what you want the relation to be for.
Relation Company
Use this field to relate companies. Choose a relation type:
- One to many
- Many to many
Then, in the Pattern field, you select what you want the relation to be for.
Relation User
Use this field to relate users. Choose a relation type:
- One to many
- Many to many
Then, in the Pattern field, you select what you want the relation to be for.
Ticket Permissions
Use the second tab to set viewing and editing permissions separately for each ticket type.
Selecting a role
If you want to change rights, first you need to select one position from the list of available General types of roles.
They can be e.g., ‘Agent Roles’ (if you have more than one created in Admin > Agents > Roles section) or ‘Company Roles’ (located in Admin > Companies > Company Manager section.
After you do that, from the second list you need to select a particular type of Role for which you want to change the rights.
The screen below shows the situation when we’ve decided to select ‘Agent roles’ and then one particular role: ‘Service Desk Agent’, which means that we will be able to change the rights for this particular role.
Read and update permissions
Now we can change the rights by selecting some check-boxes located on the right side of each Ticket type. Please notice that you can also select/remove right for each Attribute as well.
There are two types of rights in the Mint Service Desk:
- Read – allows the user only to view the content of the Tickets
- Update – allows the user to make changes in the content of a Ticket. For example, Agent will be allowed to answer the client (to create a message in the communication section)
Selecting ‘Read’ does not select ‘Update’.
Selecting ‘Update’ also selects ‘Read’, allowing the user to view and change ticket content.
Once you finish making the changes, you need to click button, otherwise, when you try to leave this part of the system it will inform you that you have some unsaved changes.
Conditional Attributes
Configure rules that show or hide ticket fields according to other field values.
Creating a rule
To add a new conditional attribute, you must press button. When the button is pressed, the user will be taken to the conditional attribute configuration form.
-
Order - This field specifies the order in which actions should be performed. The conditional attribute with the smaller number will be executed first. This field takes integer values.
-
Name - This is where the user enters what their configuration should be called.
-
Description - Here the user can enter a description of the configuration.
-
Stop after match - When the user checks this box then if the conditional attribute is satisfied then the system will stop there and will not search further.
-
Category - This is where you select your ticket type.
-
Dependent - Here you select a dependent field that will appear or disappear depending on the choice made in ‘Action Type’
-
Action Type - This is where you specify what should happen after matching. There are two options to choose from ‘Visible’ and ‘Hidden’. If the user selects ‘Visible’ then initially the field selected in ‘Dependent’ will be hidden until the conditions specified below are met. The ‘Hidden’ option works exactly the opposite.
-
Matching conditions - At this point you have a choice of two options ‘And’ and ‘Or’. If you choose the ‘And’ option, all conditions must be met. If you choose the ‘Or’ option, only one condition needs to be met.
-
Dependees - In this field, you choose which field to take into account when appearing or hiding the field selected in ‘Dependent’.
-
Logic operator - In this field, you have four options to choose from: ‘Equals’, ‘NotEquals’, ‘Contains’ and ‘NotContains’.
- Selecting the ‘Equals’ field means that it must equal ‘Value’.
- Selecting the ‘NotEquals’ field means that it must be different from ‘Value’.
- Selecting the ‘Contains’ field means it must contain ‘Value’.
- Selecting the ‘NotContains’ field means it must not contain ‘Value’.
-
Value - Here you enter the value that must be met.
-
Stop after match - If this box is checked and there is more than one condition the system will not search further once one condition is met.
Example
In this setting, initially the ‘Int’ field is hidden but will appear if the ‘Description’ field is equal to ‘Problem’.
If you want to add another condition, you can press button.
To complete the configuration process, press button.
Exporting settings
At the top of ‘Custom Fields’ tab you have an option to export settings.
Export the settings as a csv or xlsx file.
Use the export to check for accidental deletions or compare the ticket structure before and after a Mint or database update.
You can easily export settings by clicking button to export basic structure, or by clicking button to export Ticket Type Permissions
Templates
View, create, edit and delete templates assembled from the components defined in ‘Components’.
Use templates for system emails, automatic ticket replies and predefined messages that agents send manually.
Create templates for the answers and replies your team uses regularly.
Mint Service Desk also includes predefined templates.
Creating a template
If you want to create a new one, just click on the button and you will be moved to the “Create template’ form. Always remember that before moving to create a new template you need to create the needed components (in ‘Components’ section).
In the “Create Template” view you need to fill the “Name” (required) and add some “Description” if you like.
Components and template type
Once you do that you need to select components from which your Template will be built. You can select four components: ‘Subject’, ‘Header’, ‘Body’, and ‘Footer’. ‘Body’ is required, the others are optional.
For an email template, such as an account confirmation, include ‘Subject’ as well as ‘Body’. Add ‘Header’ and ‘Footer’ if needed.
After selecting the components, you need to choose one of two available ‘Template types’. Those are ‘System’ and ‘Custom Response’.
Select “System” for templates which the system will send automatically based on some activity.
If, on the other hand, you want to have a predefined template that your agents will use to manually answer your customers choose the “Custom Response” type.
Saving and editing
Once you finish save your changes by clicking button.
After creating a new template, you can always either change anything in it ( button) or even delete it from the system ( button). Deleting the template does not delete any components which were used in that template.
Components
Create reusable components for message templates, such as the ‘Thank you’ message sent after a ticket is created.
Define the components here, then combine them into templates in the next section.
MINT Service Desk has four types of components: “Subject”, “Header”, “Body” and “Footer”.
To create a new component, you need to click on the “Add new value” button.
Now, in the ‘Create template component’ view you need to name your new component (‘Component name’) and choose a type (“Subject”, “Header”, “Body” or “Footer”).
Write and format the component in ‘Content’ using the rich text editor. Add dynamic fields to insert system data when the template is used.
To do so, click the scissor button located right below the ‘Content’ section and from the dropdown menu select and add the dynamic fields you need.
Once you finish just click the button.
Remember that after creating a new component you can always either change anything inside it () or even delete it from the system ().
Give components descriptive names so you can find the correct ones when building and maintaining templates.
Document Templates
Upload document templates for agents to use in ‘Ticket Details’.
The default view shows the list of already uploaded Document templates.
Creating a document template
To add a new Document template simply click the button.
Now, in the ‘Create document template’ put some name (‘Name’) for your template then select the Queues. Depending on your choice your template will be available to use only for tickets created in or moved to those Queues. If you want, you can also add some description (‘Description’).
Now you need to add an external file which contains the prepared Document template. MINT Service Desk only supports one file format: .docx.
To create such a Document template, you need to use external software e.g., Microsoft Word or any other which can save the file in .docx format.
System data placeholders
Use placeholders to insert system data. Enter {{Company}} in the template, for example. When an agent uses the template, {{Company}} is replaced with the client’s company name.
For the purpose of creating a Document template, you can add the fields below.
| Placeholder | Location/used in | Description |
|---|---|---|
| {{PrintDate}} | Ticket Details | Date of creating a ticket .pdf preview. |
| {{TicketName}} | Ticket Details > Details | Ticket name/title. |
| {{TicketNumber}} | Ticket Details > Details | Ticket number. |
| {{Customer}} | Ticket Details > Details | Ticket owner’s name – a person who created the ticket. |
| {{Company}} | Ticket Details > Details | Company name of the ticket owner. |
| {{Status}} | Ticket Details > Details | Ticket current status. |
| {{Assignee}} | Ticket Details > Details | A person (Agent) assigned to the ticket. |
| {{Queue}} | Ticket Details > Details | Ticket Queue name. |
| {{TicketType}} | Ticket Details > Details | Ticket type name. |
| {{Priority}} | Ticket Details > Details | Ticket priority. |
| {{Service}} | Ticket Details > Details | Name of the chosen Service for the ticket. |
| {{Age}} | Ticket Details > Details | Ticket age (in hours or days). |
| {{TicketCreationDate}} | Agent/Client Dashboard | The exact date when the ticket was created. |
Custom field placeholders
To insert a custom field from Tickets or Users, use this syntax:
{{GroupName:AttributeName}}
Example:
For the “Desktop” and “Laptop” attributes, use {{Hardware:Desktop}} and {{Hardware:Laptop}}.
If Users and Tickets have the same group and attribute names, MINT uses the value from the ticket’s custom field.
Below you can see how a prepared template document should look like.
Placeholders are written in blue.
Uploading and saving
Now, when you have such a Document template ready you can upload it to the MINT Service Desk. In the ‘Files’ part click on the ‘Click to attach file’ field.
In your system’s file explorer find, select and add your custom-made Document template. Once you do that you will see a file miniature in the ‘Files’ part.
If you want to delete the file and add a new one you can do that by clicking the X button located at the top right corner of the file’s miniature the moment you move your mouse cursor over it.
Once you decide that everything is in order click button. After that, you will notice a new position on the list of available Document templates.
Now Agent can use it while communicating with a Client, inside the ‘Ticket details’ view. It was already described in the Agent > Ticket Details part of this guide.
Signatures
The list shows existing signatures. Click to open the form for a new signature.
Two fields must be completed at this point:
- Signature name - In this space, enter what you want the signature to be called.
- Content - Enter the content of the signature in this space.
Signature content supports custom fields and formatting such as bold and underline.
After completing the fields, press the button.
Configuration
Define settings that apply to selected queues or ticket types.
For example, configure closed tickets in a particular queue to reopen when a new article arrives.
After entering this tab, a list of all available configurations will be displayed.
Creating a configuration
To start the process of creating a new configuration, press the button.
The configuration is divided into two segments. In the first segment, complete these fields:
- Message element - Here you choose whether you want the configuration to apply to the Queue or Ticket Type.
- Operation type - Here you select the type of operation.
- Element value - Here you choose which value you want the configuration to apply to. The list depends on the selection in the Email element.
Combining conditions
Below this configuration, there are two options to choose from:
- All conditions are met - This option means that the configuration will work when ALL conditions are met.
- One of the conditions is met - This option means that the configuration will work when AT LEAST one condition is met.
There is a button in the lower right corner of this segment. Pressing it allows you to create another configuration condition.
This setting means that the configuration will work when the queue is “Q1” OR Ticket Type is “T1”.
Order and actions
The second section includes such fields:
- Order - Here you enter a number. This value indicates in what order the configurations will be executed. The configuration with the smaller number will execute first.
- Name - Here you enter the name that the configuration should carry.
- Reopen when closed - Checking this option will cause that when the ticket is closed and a new article falls in then the ticket will change its status to ReOpened.
- Reopen on pending close - Checking this option will cause that when the ticket is on Pending Autoclose and a new article drops in, the ticket will be reopened. When the time is up and the ticket is closed then the ticket will not reopen.
- Block closed ticket - Checking this option will block the ticket that has changed to the ‘Closed’ status.
- Block closed ticket delay - This option is active with Block closed ticket checked. This setting allows you to specify the time after which a ticket that has changed to the ‘Closed’ status will be blocked
- Stop after match - If this box is checked and there is more than one condition the system will not search further once one condition is met.
This is what a simple configuration looks like:
Strike Rules
Configure reminders that trigger as a Pending Autoclose period elapses. Set the total duration in Tickets → Statuses.
To add a new configuration, click the button. Then, in the Name field, enter the configuration name and click New Row.
A row will appear where you fill in the name of the item and the percentage of time after which the notification should trigger. If you need additional notifications as the Pending Autoclose status time elapses, press the New Row button again, and another row will appear for completion. You can always modify the saved configuration or even delete unnecessary rows with button.
After completing the fields, press . The configuration appears in the Strike rules list.
Assigning the configuration to the Pending Autoclose status is described in the Tickets → Statuses section (click here to visit), while the notification configuration is described in Notifications section (click here to visit).
Contact Group Categories
Create categories that agents can select in the Contact Groups section of their profiles.
When you enter the tab ‘Contact group categories’, the main configuration page appears.
To add a new category, click the button in the upper right corner of the screen. Then enter the name of the new category and click the button in the lower right corner.
After saving, the new category will appear on the list.
From that moment on, Agents can select the newly added category in the Contact Group section of their profile (CLICK HERE to proceed to Contact Group section in Agent profile).