---
title: Creating and Viewing Sub-Ticket
slug: itsm-en/creating-and-viewing-sub-ticket
description: Learn how to register a sub-ticket with activities tied to the main ticket in this comprehensive document. Follow the step-by-step instructions to access the Ticket Management feature, create a sub-ticket, and save it. Discover how the system notifies the
docTags: 
createdAt: 2021-10-27T20:28:47.000Z
---

This functionality allows <font color="#3b9f0f">**registering a ticket with activities related to the original ticket**</font>.

## Before getting started

It is necessary:

- [x] To register previously the employee, contract, and unity;
- [x] It is
  &#x20;also necessary to link the group to the contract, unit to the contract and
  &#x20;contract to the service;
- [x] To register the portfolio with services and activities of request and incident;
- [x] To set
  &#x20;the time of attendance for the activities of request and incident;
- [x] To link the activities of request and incident to the service contract;
- [x] Finally, to set the
  &#x20;**parameter 385** with the value '**Y**'.

## Procedure

1. Access the **Ticket Management** functionality through the main menu `Processes  > Ticket Management > Ticket`;
2. Click on the ticket you want and select "**Create sub-ticket**" in the
   &#x20;options menu;
3. Complete all mandatory fields and click on "**Save**". The sub-ticket will
   &#x20;be directed to the executor group defined in the activity link registration,
   &#x20;to the executor group defined in the **parameter 9**;
4. Note that the system will send a notification e-mail about the creation,
   &#x20;escalation, capture, close and other changes in the related tickets to the
   &#x20;executor group of the main ticket.
5. To search for tickets related, it will be necessary to select the "**Show related**" filter in
   &#x20;the search area in the main screen of the functionality.

:::hint{type="info"}
🖊 <u>**Note**</u>**:&#x20;**&#x54;he sub-ticket has its own flow, therefore, it is not finished along with the
&#x20;closure of the origin ticket. It should, then, be executed and closed autonomously.
:::

:::hint{type="info"}
🖊 <u>**Note**</u>**:&#x20;**&#x54;he sub-ticket can be reopened at any time, regardless of the status of the parent&#x20;
request (whether it is reopened or closed).
:::