We built Issue Delivery Report for teams who are tired of guessing why issues don’t make it to “Done.”
Instead of just showing total time or status age, this app analyzes full issue history, categorizes time into Active / Waiting / Blocked, and gives clear insights like whether the issue was added mid-sprint or suffered from low flow efficiency.
What makes it unique:
- It runs inside the issue view no switching tabs
- Exports in Markdown, CSV, JSON, TXT
- Flags delivery risks automatically
We’re especially proud of how quickly you can turn any issue into a story of what really happened perfect for retros, reports, or reviews.
We hope it helps your team work smarter. Looking forward to your feedback!
Issue Delivery Report relies on keyword-based classification to group statuses into Active, Waiting, Blocked, and Done. If status names are inconsistent across teams, we recommend reviewing or aligning naming conventions to improve report accuracy.
You can find the full list of supported keywords and guidance here:
Replies
PeekNote
How do you differentiate between “Waiting” and “Blocked” if the status naming is inconsistent across teams?
PeekNote
@masump
Great question!
Issue Delivery Report relies on keyword-based classification to group statuses into Active, Waiting, Blocked, and Done. If status names are inconsistent across teams, we recommend reviewing or aligning naming conventions to improve report accuracy.
You can find the full list of supported keywords and guidance here:
👉 Status Naming: How to Ensure Accurate Reports