Half your backlog is one-line tickets nobody has had time to think about yet.
What it does
- Drag a ticket into your "analyze" status → the AI posts a breakdown grounded in your actual repo
- Comment back to challenge or refine it → it answers in the same thread
- Transition it to your "build" status → it opens a pull request
- It listens to the whole Jira event stream — issues, comments, sprints, versions, worklogs — not just one board
What it does not do
It never transitions your tickets, merges PRs or closes issues. Status changes stay a human decision.
Honest note: this recipe is beta — built and smoke-tested, still waiting on live-fire use. Tell me what breaks.
Setup
clone → ./setup.sh → pick Jira → answer a few questions
~5 minutes. No server, no database, free.
Get it
The recipe is open source: github.com/akshaypatel-ai/ai-automations
This is one of 30+ automations in the series — the full write-up lives on my site.
