A badge for speed, a descriptor for trust
Badges are quick; descriptors are explainable
Sprint board / AUTH
Board progress badges
To Do
2Low readiness, still being defined
AUTH-21
Define SSO callback edge cases
Waiting on acceptance criteria and API contract notes.
AUTH-24
Document logout behavior across tabs
Direction is emerging but not implementation-ready yet.
In Progress
2Implementation is moving, not fully closed
AUTH-37
Wire protected routes and token refresh
Core flows are live; callback validation remains open.
AUTH-41
Connect billing account guardrails
Main logic is in place, but one API branch is still risky.
Review
2High readiness, near the finish line
AUTH-48
Finalize auth screen copy and errors
Implementation is complete and waiting for review feedback.
AUTH-52
Expose AI progress report on issue view
Ready for QA and release-note confirmation.
Selected task descriptor
The same issue can expose a detailed AI Task Progress view and an AI Progress Report field.
AUTH-37
Wire protected routes and token refresh
What’s ready
- • Protected-route wrapper is implemented and attached to the app shell.
- • JWT refresh handling is live for the primary happy path.
- • Error-state telemetry exists for the standard expired-token flow.
What’s left
- • SSO callback validation still needs negative-path coverage.
- • Logout metrics and cleanup behavior require one more backend review.
Risk flags
- • The callback contract may still change if the identity provider payload shifts.
AI Progress Report
Custom field- • Main protected-route integration is live.
- • Callback validation remains the main unresolved branch.
- • Logout telemetry should be reviewed before closeout.
What ships with this Jira surface
AI Readiness custom field
A compact read-only percentage field that makes issue readiness scannable anywhere the field is exposed in Jira.
AI Task Progress issue panel
A richer task view with progress, confidence, ready/left bullets, risk flags, and a last-updated signal.
AI Progress Report field
A longer-form companion field for teams that want the supporting narrative directly on the issue layout.
Dashboard task descriptors
The same issue-level state can also surface through task popups from active-user and progress analytics views.
Where teams use it
- Run faster standups because the sprint board shows both rough readiness and deeper issue-level explanations.
- Help tech leads decide which ticket needs review, clarification, or unblock support first.
- Give engineering managers a Jira-native way to discuss progress without turning status into guesswork.
- Keep progress, risk, and remaining work attached to the ticket instead of splitting the story across chat and docs.
From status scanning to deeper inspection