Turn your Miro retro action items into real Jira issues

By General Input

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.

Integrations

  • Miro
  • Jira
  • Slack Bot

Type

Agentic Task

Categories

  • Engineering
  • Product

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.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seatsPause marketing emails to escalated customers, then restore them