Use casesStatus updates

Automate the sprint status update you rebuild every Monday

Mitra automates the sprint status update by reading last week's Jira movement itself, then grouping every issue by epic into shipped, slipped and still open. Mitra writes the full summary to a Notion page and posts a three-line version to Slack. The run happens each Monday at 9am, before anyone asks.

Runs: Mondays at 9am
Used by: Product Managers · Engineering

The prompt

Every Monday at 9am, summarize last week's Jira movement by epic — what shipped, what slipped and what is still open. Write the full summary to the 'Sprint updates' page in Notion, then post a three-line version to #product in Slack.

Jira

Notion

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

Read last week's Jira movement
The agent collects every issue whose status changed in the last seven days, along with its epic, owner and current column.
Sort it into shipped, slipped and still open
Closed issues are shipped, issues that missed the sprint are slipped, and everything else is still open with the name of whoever holds it.
Write the full update to Notion
The summary lands on the 'Sprint updates' page, epic by epic, so anyone who wants the detail can read it without asking you for it.
Post a three-line version to Slack
Three lines go to #product — what shipped, what slipped, what to watch — with a link back to the Notion page for the rest.

Make it yours.

Product managers who run sprints in Jira and spend Monday morning reconstructing what moved, for stakeholders who read Notion and ask in Slack. The agent fits best when the board is the record of truth and the update is the part nobody has time to write. Change any of this by saying so — there is nothing to rewire.

Run the agent on the last afternoon of the sprint instead, so the summary is already written when retro starts.
Group by team or by assignee rather than by epic, for a weekly view of who is carrying what.
Send the update by email to stakeholders who are not in your Slack, and keep the Notion page as the archive.

Questions, answered.

Can Mitra group the sprint update by epic instead of by person?

Yes. Mitra groups last sprint's Jira issues however you ask — by epic, by team, by assignee or by label — because you describe the grouping in plain English instead of configuring a report. Change your mind later and tell Mitra to regroup the update.

What if my team forgets to move tickets in Jira?

Mitra reports what Jira actually says, so a ticket left in the wrong column shows up as still open rather than shipped. That makes the Monday update a reason to keep the board honest. Every run is recorded step by step, so you can see which issues Mitra counted.