Coming soon · In preparation

Blocker Triagefor Jira

See open blocked work and the issues directly blocking it. Bring blocker ownership, status and priority into one focused queue for your Jira project.

Explore the App Ask About Launch

Jira Cloud · Read-only · Atlassian Forge UI Kit

Open blockers onlyCompleted blockers are excluded from the queue.
Ownership in contextReview the owner, status and priority of each direct blocker.
Bounded resultsUp to 500 open project items and 500 linked keys. Warnings identify capped subsets; totals are not a whole-project audit.
The work to review next

Keep the blocker conversation in context

A practical queue for reviewing direct dependencies within one Jira project.

01

Find open blocked work

Review open work with direct blocker relationships, without traversing a multi-level dependency graph.

02

See the blocker details

Bring the blocker owner, current status and priority into the same view as the work it affects.

03

Use age with care

Age means the age of the issue from creation. It does not measure when a blocker link was added or how long work has been blocked.

Local application demo

Explore the blocker queue

Actual application source rendered with synthetic Jira data in a local DOM host adapter. These previews do not show the native Jira host or a production release.

Labeled local source-render demo: Four relationships in the synthetic example pair blocked work with its active blockers.

Review direct blocker relationships

Four relationships in the synthetic example pair blocked work with its active blockers.

Local application demo with synthetic Jira data; DOM host adapter, not a live Jira screenshot.

Labeled local source-render demo: The example narrows to two rows whose blocker has no assignee.

Focus on unassigned blockers

The example narrows to two rows whose blocker has no assignee.

Local application demo with synthetic Jira data; DOM host adapter, not a live Jira screenshot.

Labeled local source-render demo: The example shows the first two distinct priority levels among active visible blockers in this scan, rather than a global highest-priority threshold.

Top 2 priorities in scan

The example shows the first two distinct priority levels among active visible blockers in this scan, rather than a global highest-priority threshold.

Local application demo with synthetic Jira data; DOM host adapter, not a live Jira screenshot.

Labeled local source-render demo: The same synthetic queue at a narrower desktop viewport.

A narrower queue view

The same synthetic queue at a narrower desktop viewport.

Local application demo with synthetic Jira data; DOM host adapter, not a live Jira screenshot.

Focused by design

Review Jira work with a read-only app

  • One project at a time
  • Direct blockers, one hop
  • Completed blockers excluded
  • Explicit item caps
  • No app-owned Jira content storage
  • No external data egress
Launch preparation

A clearer place to review blocked work.

Blocker Triage for Jira is coming soon. Contact Kitawolf Studios with questions about the app or its launch.

Contact Kitawolf Studios
Help and information

Learn about Blocker Triage

Read the user guide and app-specific support, security and legal information.