Half your backlog is one-line tickets nobody has had time to think about yet. They are not blocked, they are not ready either — they are just sitting there, costing a grooming meeting every fortnight.
What it does
- Drag a ticket into your analyze status, and the AI posts a breakdown grounded in your actual repository.
- Comment back to challenge or refine it, and it answers in the same thread.
- Transition it to your build status, and it opens a pull request.
- It listens to the whole Jira event stream — issues, comments, sprints, versions, worklogs — not just one board.
What it will not do
It never transitions your tickets, merges pull requests, or closes issues. Status changes stay a human decision, which also means the automation can never quietly bypass whatever workflow rules your project has.
Why the whole event stream matters
Most Jira integrations bind to a single board and a single transition. This one subscribes to the event stream, so a comment on a ticket in a different project still reaches it. The webhook itself is only a doorbell — every run re-fetches the ticket from the Jira API before it does anything, so a duplicated or missed event cannot put the agent out of sync with reality.
Setup takes about five minutes
Clone the repo, run ./setup.sh, pick Jira, and answer a few questions — your IDs, your tokens, your conventions. The installer copies the recipe into your repository, sets your secrets, and prints whatever manual steps are left with your real values already filled in. No server to host, no database to run, nothing to pay for beyond the AI you already use.
Honest status: beta. It is built and smoke-tested, and it carries a live-fire checklist in its README that I am working through one tool at a time. Jira is the most configurable tracker in the series, so your status names and screens are the thing most likely to need a second pass. If you hit an edge, open an issue — that is exactly what the beta label is asking for.
The recipe is MIT-licensed and open source: ai-automations. It is one of 35 — see the series overview for the full list and the rules every recipe follows. If your tool is not on the list, name it and I will build the automation for it, free.
FAQ
Will it transition my tickets?
No. It never transitions, merges or closes. Status changes stay a human decision, so the automation cannot bypass your project's workflow rules.
Does it only listen to one board?
No. It subscribes to the Jira event stream — issues, comments, sprints, versions, worklogs — so a comment on a ticket in another project still reaches it.
Our status names are custom. Does that matter?
You tell it which statuses mean analyze and build. Jira is the most configurable tracker in the series, so those names are the thing most likely to need a second pass.
More in this series: Basecamp · Slack · all 35 automations
Working on something similar?
If you are wiring AI into the tools your team already uses, I am happy to look at it with you. Thirty minutes, no deck — bring the workflow that costs your team the most time and we will work out whether it is automatable. Get in touch.