Jira Sprint Status Digest

Standup is twelve people taking turns to read out a board that everybody could have read. Each morning this agent runs your sprint JQL and posts one Slack message: yesterday's closes, the work in flight, every blocked issue with the reason quoted from the ticket itself, and whatever entered or left the sprint since it opened. Teams spread across time zones get the same picture without needing to be awake at the same moment as each other.

What people use it for

• Standup becomes something you read - The circle exists because nobody has looked at the board. Once the board turns up in Slack at nine, the meeting either shrinks or quietly stops, and the people in the wrong time zone stop missing it entirely.
• Blockers arrive with their reason - Each blocked line quotes the impediment text and how long it has sat there, so a four day wait on an outside vendor reads as four days rather than as a red icon nobody has clicked.
• Mid sprint additions stop hiding - Work that turned up after the sprint opened is listed by key, so at the end of the week nobody has to argue about whether scope changed, only about what to do next time.
• A written record for retro - Each morning's message stays in the channel, so at retro you scroll back to the day a blocker first appeared rather than reconstructing the fortnight from memory.

Before you fork

We already have a board and sprint reports. Why a digest?

Both wait for somebody to open them, and neither one quotes the blocker text out loud. This lands where your team is already typing, with the flag reasons and the late arrivals spelled out. If your board honestly does get read by everyone before standup, you do not need this.

Can it change anything on the board?

No. Its Jira access is a search and a read, and it is instructed never to transition an issue, post a comment, or edit the sprint. The Slack message is the entire output, so the worst outcome is a wrong line in a channel rather than a wrong state on a board twelve people are working from.

What does it need from Jira, and what does a month of mornings cost?

A Jira credential that can browse the project and run JQL, plus a Slack channel to post into. It runs once each morning whether the sprint holds nine issues or ninety, so spend follows the schedule rather than the board. The schedule step sets the time and the time zone, which lets it land twenty minutes ahead of standup wherever your team sits.