Green — on track, no delay recorded Amber — 1–3 days delayed Red — more than 3 days delayed
1 Data source
No data is bundled — sync from Jira (panel 2) or upload an export (.xlsx / .csv, same columns as "Export CSV" below) to populate the dashboard.
Click to choose a file or drag it here
.xlsx / .xls / .csv
No data yetSync from Jira or upload a file to begin
2 Sync from Jira
Re-run the same saved filter (34327) against Jira to pull the current set of sub-tasks, statuses, due dates, comments and done dates.
Jira is the source of truth for the columns it owns, and credentials live on the server — never in this page.
Sub-tasks are fetched and stored server-side; this page reads them over the API. Anything you type into a
tracking column belongs to this dashboard, is saved per sub-task, and survives every sync.
Tracking columns
Columns you define here are stored by this dashboard and merged onto the Jira rows on every load.
Removing a column keeps its values — restore the column, or an earlier template version,
and the data comes back with it.
next in 30s
Refreshed
Revised ETA is empty because no sub-task's due date has changed since the sprint started (03‑Aug‑2026) — Jira's tracked previous-due-date field is blank on every item in this filter. Delayed by is calculated as days past due date (against Done Date if closed, or today if still open). Delay Reason isn't tracked in Jira for these sub-tasks — click into any cell in that column to type one in directly; it's saved in this browser (via local storage) so it survives a page reload, and "Export CSV" downloads everything including your typed-in reasons. It is not written back to Jira and not shared with anyone else who opens this file.