Turn your Miro retro action items into real Jira issues
Every Friday we read your team's retrospective board, work out which sticky notes are real actions, and file them as Jira issues without the duplicates.
Every Friday at 4pm, read my team's Miro retrospective board and turn the action items into properly written Jira issues.
Start with Miro List Board Items to pull every item on the board, then Get Sticky Note for the full text of each sticky note. Use Get Frame to work out which frame each note sits inside, and Get Tags from Item to see whether a note carries an action tag. You need to be able to tell the difference between notes in the "Action items" frame or tagged as actions, and the notes sitting in the "What went well" and "What to improve" columns.
Decide which notes are genuinely actionable. Where several people wrote about the same problem, merge those notes into a single item and keep a count of how many people raised it. Skip pure venting, and skip anything that is an observation rather than a next step. Read the "What went well" and "What to improve" notes for context so you understand what an action refers to, but do not file them as issues.
Before creating anything, run Jira Search Issues (JQL) against the project to confirm the action is not already tracked. Retros repeat weekly and the same action often gets re-raised, so if an open issue already covers it, skip it and record that it was already tracked.
For each surviving item, use Jira Create Issue with a clear, specific summary phrased as an action rather than a complaint. In the description, quote the original sticky note text verbatim and name the retro date. Infer priority from how many people raised it, so something several teammates wrote about outranks a one-off remark.
Then write the new issue keys back onto the board. Use Miro Create Sticky Note to place a note carrying the issue key beside each original note, so the team can see at a glance which notes became tickets.
Finally, post one summary to Slack with Send a Message, listing what was created with its issue key, what was merged together, and what was skipped along with the reason. If nothing actionable was found on the board, say so in one line rather than staying silent.
What does this prompt do?
- Reads every sticky note on your retro board each Friday and works out which ones sit in the action items area or carry an action tag
- Merges near duplicates when several people wrote about the same problem, and skips pure venting
- Checks your Jira project first, so an action that is already being tracked does not get filed twice
- Writes the new issue keys back onto the board beside the original notes, and posts one Slack summary of what was created, merged, and skipped
What do I need to use this?
- A Miro account with the retrospective board your team uses
- A Jira project where the action items should be filed
- A Slack workspace and a channel for the weekly summary
- A retro board with a clear action items area, or action notes marked with a tag
How can I customize it?
- Change the day and time, set to Friday at 4pm by default, to match when your retro actually finishes
- Point it at a different board, a different Jira project, or another Slack channel
- Adjust how priority is decided, such as how many people need to raise something before it counts as high
FAQs
What if our retro board does not have an action items frame?
Will it create duplicate issues if the same problem comes up week after week?
Does it turn every sticky note into a ticket?
How does it decide priority?
Can I tell what it did without opening Jira?
Related templates
When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.
Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.
Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.
Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.
Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.
When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.
Stop rewriting retro notes into tickets by hand.
Let Friday's retrospective turn itself into a properly written, deduplicated Jira backlog before anyone logs off for the weekend.