Time in Status Gadget
Display Settings & Export
Control how the report looks and export your data for further analysis or sharing.
Display Settings
| Setting | What It Does |
|---|---|
| Number Format | Controls how time values are displayed (comma separators, decimal places) |
| Decimal Places | Precision for time values - 0 for whole numbers, 2 for two decimal places |
| Date Format | Format for date columns in the Status Entrance Date report |
| Chart Type | For chart-based report types: Bar, Line, or Table view |
| Default View | Set whether the gadget opens in Chart or Table view by default |
| Auto-Refresh | Automatically reload data every 10 minutes in view mode |
Export
| Format | What Is Exported |
|---|---|
| CSV | Full table with all issue rows, status columns, group columns, and calculated values |
| PNG | Image snapshot of the chart (for chart-based report types) |
| Configuration | JSON export of all gadget settings for reuse or backup |
Interpreting the Results
Finding Bottlenecks
Open Average Time and sort by time descending. The top row is your biggest bottleneck.
| What You See | What It Means | What to Do |
|---|---|---|
| "In Review" averaging 3+ days | Reviews are not happening frequently enough | Schedule daily review slots |
| "QA" averaging 5+ days | QA capacity is too low relative to developer output | Add QA resource or reduce WIP |
| "Waiting for Customer" averaging 10+ days | Follow-up is not happening | Add SLA reminders or escalation rules |
| "To Do" averaging 7+ days | Work is queued longer than it takes to complete | Review prioritization process |
Spotting Rework
Open Transition Count. Issues with counts > 2 on "In Review" or "QA" are bouncing back and forth - a sign of incomplete work or unclear acceptance criteria.
SLA Tracking
Open Status Entrance Date and export as CSV. Combine with your SLA targets in a spreadsheet to flag issues that have been in a status longer than your policy allows.
Tip: Export the chart as PNG to include Jira process data in presentations or status emails without requiring stakeholders to log into Jira.