PI4 Sprint 1 — Sub-task Daily Status

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 site URL

Filter ID

JQL (overrides Filter ID when set)

Also sync on every auto-refresh

Credentials live on the backend, not here. Set JIRA_EMAIL + JIRA_API_TOKEN in backend/.env, run npm start inside backend/, then sign in above (Microsoft and/or the plain testing login, depending on AUTH_MODE). Sub-tasks are fetched and stored server-side; this page only reads them over the API.

Auto-refresh every 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.

Status Component RAG Delayed only

Epic ▲▼	User Story / Task ▲▼	Sub-task ▲▼	Components ▲▼	Assignee ▲▼	Last Comment ▲▼	Due date ▲▼	Revised ETA ▲▼	Delayed by (days) ▲▼	RAG ▲▼	Status ▲▼	Delay Reason ▲▼	Done Date ▲▼	Jira ▲▼