Issue Relations and Dependencies

Issue relations show how work items depend on or relate to each other inside one Team.

Use relations when two Issues should stay connected without becoming parent/child work. Use dependencies when one Issue blocks another. Duplicate marking stays in the workflow-owned duplicate flow, and sub-Issues stay in the hierarchy flow.

Relation types

V1 relations are same-Team only. Cross-Team relations are intentionally deferred so Team keys, private Team visibility, Team moves, and status translation stay predictable.

Add relations to existing Issues

Open an Issue and use the Issue menu:

... -> Mark as -> Related to...
... -> Mark as -> Blocked by...
... -> Mark as -> Blocking...

The picker lists readable active Issues from the same Team. Hidden private-Team targets do not appear.

When you mark an Issue as Blocked by, Integrity moves the blocked Issue to the Team Backlog status. The status keeps the Team workflow status, but the UI shows a blocked Backlog treatment while a visible active blocker remains.

Create related Issues

Use Create related from Issue detail or an Issue row menu to create a new Issue and link it after save:

... -> Create related -> Issue...
... -> Create related -> Blocked issue...
... -> Create related -> Blocking issue...

The create dialog shows a pending relation badge before save. You can open that badge to review the target Issue and remove the pending relation before creating the new Issue.

Apply relations to a selection

After selecting editable active Issues from one Team, open Actions:

• Create related creates one new related, blocked, or blocking Issue against the complete selection.
• Mark as → Related to..., Blocked by..., or Blocking... links every selected Issue to one chosen target.
• Mark as → Duplicate of... marks every selected Issue as a duplicate of one canonical target.
• Remove relations removes one shared related, blocked-by, or blocking target, or unmarks every affected duplicate in the selection.

The confirmation names the relation direction and any blocked-to-Backlog or Duplicate-status effect. Existing identical links are treated as successful retries without duplicate Activity, and every database-visible change succeeds together or rolls back together. Removal confirmation stays in the same selection palette and reports the affected count. Removing a blocker does not change status; unmarking a duplicate restores its previous active status when available, otherwise the Team default.

Resolve blockers

When the blocking Issue moves to a completed or canceled status, Integrity converts the blocking dependency to Related.

The formerly blocked Issue stays in Backlog until someone changes its status. Integrity does not restore a previous status automatically because later workflow decisions may have happened while the Issue was blocked.

Where relations appear

Relations can appear in:

• the Issue detail right drawer under Relations;
• Issue table badges for blocked and blocking work;
• the Relations filter group in Issue tables;
• Issue Activity entries for relation creation, removal, create-related saves, blocked-to-Backlog movement, and blocker resolution.

Related