Tickets can be linked to each other in four ways: as parent and child, as blocker and blocked, as related, and as duplicates. SAQ has no separate epic, milestone, or subtask objects: a parent ticket is the epic or milestone, and its children are the work under it. A ticket can also carry references to GitHub commits and pull requests.
Before you start
You need to be able to edit the ticket you link from (Owner or Admin, a member of its project, or any workspace user on an Inbox ticket) and to see the ticket you link to. Regular client users cannot link tickets.
Steps
- Open the ticket. The Links row under the description lists every link as a chip prefixed with its kind: Parent, Children, Blocks, Blocked by, Relates to, Duplicates, and GitHub. The row is hidden when there are no links and you may not add one. The Files row that lists the ticket's attachments sits directly under it (see Attach files).
- Select the plus at the end of the row (Add a link), choose the Link type (Relates to, Blocks, Duplicates, Parent, or Sub-ticket), then find the other ticket: type its id (for example
ACME-12, or just12) or a few words from its title, and pick it from the list that appears, which links it at once. The list shows only tickets you can see, never the ticket you are on, and it opens above the field when there is no room below. You can also type the full id and select Link. Parent places the ticket you are on under the ticket you pick; Sub-ticket places the ticket you pick under the ticket you are on, and needs edit rights on that ticket. - To remove a link, select the cross on its chip (Remove link). A parent is removed from the child's page; the children list on the parent is read-only.
To break a ticket down, select New sub-ticket in the Links row. The new-ticket form opens with the ticket named at the top ("Sub-ticket of ACME-200 Release 3.2") and its project preselected; the ticket is created under it. The button is shown when you may edit the ticket and it is not archived.
To link GitHub, select the plus (Add a link), paste a commit or pull request address into the GitHub URL field, and select Link GitHub. Select the cross (Done linking) to close the forms again.
Rules
- Parent and child. A ticket has at most one parent and any number of children. Setting a parent from ticket A to ticket B makes A a child of B. A ticket cannot be its own parent or ancestor, and a chain of parents is limited to 10 levels, counting the moved subtree. Closed linked tickets are shown struck through.
- Estimates roll up. A ticket with children has no estimate of its own; its Estimate row shows the sum of the estimates of the children you may see, marked "(sum of children)". An estimate set before the ticket got children is kept but not counted; the row says so ("This ticket also has an estimate of its own (2h) that is not counted.") with Remove it for those who may set estimates. Reports grouped by ticket roll time up through visible ancestors as well. See Estimate.
- Time rolls up. On a ticket with children, the Time group shows the ticket's own logged time and a second line "including sub-tickets" that adds the time logged on every descendant you may see. Time may still be logged directly on a parent, but the group then says "1h is logged directly on this ticket rather than on a sub-ticket.", and the Time spent box in the comment form carries the same hint.
- On boards and lists. A sub-ticket's card and list row carry its parent's id; a parent's card shows how many of its visible sub-tickets are closed. The Sub-tickets filter hides sub-tickets or keeps one parent's sub-tickets only. See Use boards.
- Dates are held softly. A sub-ticket may start before its parent or be due after it, but both pages say so: the child shows "Starts before the parent ticket (1 Oct 2026)" or "Due after the parent ticket (31 Oct 2026)" next to its dates, and the parent shows "2 sub-tickets fall outside these dates". On one ticket, a start date after the due date is refused. See Update a ticket. A project's timeline draws the same tree against a calendar and lets you move a parent with or without its sub-tickets.
- Blocks and blocked by. "A blocks B" appears as Blocks on A and Blocked by on B. Dependency cycles are refused, and a chain of blockers is limited to 10 links.
- Relates to and duplicates. Symmetric links with no rules beyond not linking a ticket to itself. Marking a duplicate does not close or merge anything; close the duplicate yourself if that is what you mean.
- One link per pair and type. Linking the same two tickets the same way twice does nothing.
- Recurring tickets. A ticket created by a recurring series cannot have sub-tickets, and its own parent is set on the series rather than on the ticket. The series may name a parent; every occurrence then becomes a sub-ticket of it, and the parent's estimate roll-up grows with them.
- Visibility. Links to tickets you cannot see are hidden entirely: no title, no id, no count. The link exists and other people see it. A parent you cannot see is not shown on the child either.
- Ticket history. Adding or removing a link is recorded on both tickets ("added a link (Blocks)"); setting a parent is recorded on the child.
- Links travel. Moving a ticket to another project keeps every link. Deleting a ticket removes its links; its children stay and lose their parent.
- GitHub links are references only. SAQ stores the repository, commit SHA or pull request number, and the address you pasted. It never contacts GitHub, fetches nothing, and has no GitHub app or webhook. The link shows as
owner/repo @ 1a2b3c4orowner/repo #42. An Owner or Admin sees every link in the workspace under Settings → Channels → GitHub. See GitHub links.
Examples
Planning a release: create a ticket "Release 3.2" with kind Planning, then open each work ticket and set Parent to ACME-200. "Release 3.2" shows the children and the sum of their estimates.
A bug cannot be fixed before an upgrade: open the upgrade ticket, choose Blocks, enter the bug's id, and select Link. The bug then shows the upgrade under Blocked by; there is no separate "Blocked by" link type to choose.
Through the API: POST /api/w/acme/tickets/ACME-184/links with {"targetId": "01924c3e-6b2a-7d11-9d0e-3a1f4b5c6d7e", "kind": "blocks"}; PUT /api/w/acme/tickets/ACME-184/parent with {"parentId": null} clears the parent. The MCP tool link_tickets accepts ticket ids such as ACME-184 directly, and with "kind": "parent" makes source a sub-ticket of target; update_ticket takes parent (a ticket id, or null to detach). See the API reference and the MCP page.
Common problems
- "There is no ticket at this address that you can see." The id you typed does not exist or you may not see that ticket.
- "A ticket cannot link to itself." / "A ticket cannot be its own parent." Check the id.
- "That would make the ticket its own ancestor." The parent you chose is already below this ticket in the tree.
- "The parent chain would be too long." / "The dependency chain would be too long." The limit is 10 levels or links; flatten the structure.
- "That link would create a dependency cycle." The target already blocks this ticket, directly or through other tickets.
- "Paste an https://github.com/…/commit/… or …/pull/… URL." Only commit and pull request addresses on github.com are accepted; the repository in the address must match, the SHA must be 7–40 hex characters, and the pull request number must be positive.
- "A parent ticket has no estimate of its own; it is the sum of its children." Set estimates on the children.
- "A recurring ticket cannot have sub-tickets." / "A recurring ticket takes its parent from its series." Occurrences of a recurring series are leaves, and their parent is edited on the series page. See Recurring tickets.