Installation and Setup

Sprint Vitals is a Forge app for Jira Software Scrum boards. Jira's Sprint Report covers one sprint. Sprint Vitals puts Intake, Delivery, and Quality on the board across recent sprints, so the team can see whether the backlog was ready, whether the commitment held, and whether Done was actually done. Backlog Health snapshots refined work across the next three future sprints and compares it to a trailing Velocity (N). Delivery tracks committed, added, removed, completed, and spillover, plus Predictability (completed ÷ committed). Quality counts defects created, defects closed, and escaped bugs, separate from delivery. An Executive Summary rolls the trend charts up across teams.

Sprint Vitals 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.

1. Open the Sprint Vitals listing on the Atlassian Marketplace and click Try it free.

   

2. Choose the Jira Cloud site where you want Sprint Vitals, 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.

   

3. Open a Jira Software project that uses a Scrum board. Sprint Vitals appears as a project tab — you do not need to configure anything in Jira project settings first.

4. In the project's horizontal navigation, click the Sprint Vitals tab. The dashboard loads inside your project.

   

5. 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.

   

6. On first load, metric cells may show Syncing… for a few minutes while Sprint Vitals 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.

7. Recommended for admins: open Sprint Vitals Settings from the link on the Sprint Vitals page (top right) or under Your apps in the Jira sidebar.

   

   On the settings page, pick a Scrum Board, set Dashboard Velocity (closed sprints in the trailing mean), adjust the Health Indicator and Predictability color bands if you need to, then click Save settings. See the Settings section below for details.

   

You are ready to use the dashboard. To open Sprint Vitals again later, click the Sprint Vitals tab in any Scrum project's horizontal navigation, pick your board from the dropdown, and refresh if metrics are still syncing.

After you pick a Scrum board, the page is organized in two main sections:

• Backlog Health — live refined work across the next three future sprints (union), plus lists of stale pointed stories (older than 30 days), blocked stories, and updated scope. Refined means story points > 0 and not a cancelled-named status. Save a snapshot before the earliest of those sprints starts; it locks when that sprint becomes active. The Health Indicator is refined points ÷ Velocity (N).
• Sprint Health Dashboard — a table of recent sprints, grouped into Intake, Delivery, and Quality, with one row per sprint.

Intake shows the planned window, Backlog Health, Health Indicator, Velocity (N), and the sprint goal. Delivery shows committed, updated scope, added, removed and cancelled, completed, Predictability (completed ÷ committed), and spillover. Quality shows Defects Created, Defects Closed, and Escaped Bugs. Each sprint has a comment under those three groups. Three trend charts sit with the table: Backlog health, Predictability, and Sprint delivery. Executive Summary (link at the top of the page) shows those charts for every team you add.

For what those numbers mean in practice — and when to open the dashboard during the sprint — see the manual.

Options apply per Scrum board on the Sprint Vitals Settings page (Step 7 above):

• Scrum board — select which board you are configuring. Board names come directly from Jira.
• Dashboard Velocity — choose how many recent closed sprints (2–7, default 4) are used for the trailing mean in the Velocity (N) column.
• Indicators — color bands for the Health Indicator (refined points ÷ Velocity (N)) and for Predictability (completed ÷ committed). Finished work is always the Completed column: Jira Done at sprint close, excluding cancelled statuses.
• Issue counts and types — metric cells default to story points. Turn on issue counts, or a per-type breakdown, under each total.
• Quality — optional team field and value when one board serves more than one team, so defect counts can be limited to that team. Leave both empty to count every matching Defect.

Click Save settings after changing options. Changes apply to the dashboard on the next load. Manage Sprints is required to edit a board's settings.

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.