Blocker Triage user guide

Open the queue

1. Open a Jira project.
2. Where an authorized installation is available, select Blocker Triage in project navigation. Development installs show a Dev badge.
3. On first use, allow the app's read-only Jira access when Jira asks.

The app starts with the relationship direction that most closely matches Jira's default Blocks — is blocked by wording.

Read a row

• Blocked work is an open item in the current project.
• Blocker is the linked issue on the selected relationship direction.
• Blocker age is whole elapsed days since the blocker issue was created.
• Blocker owner is the current assignee, or Unassigned.
• Priority and Status come directly from the blocker.
• Last updated is whole elapsed days since the blocker was updated.

Completed blockers are not shown. A blocked item can appear more than once when several open blockers hold it up.

Choose a relationship

Use “Blocked by” relationship to tell the current scan which linked issue should be treated as the blocker. Jira link types have two labelled directions, so options are explicit—for example Blocks — is blocked by and Blocks — blocks.

The selection lasts for the current page session and is not saved. No Jira configuration is changed.

Focus the queue

• All active blockers — every visible matching relationship
• Unassigned blockers — blocker has no assignee
• Open 14+ days — blocker issue was created at least 14 whole days ago
• Top 2 priorities in scan — the first two distinct priority IDs among visible active blockers returned in Jira priority order. Custom and translated names work. This is relative to this scan, not a site-wide High threshold

Limits

• One project and one link hop per scan
• Up to 500 open project items
• Up to 500 linked issue detail reads
• Calendar/business-day exclusions are not applied
• Blocker age is issue age, not time since the relationship was created
• Hidden linked issues are omitted because the app follows the viewer's Jira permissions

Troubleshooting

• No active blockers found: confirm the selected relationship direction and that the linked blockers are still open.
• No issue-link types: ask a Jira administrator to enable issue linking.
• Permission error: confirm you can browse the project and linked issues directly in Jira.
• Unexpected direction: choose the opposite inward/outward option for that link type.
• Large-project warning: narrow or archive the backlog before using totals as a full audit.

Scan failures and access

If Jira pagination cannot finish, the app shows an error instead of reporting partial totals as complete. A few empty/duplicate pages can be followed when fresh continuation tokens exist; repeated tokens or bounded page/progress limits stop the scan. Short rate limits retry at most twice; long limits ask you to wait. Use Scan again after the condition clears.

Production requires an explicitly active Marketplace license. Missing metadata is allowed only in known development/staging contexts; unknown environments are denied. No extra Jira administration permission is needed for priority sorting.

Result validity and rescan

Queue results and reusable linked-detail cache entries are valid for an absolute 15 minutes from scan start. Changing a focus filter or relationship does not extend that limit. When execution runs, expired queue state and cache entries are cleared, and expired results cannot be reused or completed into the view. Start a new scan explicitly; the app does not refresh automatically in the background. A suspended browser/device can retain memory until JavaScript resumes, so this is not a physical-erasure guarantee during suspension.

Availability and demo images

Blocker Triage is in preparation; this guide does not establish Marketplace availability. Website screenshots render actual application source with synthetic Jira data through a local DOM host adapter. They are not live or native Jira screenshots, and do not certify customer release validation.