⚠️ Status Naming: How to Ensure Accurate Reports

Sprint Health Analyzer relies on status names to calculate delivery metrics such as health score, cycle time, blocked ratio, and workflow patterns. To ensure accurate reporting, your Jira project should follow certain naming conventions — especially for “Done” and “Blocked” statuses.

This guide explains how the app uses status names and how you can align your workflows for best results.

Sprint Health Analyzer does not rely on Jira status categories (like “To Do” or “Done”), but instead uses exact name matching based on built-in keyword lists.

Used to detect when work finishes and calculate cycle time and velocity.

ℹ️ These statuses are case-insensitive and matched via .includes() or .toLowerCase() logic.

Used to calculate % of time spent blocked, which impacts the Health Score and workflow pattern.

1. Use clear, consistent naming
   Avoid generic names like “Step 3” or “Doing (2)”. Use descriptive terms like “Waiting for Review” or “In Progress”.

2. Map your blocked states
   If your team uses custom status names for blocked-type states (e.g. “Pending Client”), consider renaming or aligning them to one of the recognized values above.

3. Use automation if needed
   Use Jira automation to automatically transition issues into/from standard blocked states based on issue fields, SLA violations, or labels.

If your project uses fully customized workflows with non-standard status names:

• The app will still calculate metrics.

• However, Blocked % and Cycle Time may be inaccurate if your “blocked” or “done” statuses are not included in the app's lists.

📝 You can submit a feature request to support custom status mappings via project settings.

In exports (CSV, JSON, MD, TXT), the app includes:

• Raw status name

• Status jump count

• Cycle time

• Blocked time ratio

Any misalignment in status naming will be visible in these exports.