ℹ️ Where this data comes from
Everything below is a snapshot of local files under .specify/ and docs/jira/ — refreshed
every 5s, no network calls. Task status reflects tasks.md, not live PR state.
🕐 next to a document's status is its own ## Version History table: created date (first row),
days since/until approval, and revision-round count (version bumps after the first row). Needs
{date} fields written as YYYY-MM-DD — older documents, or hand-edited dates in another
format, just don't show it. The feature-level Timeline card rolls this up: start = earliest
document's created date, end = release.md's approval date.
"Details" → Content reads the raw .md file from disk. Jira/Confluence pills next to a document come from a local cache written
the last time you ran sdd jira push / sdd confluence push / sdd review submit/apply —
they can go stale if the ticket changed since then. Click "Check Jira/Confluence status" to make a
live call that refreshes both pills and adds the same APPROVED/NEEDS REVISION/PENDING classification as
sdd review check --doc, plus reviewer comments (shown under 💬) — and, in the same call, the live Jira
workflow status (e.g. "In Review", "Done") for both the review-gate tickets and the Jira Export card's Epic/Story/Task
tickets. That's the only thing on this page that talks to Jira/Confluence — everything else is local-file-only — and
once you've clicked it for a feature, it quietly re-checks every 5 minutes so it all stays fresh without you clicking again.
Approve and comments update the local Status header (same as sdd review approve --local),
mirror to Confluence if configured, and post a best-effort Jira comment.
Running with --share? Approve/comment are read-only over the network unless the host machine also
passed --write, in which case every write request must carry the one-time token baked into the
link you were given — treat that link like a credential.