Last updated: October 2026
Backlog Guardian for Jira helps teams monitor backlog hygiene and identify common quality issues before they affect planning and delivery.
1. Overview
Backlog Guardian scans Jira projects for common backlog hygiene issues and summarizes the result in a Backlog Health Score from 0 to 100.
The app currently checks for:
- Unassigned issues
- Stale issues
- Overdue issues
- Missing estimates
- Stale epics
Each check shows the number of affected issues and allows users to inspect the underlying Jira work items.
2. Installation
Backlog Guardian is installed from the Atlassian Marketplace into a Jira Cloud site.
To install the app:
- Open the Backlog Guardian Marketplace listing.
- Select the option to install or start a trial.
- Select the Jira Cloud site where the app should be installed.
- Approve the requested Jira permissions.
- Open Backlog Guardian from Jira after installation completes.
Backlog Guardian is a Jira Cloud app built on Atlassian Forge.
3. Selecting a project
Use the project selector at the top of Backlog Guardian to choose the Jira project you want to inspect.
The app only displays Jira projects that the current user is permitted to access.
4. Backlog Health Score
The Backlog Health Score provides a simple summary of backlog hygiene. The score ranges from 0 to 100.
A higher score indicates fewer detected backlog hygiene problems. The score breakdown shows which checks contribute penalties to the current score.
The current scoring model considers:
- Overdue issues
- Stale epics
- Unassigned issues
- Stale issues
- Missing estimates
5. Backlog checks
Unassigned Issues
Detects open Jira issues that do not currently have an assignee.
Stale Issues
Detects open issues that have not been updated within the configured number of days.
Overdue Issues
Detects open issues where the due date has already passed.
Missing Estimates
Detects open issues that do not contain the configured estimate information.
Supported estimate methods include:
- Original Estimate
- Story Points
- Disabled
Stale Epics
Detects epics that have not been updated within the configured stale epic threshold.
6. Inspecting affected issues
Checks with affected issues include a View issues action.
Selecting this action opens a detail section showing the affected Jira issues, including their issue key, summary and status.
Issue keys can be opened directly in Jira for further investigation and cleanup.
7. Project configuration
Backlog Guardian supports project-specific monitoring settings.
Available settings include:
- Enable or disable automatic monitoring
- Stale issue threshold in days
- Stale epic threshold in days
- Estimate method
Configuration changes require the appropriate Jira project administration permissions.
8. Manual scans
Use Run scan now to perform an immediate backlog health scan for the selected project.
After the scan completes, the latest Backlog Health Score, check counts and score breakdown are displayed.
9. Automatic daily monitoring
Projects with monitoring enabled are scanned automatically once per day.
The latest completed scan is stored and shown when users return to Backlog Guardian.
10. Permissions
Backlog Guardian uses Jira permissions to control access to project and issue data.
Interactive Jira access is performed according to the permissions available to the current Jira user where applicable.
Project configuration changes are restricted to users with the required project administration permissions.
11. Licensing
Backlog Guardian is distributed through the Atlassian Marketplace.
When the app does not have an active Marketplace license or trial, Backlog Guardian operates in read-only mode.
Existing backlog health information can still be reviewed, but configuration changes and manual scans require an active license or trial.
12. Data and hosting
Backlog Guardian is built on Atlassian Forge.
Application compute and persistent application storage are provided by Atlassian infrastructure.
Backlog Guardian does not require an external application server or external database for its core functionality.
13. Troubleshooting
No projects are visible
Confirm that the current Jira user has permission to browse the relevant project.
Settings cannot be changed
Confirm that the current user has the required Jira project administration permissions and that the app has an active license or trial.
A check shows unexpected results
Review the configured stale thresholds and estimate method for the selected project. You can also open the affected issues to verify the underlying Jira data.
Manual scan is unavailable
Manual scans require an active Marketplace license or trial.
14. Support
If you need help with installation, configuration, licensing or unexpected scan results, visit the Backlog Guardian Support page.