Use casesStatus updates
The sprint status update you rebuild every Monday, written for you
Mitra reads last week's Jira movement itself and groups every issue by epic into shipped, slipped and still open. The full summary goes to a Notion page and a three-line version to Slack. The run happens each Monday at 9am, before anyone asks for it.
Every Monday at 9am, summarize last week's Jira movement by epic into shipped, slipped and still open. Write it to Notion and post three lines to #product.
200 credits to start · no credit card
What the agent actually does.
Read last week's movement
The agent collects every issue whose status changed in the last seven days, with its epic, owner and column.
Sort it into three groups
Closed issues shipped, issues that missed the sprint slipped, and the rest are open with whoever holds them.
Write the full update
The summary lands on your Notion page, epic by epic, so anyone can read the detail without asking you.
Post three lines
What shipped, what slipped, what to watch, with a link back to the Notion page for the rest.
Make it yours.
For product managers who spend Monday morning reconstructing what moved, for stakeholders who read Notion and ask in Slack. Change any of this by saying so — there is nothing to rewire.
- Run it on the last afternoon of the sprint, so the summary is ready for retro.
- Group by team or assignee rather than by epic.
- Email the update to stakeholders outside your Slack, and keep Notion as the archive.
Questions, answered.
Can Mitra group the sprint update by epic instead of by person?
What if my team forgets to move tickets in Jira?
Ready to
reclaim your day?
Build my first agent200 free credits · no credit card · nothing to install