Find active requests outside your selected queues.

Queue Coverage for JSM checks the actual memberships of the operational queues you choose, for the signed-in agent. It distinguishes covered requests, requests outside those queues, intentional exclusions and unknowns.

Submission preparation. This app is not yet approved or available for purchase on Atlassian Marketplace.

Choose the scope

A project administrator saves 1–10 operational queues and To Do / In Progress categories. Checks include up to 200 visible requests with a Customer Request Type. Every observation names its policy version and read interval.

Make intentional exclusions explicit

Exclude a currently readable request using a predefined reason and an expiry within 30 days. The result shows the excluded row and removes it from the eligible denominator. Expired exclusions become eligible again.

Recheck before exporting

Each CSV is generated by a fresh permission-checked scan. Results clear after one minute. Optional personal history stores only run dates and policy versions, not request content or result counts.

Understand the limits

Queues using currentUser() can differ between agents. Partial reads never establish that a request is outside all selected queues. These are non-atomic observations; Jira indexing can lag. The app does not modify Jira, fix filters or promise that no ticket will ever be missed.

Read setup and use instructions · Review security and retention