Jira Sprint Status Digest with OpenCode
One run every morning, whichever way the board is going. Nine issues or ninety, the digest is two searches, a few issue fetches and a single message, so spend tracks the number of mornings rather than the size of the sprint. OpenCode hands you the model choice on a fixed daily job like that, which is the one lever worth having on it.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Sprint digest 12 May
Day 6 of a 10 day sprint with 34 issues in scope. Four reached Done since yesterday, nine sit In Progress and three are In Review. PAY-1841 has carried the blocked flag for four days with the impediment note waiting on acquirer sandbox credentials from Nordea. Two issues were pulled in yesterday by the product manager and one was pushed to the next sprint.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Jira
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Sprint scope
Which board and project this covers, the JQL that finds your active sprint, and who to name when a query comes back broken.
Digest style
How your standup should read: how many lines before people stop scrolling, whether the assignee belongs on every line, and which headings your team genuinely uses.
Runs on OpenCode
Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why OpenCode for this agent
Board size does not bill
A sprint that doubles in scope does not double the run. The work is a couple of queries and a formatting pass either way, which makes the monthly figure a calendar question.
One lever, set once
With volume fixed by the schedule, the model is the only thing left that moves cost. Pick it once against a morning of real output and you are unlikely to revisit it.
Before you fork
Three teams, three boards. Is that three of everything?
Three forks, three schedules, three runs a morning, each carrying its own JQL, its own headings and its own model. Boards that differ mainly in their JQL are cheap to run side by side, and a team whose digest nobody reads can be paused on its own without disturbing the other two.
Run it with a different agent
Put Jira Sprint Status Digest to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.