> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/dineplan/backoffice/tickets/ticket-tags.md).

# Ticket Tags

### **Overview** <a href="#overview.2" id="overview.2"></a>

The Ticket Tags setting allows you to manage tags used for tickets. You can add new ticket tags, edit existing tags, delete tags, and change their display order. Each ticket tag can also be configured with general settings, sub tags, and mappings.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-76b3311a82c1d6f4c30832e45567693f2c44baff%2Fatt_22_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

### **Screen Elements** <a href="#screen-elements.2" id="screen-elements.2"></a>

#### **Ticket Tag List** <a href="#ticket-tag-list" id="ticket-tag-list"></a>

| **Screen Element** | **Description**                                     |
| ------------------ | --------------------------------------------------- |
| Ticket Tag List    | Displays the available ticket tags.                 |
| Search             | Allows you to search for a specific ticket tag.     |
| Add Ticket Tag     | Opens the screen to create a new ticket tag.        |
| Edit Ticket Tag    | Allows you to modify the selected ticket tag.       |
| Delete Ticket Tag  | Deletes the selected ticket tag after confirmation. |
| Sort Ticket Tags   | Allows you to change the order of the ticket tags.  |
| Close              | Closes the Ticket Tag screen.                       |

#### **General Settings** <a href="#general-settings" id="general-settings"></a>

| **Screen Element**         | **Description**                                                        |
| -------------------------- | ---------------------------------------------------------------------- |
| Ticket Tag Name            | Specifies the name of the ticket tag.                                  |
| DisplayName                | Specifies the display name for the ticket tag.                         |
| Selection Required         | Controls whether selecting the ticket tag is required.                 |
| Ask Before Creating Ticket | Controls whether the system asks for the tag before creating a ticket. |
| Free Tagging               | Allows free tagging when enabled.                                      |
| Save Free Tags             | Saves tags entered through free tagging when enabled.                  |
| Tagging Type               | Specifies the tagging type.                                            |
| Free Tag Maximum Length    | Specifies the maximum length allowed for a free tag.                   |
| When Tagged                | Specifies the button color displayed when the ticket is tagged.        |
| When Untagged              | Specifies the button color displayed when the ticket is not tagged.    |
| Save                       | Saves the ticket tag configuration.                                    |
| Close                      | Closes the ticket tag configuration screen.                            |

### **Working** <a href="#working.2" id="working.2"></a>

#### **Add a Ticket Tag** <a href="#add-a-ticket-tag" id="add-a-ticket-tag"></a>

1. Select "Add Ticket Tag" from the Ticket Tag List.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-7218d374d833822970f244e6c25aa6075fd62673%2Fatt_23_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

2. In General Settings, enter the Ticket Tag Name and DisplayName.
3. Configure the required options, such as "Selection Required", "Ask Before Creating Ticket", and "Free Tagging".
4. Select the required "Tagging Type" and configure "Free Tag Maximum Length", if applicable.
5. Configure the button colors for "When Tagged" and "When Untagged".

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-a15f69bd0568b9100100063ce9160af7bc15c956%2Fatt_24_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

6. Select "Sub Tags" to add and manage sub tags, if required.
7. Select "Add Tag".
8. Enter the sub tag name in the "New Tag" field.
9. Enter the "Alias Name", if required.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-bf89b7dfa6892c557c497a5a3e8bf2562af4ef45%2Fatt_25_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

10. Select "Mappings" to add mapping details, if required.
11. Select "Add".
12. Select the required values for "Terminal", "User Role", "Department", "Ticket Type", and "DefaultValue".

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-54e99efde48214af46b84be3b935c916d41724e9%2Fatt_26_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

13. Select "Save" to save the ticket tag.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-3fe7c5e74a654eacfdf2b29917c3f2a8a1c5bf2d%2Fatt_27_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Edit a Ticket Tag** <a href="#edit-a-ticket-tag" id="edit-a-ticket-tag"></a>

1. Select the required ticket tag from the Ticket Tag List.
2. Select "Edit Ticket Tag".

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-8c1ee48610cf8fcdb02f3c4d3e9a1689eeb2e397%2Fatt_28_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Modify the required configuration.
4. Select "Save" to apply the changes.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-3fe7c5e74a654eacfdf2b29917c3f2a8a1c5bf2d%2Fatt_27_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Delete a Ticket Tag** <a href="#delete-a-ticket-tag" id="delete-a-ticket-tag"></a>

1. Select the ticket tag you want to remove.
2. Select "Delete Ticket Tag".

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-1793b27d4d9d7ba3b8677096f8156662f05991f8%2Fatt_30_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

3. In the confirmation message, select "Yes" to delete the ticket tag.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-6f3022def0431df0661d6bb57d9068e007b493d1%2Fatt_31_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Sort Ticket Tags** <a href="#sort-ticket-tags" id="sort-ticket-tags"></a>

1. Select "Sort Ticket Tags" from the Ticket Tag List.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-559fa52aa9fa32654bb41030ceb1137c2e236fe7%2Fatt_32_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

2. Drag the accounts to arrange them in the required order.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-d5f831f240abd3501b9edda7cb1456dd7b948f0c%2Fatt_33_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Select "OK" to apply the changes.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-1b5c955f6cedd68343dd4e695d85369bf0684529%2Fatt_34_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

### **Use Case** <a href="#use-case.2" id="use-case.2"></a>

* Create ticket tags to categorize and organize tickets.
* Configure whether selecting a ticket tag is required when creating tickets.
* Allow users to enter tags manually using "Free Tagging".
* Create sub tags to provide additional tagging options.
* Configure aliases for sub tags using "Alias Name".
* Define mappings based on terminal, user role, department, and ticket type.
* Edit existing ticket tags when their configuration needs to be updated.
* Sort or delete ticket tags to maintain an organized tag list.

### **Notes** <a href="#notes.2" id="notes.2"></a>

* "Ticket Tag Name" must be provided before saving a ticket tag.
* Use "DisplayName" to define how the tag is displayed.
* "Selection Required" can be enabled when a ticket tag must be selected.
* "Free Tagging" allows users to enter tags manually when enabled.
* Configure "Free Tag Maximum Length" when a character limit is required for free tags.
* Sub tags can be added, deleted, and sorted within a ticket tag.
* Mappings can be configured using "Terminal", "User Role", "Department", and "Ticket Type".
* Deleting a ticket tag requires confirmation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rbsgo.com/dineplan/backoffice/tickets/ticket-tags.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
