Skip to content

Ticket links guide

Ticket links let you model dependencies and duplicates without losing any ticket data. Every issue keeps its own ID, content, and history.

Supported link types

Type Direction Use case
DuplicateOf Directional From duplicate issue to canonical issue.
DependsOn Directional Issue A needs issue B first.
RelatedTo Non-directional Issues are connected but without dependency.

Quick workflow

  1. Open a project and go to the Issues tab.
  2. Open an issue card, then select the Links tab in Issue details.
  3. Choose target issue, link type, and rationale.
  4. Use DuplicateOf when this issue is not canonical.
  5. Use incoming and outgoing lists to navigate the full link graph.

Duplicate handling (non-loss)

  • Duplicates stay as separate tickets for traceability and reporting.
  • A duplicate points to its canonical ticket through DuplicateOf.
  • The canonical ticket shows incoming duplicates.
  • No merge-away behavior is required to keep auditability.

Auditability

Link create and delete operations are recorded as auditable events with timestamp and process metadata. Use rationale text when creating links to preserve why the link exists.

API endpoints

  • POST /api/tickets/{ticketId}/links to create a link.
  • GET /api/tickets/{ticketId}/links to read links for an issue.
  • DELETE /api/ticketLinks/{linkId} for soft-delete.
  • GET /api/tickets/{ticketId}/linkGraph?depth=2 for graph traversal.
Need onboarding first? See Getting started in 5 minutes.