​
Understanding Ticket Relations

Ticket relations help you organize complex work by creating parent-subticket relationships between tickets. Parent and subtickets can exist in different queues, providing flexibility for organizing work across different teams or project areas. Introduction

​
How Relations Work

When you create a new ticket, you can specify a parent ticket to establish the relationship immediately. You can also establish relationships between existing tickets by editing a ticket and selecting its parent. This flexibility allows you to organize work as projects evolve and relationships become clear.

​
Adding Parent Tickets

You can attach a parent ticket to an existing ticket in several ways: From Ticket Details: Navigate to the ticket details page and use the actions dropdown. Select Relations and then Add Parent Ticket. This opens a modal where you can browse and select from existing tickets to connect as the parent. Introduction Introduction From Ticket Lists: In any ticket list or table view, use the actions dropdown in the rightmost column. Select Relations and then Add Parent Ticket. The same modal flow allows you to browse and select an existing ticket to serve as the parent. Both methods open the same existing ticket list modal, giving you the ability to search through and select the appropriate parent ticket for your relationship.

​
Adding Subtickets

You can add subtickets to a parent ticket in multiple ways: From Ticket Details: When viewing a ticket details page, you’ll see an Add Subticket button prominently displayed in the middle of the screen. Click this to add a new subticket to the current ticket. From Actions Menu: Similar to adding parent tickets, you can use the actions dropdown and select Relations, then Add Subticket. This provides the same functionality as the button in ticket details.

​
Viewing Relationships

Parent Information: Tickets display their parent relationship prominently, showing the parent ticket number and queue prefix. This provides immediate context about where the ticket fits in the larger project structure. In ticket lists and tables, subtickets show a parent ticket badge that you can click to navigate directly to the parent ticket. Subtickets: Parent tickets show a list of their subtickets, including titles, descriptions, current status, and priority levels. This gives you a complete view of all related work items and their progress. In ticket lists and tables, parent tickets display a count of their subtickets, making it easy to see how many related work items exist at a glance. Cross-Queue Relationships: Parent and subtickets can exist in different queues, providing flexibility for organizing work across different teams or project areas. This allows you to maintain relationships between tickets even when they belong to different parts of your organization. Organizing and Sorting: You can group tickets by parent in ticket lists and tables, making it easy to see all related work items together. You can also sort tickets by parent.

​
Archiving Behavior

When you archive a parent ticket, all of its subtickets are automatically archived as well. This cascading behavior ensures that when a project is completed or put on hold, all related work items are properly organized and removed from active ticket lists. The system handles this process automatically throughout the entire hierarchy, so if subtickets have their own subtickets, those are archived too. This maintains the integrity of your ticket relationships and prevents orphaned tickets from cluttering your workspace.

​
Unarchiving Tickets

When you unarchive a parent ticket, all of its subtickets are automatically unarchived as well. This ensures that when you resume work on a project, all related tickets become available again with their relationships intact. The automatic unarchiving process maintains the complete project structure, so you can pick up where you left off without manually unarchiving individual tickets.

​
Deleting Tickets

When you delete a parent ticket, all subtickets are permanently deleted as well. This cascading deletion ensures that removing a project removes all associated work items, maintaining clean data organization. The deletion process works automatically through the entire ticket hierarchy, so complex project structures are completely removed when the parent ticket is deleted.

​
Summary

Ticket relations provide a powerful way to organize complex work through parent-subticket relationships. By breaking down projects into manageable components while maintaining clear connections between related work items, you can improve both individual productivity and overall project visibility. The automatic archiving and deletion behavior ensures that your ticket organization remains clean and consistent, while the flexible relationship structure adapts to different project types and organizational needs. Use these relationships to create clear project hierarchies that make complex work more manageable and trackable.