📘 How to Use Issue Delivery Report
🧭 Overview
Issue Delivery Report is a Jira Cloud app that analyzes how long an issue spends in different workflow phases — Active, Waiting, Blocked, and Done — based on your team's status naming. It calculates total delivery time, flow efficiency, and highlights potential bottlenecks like excessive wait or blocked time.
It also shows whether an issue was added to a sprint late and provides clear visual indicators and export options for retrospectives, audits, or reports.
🚀 Getting Started
Open any issue in Jira Cloud.
Click the Issue Delivery Report panel on the issue view.
Wait a few seconds while the app loads status history.
View:
A categorized time breakdown
Sprint info (if available)
Flow efficiency warnings (if applicable)
Click Export to download a delivery report in:
CSV
JSON
Markdown
Plain Text
📋 Key Metrics in the Report
Metric | Description |
|---|---|
🕒 Total Time | Total time from issue creation to now or completion |
🛠️ Active Time | Time in “work-in-progress” statuses (e.g. “In Progress”, “Reviewing”) |
📥 Waiting Time | Time in idle or queue statuses (e.g. “To Do”, “Backlog”, “Ready”) |
⛔ Blocked Time | Time in paused or blocked statuses (e.g. “Blocked”, “Needs Info”) |
📊 Flow Efficiency | Ratio of active time to (active + waiting), shown as percentage |
🏁 Sprint Addition | Shows if the issue was added after the sprint started (⚠️ if so) |
⚠️ Warnings are displayed if:
Blocked time exceeds 1 day
Flow efficiency drops below 60%
Sprint addition happened after the sprint start
📤 Export Your Metrics
Use the Export button to download the report in various formats. Each format includes:
All key metrics
Sprint metadata
Key insights
Human-readable durations
ℹ️ Info Section
Click Info to open an interactive explanation with:
Definitions of each metric
How statuses are categorized
Examples of status keywords (e.g., “in progress”, “blocked”, “done”)
Tips for ensuring your statuses are correctly recognized
🧪 How It Works
The app reads the issue's full status history from the Jira changelog API (
/rest/api/3/issue/...expand=changelog)It analyzes transitions, assigns each time period a status category
Duration in each category is calculated and visualized
Flow efficiency is computed automatically
Sprint metadata is extracted if available
All data is stored in-memory; nothing is persisted in Jira unless exported
🛡 Permissions & Data
Issue Delivery Report only reads:
Issue key, status history, and creation date
Sprint metadata (if exists)
Author of status changes
No write actions are performed unless you export the report.
💡 Best Practices
Ensure your status names are intuitive (e.g. “Blocked” instead of “Waiting for Designer”)
Use the report after sprint closure or during retrospectives
Watch for flow efficiency drops — they often signal hidden process issues