You know the cycle. Your team runs a great retro. People are honest. Three or four genuinely good action items go up on the board. Someone says "I'll put these in Jira." Everyone nods. Two weeks later you're sitting in the next retro and someone raises the same problem.
That moment, multiplied across thousands of teams, is why a 2023 Scrum Alliance survey found only 35% of teams consistently complete their retro action items. The other 65% are running the conversation, generating the insight, and then losing it within about a week.
I've watched this play out enough times that I have an opinion now, and it's not the one I started with. Most retro action items don't belong in Jira. Some do. The ones that don't belong there are the ones that quietly disappear.
The two camps every team falls into
Camp 1: dump everything into Jira. It feels rigorous. Jira is the system of record for the rest of the work, so if a thing is real it should have a ticket. "Improve our PR review process" becomes JIRA-4471, gets assigned to Sarah, and joins the queue. Sarah remembers it for about six days.
Camp 2: leave them in the meeting notes. Someone pastes the action items into a Confluence page or a shared doc. The expectation is that people will check back. Nobody does. By Wednesday they couldn't find the doc if you paid them.
Both camps fail for the same reason. The place you store an action item should match the cadence and shape of the work it represents. Jira is built for prioritised, customer-facing work that flows through a board. Retro action items usually aren't that. The shared doc has the opposite problem: it tracks nothing.
Why Jira feels right and usually isn't
Putting an action item in Jira looks responsible. You're treating it like real work. It tends to fall flat anyway, for four reasons.
No stakeholders. A Jira ticket usually exists because a customer or a PM wants something shipped. A retro action item exists because the team wants to fix itself. Without external pressure on the assignee, it sinks.
Grooming kills it. Backlogs get prioritised by impact, urgency, and customer pain. "Add a 5-item PR checklist" loses to every customer-facing ticket. Forever.
Invisible to the next retro. When the team brainstorms again, nobody opens Jira to check what's still open from last sprint. The information is technically there. The flow doesn't bring it back into the room.
Process improvements don't scope down. "Communicate better about blockers" or "do refinement before planning" aren't tickets. They're rituals. Forcing them into a story-points-and-acceptance-criteria shape distorts them and makes them harder to do, not easier.
The action items that DO belong in Jira
I want to be fair. Some retro action items absolutely belong in your tracker. The test is whether the action is real shippable work.
- "Add integration tests for the checkout flow." Engineering work, has an outcome a PM cares about, ships.
- "Fix the three flakiest tests in CI." Real work, scoped, owned, ships.
- "Document the on-call runbook for the auth service." Borderline. Real work but it'll never win against customer features in grooming. Probably better in your retro tool with a Jira ticket linked when someone actually picks it up.
The clean rule: if the action item would survive a sprint planning conversation as a regular ticket on its own merits, it belongs in your tracker. Push it there with a one-click export, link the ticket back to the retro item, and move on.
The action items that DON'T belong in Jira
Almost everything else.
- "Stop scheduling refinement on Fridays."
- "Run a 5-minute kudos round at the end of every retro."
- "Try a 4-day sprint for the next two cycles as an experiment."
- "Stop merging on Fridays unless a release manager approves."
These are commitments and rituals. They matter, but none of them have a definition of done that fits a sprint board. They need somewhere they can be revisited weekly without competing for priority against feature work.
That somewhere is your retro tool.
Why the retro tool is the right default
Four things engineering trackers don't do well:
Continuity. When the next retro opens, last sprint's open action items are right there. The team sees them before brainstorming new ones. This single behaviour does more for follow-through than any other intervention I've tried.
Context. The action item lives next to the retro item that produced it. Click through and you see the original "we keep merging on Fridays and breaking things" thread, the discussion, the votes. Tickets in Jira get stripped of all that and become a one-line subject nobody can decode three weeks later.
Cadence. Retro action items want a weekly heartbeat. A ticket on a sprint board wants daily standup attention or it gets buried.
Pattern detection. When the same problem comes up across three retros over six weeks, that's a different problem than a one-off complaint. Jira can't surface that, because it doesn't know the items are related.
That last one is what tipped me. The first time I saw a tool flag "this team has raised CI flakiness in three retros over six weeks and only one action item from those retros has been completed", I realised I'd been undercounting how often we punted on the same thing. It was uncomfortable, and it was the most useful single data point I'd gotten about my team in a year.
What this looks like in practice (Kollabe)
I work on Kollabe, so take this with the appropriate grain of salt. The patterns generalise; if your tool of choice does these differently, swap in the equivalent.
Action items live with the retro that produced them. Each has an owner, a due date, and a status. They show up in the next retro before the team starts on new ones.
Every Monday morning, anyone with open action items assigned to them gets a single email summarising what's still open. Not a Slack ping in a channel where it scrolls past lunch. A direct email at the start of the week, addressed to one person.
If you're on a paid plan, the team also gets a weekly insights report every Monday. Three things in it actually matter for action items: completion rate (with the top overdue items by name), recurring themes flagged across multiple retros, and a team health score that includes follow-through and blocker persistence. When the score drops, it's almost always because the team is generating action items faster than it's closing them. That's a leadership signal, not a process complaint.
For the action items that are real shippable work, one click pushes them into Jira, GitHub Projects, or Linear, with a link back to the retro item. The point isn't the specific product. The point is the loop: action item, owner, weekly nudge, next retro shows the open ones, AI catches when the same theme keeps reappearing.
When the "everything in Jira" approach actually works
There's one case where Jira-only is fine: very small teams (3-5 engineers, no PMs, strong self-driving culture). They don't need a separate place for retro action items because they have so few moving pieces that the items don't get lost. The whole team holds the list in their heads.
If that's you, the rest of this post doesn't apply. Once your team gets above seven people, or you add a layer of PMs and stakeholders, the Jira-only pattern starts breaking. You'll feel it within a quarter, usually as the same complaint coming up in three retros in a row while everyone insists "we're working on it".
A practical rule of thumb
When the team agrees on an action item, ask one question before deciding where it lives:
If we don't do this, who's disappointed?
If the answer is "a customer" or "the PM" or "the company", it's a Jira ticket. If the answer is "us" or "future-us" or "the next retro", it stays in the retro tool with an owner, a due date, and a Monday reminder.
One question, no debate, routes about 90% of action items correctly. The other 10% is borderline and you'll argue about it for thirty seconds, which is the right amount of time to argue about anything in a retro.
Closing
Retros are cheap to run and expensive to ignore. The format you pick for the conversation matters less than where the action items end up afterward. If they don't have a home that nudges the assignee, persists across sprints, and surfaces patterns when the same thing keeps coming up, you're paying for the meeting and not collecting the dividend.
If you want a setup that does the nudging and the pattern detection out of the box, Kollabe's retrospectives tool handles it on the free plan, with weekly insights reports on Premium. Or steal the workflow and apply it to whatever you're already using. The "who's disappointed" rule is free.
Top comments (0)