---
title: Create and View Sub-Ticket
slug: citsmart-8-en/create-and-view-sub-ticket
description: Learn how to register a ticket with activities linked to the original ticket. Follow the steps to register employees, contracts, units, and associate them accordingly. Don't forget to register the necessary portfolio of services and activities, along with
docTags: 
createdAt: 2022-01-19T23:00:18.000Z
---

This functionality allows registering a ticket with activities related to the original ticket.

## Before getting started

It is necessary to previously register the employee, contract, and unity. It is also necessary to link the group to the contract, unit to the contract and&#x20;contract to the service.

Register the portfolio with services and activities of request and incident. Set&#x20;the time of attendance for the activities of request and incident.

Link the activities of request and incident to the service contract. Set the&#x20;parameter 385 with value "**Y**".

## Procedure

1. Access the functionality of the Ticket Management 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 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 executor group of the main ticket.
5. To search for tickets related, it will be necessary to select the filter "**Show related**" in   &#x20;the search area on the main screen of the functionality.

:::hint{type="info"}
🖊 <u>**Note:**</u>

The 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.

However, it can be reopened at any time, regardless of the status of the parent's request (whether it is reopened or closed).
:::

