/
⚠️ Status Naming: How to Ensure Accurate Reports

⚠️ Status Naming: How to Ensure Accurate Reports

Issue Delivery Report uses smart keyword matching to classify your issue statuses into one of four categories:

  • πŸ› οΈ Active

  • πŸ“₯ Waiting

  • β›” Blocked

  • βœ… Done

The accuracy of your metrics β€” including Active Time, Blocked Time, and Flow Efficiency β€” depends on how clearly your statuses reflect their real meaning. To get the best results:

πŸ‘‰ Use words from the lists below
πŸ‘‰ Avoid vague or ambiguous status names like "Triage" or "Custom Phase 1"

πŸ“š Keyword Reference

Below is the complete list of recognized keywords from the app’s logic:

πŸ› οΈ Active Statuses

Used to calculate Active Time

  • in progress

  • doing

  • working

  • designing

  • researching

  • developing

  • develop

  • implementing

  • coding

  • writing

  • building

  • reviewing

  • testing

  • test execution

  • qa in progress

  • visual design

  • ux design

  • ui design

  • finalizing

  • editing

  • adjusting

  • proofing

  • in review

πŸ“₯ Waiting Statuses

Used to calculate Waiting Time

  • to do

  • todo

  • ready

  • open

  • pending

  • backlog

  • grooming

  • planned

  • awaiting review

  • awaiting testing

  • ready for development

  • ready for design

  • ready for qa

  • ready for ux

  • ready for ui

  • review needed

  • ready for feedback

  • ready for delivery

  • waiting for approval

  • waiting for merge

  • waiting for sign off

β›” Blocked Statuses

Used to calculate Blocked Time
(also included in Waiting Time for efficiency calculation)

  • blocked

  • on hold

  • paused

  • waiting for client

  • waiting for input

  • needs info

  • needs clarification

  • waiting for designer

  • waiting for developer

  • waiting for qa

  • waiting for stakeholder

  • needs fix

  • waiting on bug fix

βœ… Done Statuses

Used to detect issue completion and determine end of Total Time

  • done

  • completed

  • closed

  • resolved

  • shipped

  • approved

  • final

  • released

  • merged

  • deployed

  • test passed

  • signed off

🚫 Important Note on Custom Status Names

Issue Delivery Report uses keyword-based classification to determine how long an issue spends in each phase. If your Jira statuses do not include any of the words from the lists above, the app will not be able to categorize them correctly.

This means:

  • Time spent in unrecognized statuses will be ignored or misclassified

  • Metrics such as Active Time, Waiting Time, Blocked Time, and Flow Efficiency will be inaccurate

  • The Pie Chart and badges may not reflect your team's actual delivery behavior

βœ… To ensure accurate results, use only the keywords listed in the categories above when naming your statuses β€” or make sure each status contains one of those words.

For example:

  • βœ… "Blocked - Waiting for Design" β†’ βœ… recognized as Blocked

  • ❌ "UX Freeze" β†’ ❌ unrecognized (should be renamed or updated)

If your workflow includes custom phases that don’t match any category, we recommend updating status names to include clear intent words (e.g., β€œIn Progress,” β€œBlocked,” β€œTo Do”) as a prefix or suffix.