๐ ๏ธ Administratorโs Guide
This guide is for Jira Cloud administrators responsible for managing and configuring the Sprint Health Analyzer app.
The app runs in the context of a Jira project and uses changelogs, sprints, statuses, and story point fields to generate visual reports about delivery risk and Agile progress. No additional configuration is required โ but some setup steps can improve accuracy.
โ Installation
Go to Atlassian Marketplace and search for Sprint Health Analyzer.
Click Get app and install it to your Jira Cloud instance.
Grant project-level access to users or groups who need to use the app.
๐งพ Required Permissions
Feature | Required Permission |
|---|---|
Load sprint issues | Browse Projects |
Read issue fields and links | View Issues |
Access changelog history | View Development Tools |
Export data (CSV, JSON, etc.) | No additional required |
๐ The app does not write to issues or modify any data in Jira.
๐ฆ Data Used by the App
The following fields and resources are used internally:
Source | Purpose |
|---|---|
| Used to calculate cycle time and pattern |
| For detecting status jumps and time in status |
| For dependency and blocking analysis |
| Required for velocity/burndown/burnup |
| Used to determine scope and velocity |
| Used as fallback for issue closure time |
โ๏ธ Recommended Setup for Best Accuracy
Recommendation | Why It Matters |
|---|---|
Use standard naming for statuses | Needed for blocked/done state detection |
Ensure Story Points field is present | Required for Agile metrics |
Avoid changing issue statuses manually | Can distort cycle time and jump count |
Limit sprint scope changes mid-sprint | Affects burndown and burnup reliability |
๐ Supported Environments
Feature | Supported |
|---|---|
Jira Cloud (UI Kit) | โ Fully supported |
Jira Data Center | โ Not supported |
Team-managed projects | โ Supported |
Company-managed projects | โ Supported |
Classic workflows | โ Supported |
Next-gen workflows | โ Supported |
๐ Troubleshooting
Issue | Suggested Fix |
|---|---|
โNo data availableโ on load | Ensure sprint exists and issues are assigned |
Health Score = 0 for all issues | Missing changelog access or invalid status names |
No velocity/burndown shown | Story Points missing or unassigned sprint |
App doesnโt load | Refresh page or re-authenticate if session expired |
๐ค Data Storage & Privacy
All data is fetched from your Jira instance via Forge.
No data is sent to external servers.
Metrics are calculated client-side inside the browser.
๐ค Support
For help with setup or technical questions, contact us at: