An AI draft that still belongs to the team
Write once, refine in Jira
Project page / SeeCodes
Daily writeup
Updating daily draft
AI is collecting visible in-progress issues, recent Jira comments, and per-task progress snapshots for this project.
Generated markdown
The current implementation supports block editing and a raw markdown mode directly inside Jira.
Project overview
Payments sprint is moving steadily: three tasks are above 75% readiness, two have medium risk, and one identity-provider callback flow still needs tighter validation.
What has been done during last 24 hours
Jordan connected auth screens and token refresh. Priya closed the protected-route wrapper. Sam reviewed API contract changes and added follow-up notes on logout behavior.
All tasks currently in progress
Every active Jira issue is listed separately with its assignee, current status, and a concise summary of what is already done so far.
Blockers / Risks
The main open risk is the SSO callback contract. A smaller risk remains around logout telemetry and cleanup across browser tabs.
Suggested next steps
Finish callback validation, verify logout metrics, and move the highest-readiness task into final review before the next standup.
Source evidence
The writeup is grounded in the Jira project the team is already using.
Editing flow
Automation gets the draft started, but the page keeps the final report editable.
- • Refresh the draft on demand with Update State.
- • Edit individual markdown blocks inline inside Jira.
- • Switch to raw markdown whenever the team wants full control.
What feeds the writeup
- Visible Jira issues currently in an in-progress status category for the project.
- Rendered Jira comments and messages, with special weight on the last 24 hours.
- Per-task AI progress snapshots, including progress, confidence, ready items, remaining work, and risks.
- The previously saved draft so the narrative can preserve continuity instead of starting from scratch.
- The single report language selected in Jira App settings.
Manual refresh plus scheduled generation
A consistent final structure
Project overview
A concise summary of the project state so a reader can orient before reading individual work movement.
What has been done during last 24 hours
Grouped by assignee so daily standups and async check-ins can start with actual movement instead of memory.
All tasks currently in progress
Every in-flight Jira task appears, even when little changed in the last 24 hours.
Blockers / Risks
The draft calls out risks explicitly instead of hiding them inside task descriptions.
Suggested next steps
A short operational close that makes the writeup useful beyond a one-time status snapshot.
Where teams use it
Daily standups
Start from a written project-wide view and then go deeper only where the update says attention is needed.
Async updates
Share a clean written status in Slack, email, or internal docs without rebuilding the sprint story by hand.
Cross-functional handoffs
Give PMs, EMs, or QA a compact narrative of what moved, what is still active, and what looks risky.