Ticket Linking

Connect related tickets to track dependencies, duplicates, and blockers without merging them together.

Adding a link

Open a ticket and look for the Links section in the detail sidebar. Click Add Link, then choose the relationship type and search for the target ticket by number or title.

Relationship types

| Type | Meaning | |------|---------| | Related | General connection, no direction | | Blocks | This ticket blocks the linked one | | Blocked by | This ticket is blocked by the linked one | | Duplicates | This ticket duplicates the linked one | | Duplicated by | The linked ticket duplicates this one |

Relationships are bidirectional: linking A as "blocks" B automatically shows B as "blocked by" A. Use Blocks / Blocked by to express a dependency, and Related for a general connection. These relationships appear in the ticket detail sidebar.

Viewing links

All links appear in the ticket detail sidebar. Each shows the linked ticket's number, title, status, and relationship type. Click any link to jump to that ticket.

Linking through the API

Integrations work with the same links. With an API key that holds the tickets:write scope, POST /v1/tickets/{id}/links links a ticket to another one, named by its ID or its number, and DELETE /v1/tickets/{id}/links/{linkId} removes a link. GET /v1/tickets/{id}/links lists a ticket's links with tickets:read, and every ticket the API returns carries them in its links field. The relationship types are related, blocks, blocked_by, duplicates and duplicated_by.

A key sees and changes a link only when it can read the tickets at both ends. The API reference has the requests and responses.

Cross-referencing

Mention a ticket number (e.g. #142) in a comment or description and it becomes a clickable reference. This doesn't create a formal link but makes navigation easy.

When to link vs. merge

• Link when tickets are related but represent distinct issues or tasks.
• Merge when the same problem was reported multiple times and you want a single source of truth.