Jira

Our verdict on Jira

We have not reviewed Jira as a product, and we won't pretend to. What we can speak to is the work around it. Getting decisions out of meetings and into tickets was slow, manual and easy to get wrong. So one of our TPMs built an AI tool that does that step for him, and Jira stayed in place as the system of record.

If you are searching "Jira review," this page shows how one team uses Jira with AI in 2026. It doesn't cover Jira's features or pricing, because we never tested them on the show.

What we built with Jira

RADAR (April 2026). Matias Singer joined our team as a TPM. Two months before Episode 39, he started building with Claude and OpenAI Codex. RADAR began as a tool for his own job, and now everyone at the company has access to it. It does four things:

• Boards: each project's open, in-progress and done tickets, laid out like the boards in Jira, with internal projects from teams like social, marketing and IT.
• Analytics: charts on top of the boards, because, in Matias's words, the team was "kind of bored to see just a doc and words."
• Transcript to tickets: paste a standup transcript, even one in Spanish, and RADAR suggests action items as tickets to create in Jira.
• Weekly business review: upload one or more meeting transcripts and it drafts the WBR report, with an overview per project and upcoming priorities, which you can edit.

How we use Jira

1. Record the standup. Matias records the daily engineering standup with Granola (Episode 39, at 04:29).
2. Paste the transcript into RADAR. It reads the conversation and suggests a set of new action items. In the demo it found five.
3. Review before anything is created. Open each suggested ticket, fix the title, assign it to someone on the project, and deselect anything that isn't really a ticket.
4. Push the approved tickets to Jira. Only the ones you selected get created on the board.
5. Check boards and analytics in one place. You see every project's status without opening each Jira board.
6. Roll the week up. Select the week's transcripts to get a WBR draft, then edit out anything that isn't important. Matias said it is "not perfect" yet.

Like, I think what's key here is it doesn't automatically push them to Jira. It lets you you know, not everything should be pushed to Jira.

— Sam Nadler, Episode 39

Where Jira falls short

• Turning meetings into tickets by hand. Matias described typing while presenting, mishearing developers, and delays because a ticket wasn't raised in time. That is the job RADAR now does.
• Status updates as text. Weekly reviews built from docs and words didn't hold attention, which is why RADAR puts charts on top of the boards.
• Too much process for some teams. Adir Ben-Yehuda of Autonomy AI said that, once customers start using his product, they open fewer tasks in Jira. He said many people don't want to manage tasks in a cumbersome tool anymore; they just want to act on them (Episode 43, at 16:47). He saw the same pull away from Figma.
• The AI layer still needs a person. Matias called the ticket suggestions "pretty accurate," but said someone still needs to oversee them.

Delays were made because I did not raise the ticket at the time it was necessary to. So all this helped me a lot. It reduced my time that were four hours to minutes.

— Matias Singer, Episode 39

Next on Matias's list: a direct Granola integration so nobody has to paste transcripts, a stored transcript history, and a pre-meeting section that shows each team where it left off the day before.

Episodes featuring Jira

• Episode 39: Matias Singer demos RADAR, and Sam and Jordan explain how non-technical teams started building their own tools on top of systems like Jira, Granola and Slack.
• Episode 43: Adir Ben-Yehuda on why teams using Autonomy AI open fewer Jira tasks.

FAQ

Can AI create Jira tickets from meeting notes?

Yes. Our TPM Matias Singer built RADAR, which takes a pasted standup transcript, suggests tickets, and lets him edit, assign and choose which ones get created in Jira. He said it cut a four-hour task to minutes.

Should AI push tickets to Jira automatically?

We don't think so. Sam's point in Episode 39 was that not everything said in a meeting should become a ticket, so RADAR suggests tickets and a person approves them.

Are teams moving away from Jira?

Autonomy AI's Adir Ben-Yehuda said in May 2026 that customers using his product open fewer tasks in Jira and that many people no longer want to manage tasks in a cumbersome tool. That is one guest's view, not something we measured.

Do you need to be an engineer to build tools on top of Jira?

No. Matias is a technical program manager who had started building with Claude and Codex two months before he demoed RADAR. It is now available to everyone at our company.