📘 How to Use Sprint Health Analyzer

Sprint Health Analyzer is a Forge-based Jira Cloud app that helps Agile teams monitor delivery health inside any sprint. It analyzes each issue's lifecycle using changelog data and calculates a Health Score (0–1) based on multiple delivery risk indicators.

The app also provides Agile metrics (Velocity, Burndown, Burnup), workflow pattern analysis, and one-click exports for retrospectives and reporting.

Everything runs inside your Jira Cloud instance — no external APIs or servers are used.

🧩 Main Features

1. 🔎 Health Score Table

Each issue in the selected sprint is analyzed and shown in a grouped table by Health Score level:

For each issue, the table shows:

• Issue Key: Clickable link to open the Jira issue.

• Health Score: Aggregated metric from four dimensions.

• Status Jumps: Total number of status transitions.

• Blocked %: % of lifecycle time spent in blocked statuses (e.g. Blocked, On Hold, Waiting).

• Link Ratio %: % of issue links classified as “blocking” or “dependency” types (blocks, depends on).

• Cycle Time: Days/hours between first status and Done.

• Pattern: One of four workflow behavior tags (stable, unstable, looping, hub).

• Summary: Tooltip-enabled truncated summary.

• Status: Current issue status.

Tooltip help icons next to column headers explain each metric inline.

2. 🚀 How to Open the App in Jira

To launch Sprint Health Analyzer inside your project:

1. Open your Jira project (e.g. Sprint Alpha – Risk & Flow Test).

2. In the top navigation bar, click the ➕ plus icon next to “Pages”.

3. In the dropdown menu, scroll to the Apps section.

4. Click on Sprint Health Analyzer to open the app.
   
   

Open

3. 📊 Health Score Distribution (Chart View)

A stacked bar chart that visualizes how many issues fall into each health category (✅ ⚠️ ⛔), with percentage labels shown over each bar.

This view is toggled with the "Show Chart" button.

Open

4. 📈 Agile Metrics View

The Agile Metrics tab shows data based on the selected sprint’s date range.

You can customize the start and end dates directly via DatePickers in the UI.

Displayed metrics:

• Velocity: Total story points completed before sprint end.

• Burndown Chart: Remaining story points per day vs ideal linear burn.

• Burnup Chart: Completed points vs total scope over time.

All charts are based on actual issue resolution and addedAt timestamps (when available).

Open

5. 📤 Export Options

Click the "Export" button to download data in any of the following formats:

• CSV – Easy import into spreadsheets.

• JSON – Raw data for programmatic use.

• Markdown – Clean table format for Confluence.

• Plain Text (TXT) – Copy-paste friendly format.

Open

All exports include:

• Issue key

• Summary

• Status

• Health Score

• Jumps

• Blocked %

• Links %

• Cycle Time

• Pattern

6. ℹ️ Info Panel

Click the "Info" button to view an inline panel with:

• Full explanation of health metrics and patterns

• How data is calculated (statuses, dependencies, time windows)

• Classification logic (e.g., what counts as “Blocked” or “Done”)

• Usage benefits and common use cases

• Link to full documentation and support

7. 🔄 Data Refresh

Click the "Refresh Data" button to manually reload all issues and sprint metadata. This also refreshes changelog data used for all metrics.

Internally, this triggers:

• Re-fetching sprint list and detection of current sprint

• Re-running changelog analysis for each issue

• Recalculating health and agile metrics

🧠 How Health Score is Calculated

Each issue receives a score based on 4 components (normalized):

The final score is adjusted with a +0.1 buffer (clipped at 1.0) to avoid excessive penalization of borderline cases.

🧭 Workflow Pattern Tags

The app detects one of the following tags per issue:

• 🟢 stable — Few jumps, short cycle, low blockers

• 🔴 unstable — 8+ status jumps, many regressions

• 🟡 looping — Repeated back-and-forth transitions + blockers

• 🟣 hub — Over 50% of links are dependencies/blockers

Patterns are shown using colored lozenges and help identify common anti-patterns in your sprint.

📅 Sprint Selection Logic

On app load:

• Tries to detect current active sprint (sprint IN openSprints()).

• If not available, selects the latest available sprint with issues.

• You can manually change the date range in the Agile Metrics view using DatePicker.

✅ Requirements

• Jira Cloud project with sprints

• Changelog enabled (used for status history analysis)

• Story Points field available (used in Agile metrics)

🙋 Need Help?

• Click Support in the app

• Or contact support@typeswitch.net