Sub-task Daily Status Report

Sign in and sync a Jira filter to load a sprint.

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 yet Sync 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
Delayed by is calculated as days past the due date (against Done Date if closed, or today if still open) — it is not a Jira field. Columns marked ⇱ are mirrored from the Jira filter's own column configuration and are read-only; Jira owns them. Tracking columns are this dashboard's own: click into a cell to type, and the value is saved on the server, per sub-task and per sprint — so it is shared with everyone who opens this page, attributed to whoever typed it, and it survives every Jira sync, a redeploy and a different browser. Nothing typed here is written back to Jira. “Export CSV” downloads every column on screen, including both families.