How QueueGuard Works
QueueGuard is a Chrome extension for Jira Service Management queue governance. It helps rank visible queue work, guide execution, and explain why certain tickets should be handled first.
QueueGuard evaluates visible Jira queue/list items only. It does not claim to evaluate hidden, unloaded, filtered-out, or unavailable Jira data.
Before installation
Before using QueueGuard, make sure you have:
- Google Chrome
- Access to Jira Service Management
- Permission to access the Jira queue/list you want QueueGuard to evaluate
- A QueueGuard Pro license key if you want to use Pro features
Install steps
Install from Chrome Web Store
Open the QueueGuard Chrome Web Store listing, click Add to Chrome, and confirm installation.
Open QueueGuard Options
Open the extension options page and review the onboarding, governance, and license settings.
Configure Jira
Enter your Jira Cloud site URL, configured Jira account email, and API token if required.
Save and test connection
Save settings and click Test connection to confirm QueueGuard can connect directly to your Jira Cloud site.
Choose a governance profile
Start with Balanced Operations unless your team has a specific operational pressure such as SLA risk, backlog cleanup, or ownership gaps.
Open a Jira queue/list view
Go to the Jira Service Management queue/list you want QueueGuard to evaluate.
Open the QueueGuard side panel
Open QueueGuard, click Refresh if needed, and review Queue Health, Execution Command, and Selected Issue Decision.
Work the plan
Follow the Execution Command, work the recommended issue first, mark items done as you progress, and run the next pass when the workflow is complete.
Governance profiles
- Balanced Operations - general prioritization across SLA, priority, age, stale work, and ownership.
- SLA Protection - use when breached or near-breach SLA pressure is the dominant risk.
- Backlog Reduction - use when aging or stale work needs cleanup and sequencing.
- Ownership Cleanup - use when unassigned or unclear ownership work is creating accountability gaps.
What QueueGuard does and does not do
QueueGuard does
- Rank visible Jira queue/list items.
- Surface operational risk signals.
- Provide SLA confidence language based on available Jira data.
- Guide execution order through the side panel.
- Store configuration locally in Chrome extension storage.
- Send configured requests directly to your Jira Cloud site.
QueueGuard does not
- Replace Jira or Jira Service Management.
- Claim to evaluate hidden, unloaded, filtered-out, or unavailable Jira data.
- Send Jira data to a QueueGuard backend.
- Guarantee Jira SLA timer accuracy, because SLA configuration varies by Jira setup.
- Change Jira tickets without your direct action.
- Sell user data.
Feedback
Early feedback helps improve QueueGuard. If you are using QueueGuard during early access, please share what worked, what was confusing, and what would make it more valuable for your queue workflow.
Support
For installation help, Jira setup questions, license support, or privacy questions, contact contact QueueGuard support.