# 2. Tickets

In the menu => **Select Additional** features (1) => **select Tickets** (2)

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/EjVBFcZsOpX6aPxoYQwt/image.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/yAxLv6cejRyokbozfCSa/image.png" alt=""><figcaption><p><em>Màn hình Tickets</em></p></figcaption></figure>

* **List of Tickets:**

\- Your open tickets: List containing tickets assigned directly to the employee who is logged into the system and only displays tickets in the open state

\- Undelivered tickets: List containing tickets that have not been assigned to any group or employee

\- All tickets: List containing all tickets in the app

\- Group list: includes tickets assigned to groups in the app. By default, only displays the list of groups that the logged-in employee belongs to (is a member of that group). Other groups' lists are hidden by default until the user later sets them to hide/show

\- Employee list: includes tickets assigned to other employees in the app. By default, it is not displayed until the user sets the list of a specific employee to hide/show then.

\- Each list has an index of the open tickets it contains

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/yQwJwu8U2Q1XkcWV98XB/image.png" alt=""><figcaption><p><em>Màn hình danh sách ticket</em></p></figcaption></figure>

* Arrange Tickets

\- Each interface has a ticket sorting feature.

\- By default, sort by creation date from the latest date.

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/V9a3p0PMIyCDHdcA4lFO/image.png" alt=""><figcaption></figcaption></figure>

When clicked, the ticket arrangement has a 2-zone structure

a. Area 1: Area for selecting information fields as criteria

\-  Ticket information group

&#x20;\+ Customer: text format

&#x20;\+ Appointment start schedule: date - time format

&#x20;\+ End appointment schedule: date - time format

&#x20;\+ Reception source: text format

&#x20;\+ Resolution department in charge: text format

&#x20;\+ Person in charge: text format

&#x20;\+ Pipeline: text format

&#x20;\+ Ticket ID: number form

&#x20;\+ Status: text format

&#x20;\+ Priority: text format&#x20;

\+ Acceptance form

\- Ticket activity group

&#x20;\+ Last operation: date - time format

&#x20;\+ Creation date: date - time format

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/mlAZuru3ET2qs7F72oT1/image.png" alt=""><figcaption></figcaption></figure>

b. Area 2: Select area to sort order Newest/Oldest

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/p7H30h9cwsmt3LaMv12e/image.png" alt=""><figcaption></figcaption></figure>

* **Filter by Pipeline**: Allows displaying tickets in a list by pipeline.

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/Lz2IGocIhpIO8gsVtabv/image.png" alt=""><figcaption></figcaption></figure>

\- Default “All pipeline”: displays all tickets in the list when in table and card view.

\- When switching to a specific pipeline, you will view it in Kanban mode. The “All pipelines” option cannot be selected in the Kaban interface.

* **Switch interface**:

\- Manage tickets being processed in the system

\- The ticket administration screen has 3 types:

\+ Card management interface

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/g1CPLmxI5ckcQ1yxJgWq/image.png" alt=""><figcaption><p> <em>Giao diện quản trị dạng card</em></p></figcaption></figure>

\+ Tabular administration interface

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/gVrFiLayRRCc4PXO0WDD/image.png" alt=""><figcaption><p><em>Giao diện quản trị dạng bảng</em></p></figcaption></figure>

\+ Kanban-style management interface

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/UDheZqjTthPBWLRsEqDm/image.png" alt=""><figcaption><p><em>Giao diện quản trị dạng kaban</em></p></figcaption></figure>

* Filter: The filter structure includes:

**a. Search in filter**

\- By default, it is enabled when the user turns on the filter feature. Users can turn on/off the filter by clicking on the search icon.

\- Search information fields by keywords, display information fields that satisfy or do not find satisfactory values

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/e233NAYiiKDDcxaHizoH/image.png" alt=""><figcaption></figcaption></figure>

**b. Recently used**: Group of information fields most recently used by users, default to 3 information fields most used by users. During the first use, there are 3 fields set to system default: Pipeline, Priority, Status. The other fields are then updated when the user has used the filter.

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/4i5LjtXyrLU3hUkNchzi/image.png" alt=""><figcaption></figcaption></figure>

**c. Ticket information**

\- Ticket information filter includes information fields: Resolution department, ticket ID, Customer, Description, Receiving source, Staff in charge, Group in charge, Tag, Ticket name, Appointment start schedule, Appointment schedule ended, Employee created, Phone number, Email, Address, Ticket/ST name containing words, Child Service task, Child ticket, Filter by SLA, Ticket custom field, Customer custom field.

\- Filter information fields are in the following formats: Multi-option format, time format, text format, search format

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/0iSCprFYCEGbhRDYT6Ah/image.png" alt=""><figcaption></figcaption></figure>

**d**.**Ticket activity:** Filter tickets by time: Last activity the employee assigned the ticket to, Date created, Date closed, Last response, First response

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/GKxsDZ56Arz5mkAX4OQ7/image.png" alt=""><figcaption></figcaption></figure>

**e.Apply:** Click Apply to create tickets that satisfy the settings you created

<figure><img src="https://content.gitbook.com/content/uYmLBe2PfpkcFv78sczo/blobs/Fe08CLsyU5Ea8GjEe8n9/image.png" alt=""><figcaption></figcaption></figure>
