29 lines
1.0 KiB
Markdown
29 lines
1.0 KiB
Markdown
# 10 Ticket Links and Blockers
|
|
|
|
## Goal
|
|
|
|
Add structured ticket relationships and a visible blocked state so teams can model dependencies and impediments directly in the ticketing system.
|
|
|
|
## Requirements
|
|
|
|
- Add project-configurable ticket link type labels.
|
|
- Allow tickets to link to other tickets using one of the project's configured link types.
|
|
- Show linked tickets as a list on the ticket detail view.
|
|
- Allow a ticket to be marked as blocked.
|
|
- Blocking requires a comment.
|
|
- Blocked tickets must be visually highlighted on the board with a warning or danger style.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- A project can create and manage its own link type labels.
|
|
- A ticket can display linked tickets using those labels.
|
|
- A ticket cannot be marked as blocked without a comment.
|
|
- A blocked ticket is clearly distinguishable on the board.
|
|
- Blocking and unblocking actions create worklog entries.
|
|
|
|
## Out of Scope
|
|
|
|
- Directional dependency semantics beyond the selected label
|
|
- Automatic scheduling logic from blockers
|
|
- Notifications based on blocker changes
|