Linking

Items can be connected to many other things to build a complete workflow: branches, change requests, other items, and duplicates. Linking is permission-controlled (ref_links, cr_links, dependencies, and duplicates permissions).

Linked Branches

You can link a branch (a Git ref) to an item. This is often done automatically when you use the Create Branch & CR action, which generates a branch such as item/12-my-title. Linked branches are shown on the item detail page and can be removed with the ref_links:delete permission.

Linked Change Requests

You can link one or more change requests (CRs) to an item. Linked CRs are listed on the item detail page. Optionally, an item can be configured to automatically change state when a linked CR is merged or closed — for example, automatically setting the item to Closed when its PR is merged.

Dependencies

Items can have dependencies on other items in two directions:

• Blocked by / blocking — An item can be blocked by another item, or block other items.
• Sub-items — A parent item can contain sub-items. The parent shows a progress indicator based on how many sub-items are resolved or closed.

Duplicates

Items can be marked as duplicates of a canonical (original) item. Marking an item as a duplicate typically moves it to the Duplicate state. The duplicate group shows the canonical item and all its duplicates. Adding or removing duplicates is gated by the duplicates:add / duplicates:delete permissions on the affected items.

Item Policies and Linking

Automation rules (see Item Policies) can pre-fill defaults and assignees when an item is created, and can mark stale items after a configurable period of inactivity.