Documentation
SprintVitals
A Jira Scrum sprint health dashboard — multi-sprint history, backlog readiness snapshots, and configurable completion metrics, all inside your project.
What is SprintVitals?
SprintVitals is a Forge app for Jira Software Scrum boards. It extends Jira's native sprint report into a multi-sprint dashboard — the same core sprint metrics your team already knows (committed scope, work added mid-sprint, completion, and spillover) across recent sprints in one table, with additions such as trailing velocity averages, configurable Custom Completion, and a Backlog Health snapshot you save during the current sprint for the upcoming one — so you can measure how successful refinement was and whether you have enough refined work ready before the next sprint starts.
Installation and first-time setup
SprintVitals runs on Atlassian Forge inside Jira Software. You need a Jira Cloud site with at least one Scrum board. Follow these steps after installing from the Marketplace. Screenshots can be clicked to view full size; press Close, click outside the image, or press Escape to return.
Open the SprintVitals listing on the Atlassian Marketplace and click Try it free.
Step 1 — Find SprintVitals on the Marketplace and start the install. Choose the Jira Cloud site where you want SprintVitals, then click Review. On the Review screen, Atlassian shows trial and billing details for your site — click Install to finish. A Jira administrator may need to approve the app for your organization.
Step 2 — Select your Jira Cloud site, then click Review to confirm permissions and install. Open a Jira Software project that uses a Scrum board. SprintVitals appears as a project tab — you do not need to configure anything in Jira project settings first.
In the project's horizontal navigation, click the SprintVitals tab. The dashboard loads inside your project.
Step 4 — Open SprintVitals from the project tab in the horizontal navigation bar. Use the Scrum Board dropdown at the top of the page to choose which board to view. Sprint rows for that board appear right away.
Step 5 — Pick the Scrum board whose sprint history you want to see. On first load, metric cells may show Syncing… for a few minutes while SprintVitals pulls issue data from Jira in the background. Refresh the page after a short wait — values populate sprint by sprint. A banner at the top of the dashboard also indicates when sync is still running.
Recommended for admins: open SprintVitals Settings from the link on the SprintVitals page (top right) or under Your apps in the Jira sidebar.
Step 7a — Open SprintVitals Settings from the dashboard link or Your apps in the sidebar. On the settings page, pick a Scrum Board, set the Dashboard Average window (closed sprints to average), choose Custom Completion statuses by workflow column, then click Save settings. See the Settings section below for details.
Step 7b — Configure Dashboard Average and Custom Completion per board, then save.
You are ready to use the dashboard. To open SprintVitals again later, click the SprintVitals tab in any Scrum project's horizontal navigation, pick your board from the dropdown, and refresh if metrics are still syncing.
What the dashboard shows
After you pick a Scrum board, the page is organized in two main sections:
- Backlog Health — for the board's upcoming sprint, save a snapshot of refined backlog items (story points > 0). Snapshots lock automatically when the sprint starts in Jira. The section shows refined ticket count and total refined points.
- Sprint Health Dashboard — a table of recent sprints with one row per sprint.
Each sprint row includes columns such as planned dates, goal, committed and added scope, completed work, custom completion (when configured), spillover, backlog health from saved snapshots, and a trailing Average of completed story points across recent closed sprints.
Settings
Options apply per Scrum board on the SprintVitals Settings page (Step 7 above):
- Scrum board — select which board you are configuring. Board names come directly from Jira.
- Custom Completion — choose which Jira workflow statuses count as "completed" for the Custom Completion column. Until you save settings for a board, Custom Completion mirrors the standard Completed column (Jira Done). Saving updates historical closed sprints on that board.
- Dashboard Average window — choose how many recent closed sprints (2–7, default 4) are used for the trailing mean in the Average column.
Use Load defaults to reset status selections for the board. Click Save settings after changing options. Changes apply to the dashboard on the next load.
Support
Questions, bugs, or setup help? Email support@perpetualagile.com. You can also reach us through our support page for SLA details and Atlassian Support options.
Privacy and security
SprintVitals runs on Atlassian Forge. For how we handle data, see our Privacy Policy. For security practices, vulnerability reporting, and incident response, see our Partner Security Policy.