# 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.

- Workflow type: agent
- Services: Miro, Jira, Slack Bot
- Categories: Engineering, Product
- Published: 2026-08-07

## What it does

- 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 you'll need

- 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

## Prompt

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.

## How to customize

- 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

## FAQ

### What if our retro board does not have an action items frame?

It also looks for notes marked with an action tag, and falls back to judging the wording of each note. Naming a frame "Action items" gives the cleanest results, but it is not required.

### Will it create duplicate issues if the same problem comes up week after week?

No. Before creating anything it searches your Jira project for an existing issue covering the same action and skips it if one is already open. It also merges near duplicate notes from the same retro into a single issue.

### Does it turn every sticky note into a ticket?

No. Notes in the "What went well" and "What to improve" columns are read for context but not filed, and pure venting is skipped. The Slack summary tells you what was skipped and why.

### How does it decide priority?

Mainly by how many people raised the same thing. Something three teammates wrote about lands higher than a one-off comment. You can change that rule to match how your team grades work.

### Can I tell what it did without opening Jira?

Yes. It places a sticky note carrying the new issue key beside each original note on the board, and posts one Slack summary listing everything created, merged, and skipped.

Use this prompt in General Input: https://www.generalinput.com/prompts/turn-your-miro-retro-action-items-into-real-jira-issues