Skip to content
Mint Service Desk Documentation centre

Custom fields

Mint Service Desk 3.4.2 user manual.

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 .

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.

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

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.

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

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.

Back to Link Button overview

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.com
  • https://google.com
  • http://google.com
  • www.google.com
  • TeamViewer
  • AnyDesk

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.

Back to Link Button overview

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.

Back to Link Button overview

3. Configuration examples

3.1. Opening a map — Link

To create a button that opens a map, configure it as follows:

FieldValue
Action typeLink
Button textOpen map
Link addressAddress of the selected map
Where to open the linkIn 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.

Back to Link Button overview

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:

FieldValue
Action typeRequest
Button textGet ticket name
MethodGET
Where to execute the requestFrontend
Request addressAPI address containing the ticket ID
Trust all certificatesDisabled
Wait for responseEnabled

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.

Back to Link Button overview

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.

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