Guide
How to assign a Jira ticket to an AI agent
To assign a Jira ticket to an AI agent like AoTwin, write three things in the ticket (which screen it’s on, what should change, and what done looks like), then pick AoTwin as the assignee. It replies within seconds and comes back with a pull request for your engineers to approve, or with the reason it stopped.
Published 31 October 2026
Before your first ticket: a one-time setup
An engineer on your team connects your Jira workspace and the repositories AoTwin may work in, once. AoTwin only works in the repositories you connect.
The three lines every ticket needs
A ticket an AI coding agent can take says:
Where: which screen or page it’s on.
What should change: the change, in plain words.
What done looks like: how you’ll know it’s right.
A screenshot helps: AoTwin reads it.
Example ticket
Sidebar covers page content on phones
On phones the sidebar covers the whole page. Make it slide away so the page is readable, and keep it open on wider screens.
This one names the place (the sidebar, on phones), the change (slide away) and what done looks like (page readable on phones, sidebar still open on wider screens).
The steps in Jira
Open the ticket and check it has the three lines.
Change the assignee to AoTwin, the same way you’d assign a teammate.
Watch for the reply. AoTwin answers on the ticket within seconds (“Got it — I’ll take a look shortly.”) and moves the ticket to In Progress.
Answer any question on the ticket. If something is missing, AoTwin asks there instead of guessing. Add the missing part and assign it back.
Hand the result to your engineers. The change comes back linked to the ticket for review.
You can also file and assign tickets from Claude, Claude Code or Cursor through AoTwin’s MCP connector. Filing a ticket never starts AoTwin; assigning it does.
What a good reply looks like
Every ticket comes back one of three ways:
- Ready for review. “Done — ready for your engineers to review. It passed your team’s checks.” followed by a link to the pull request.
- Ready, with a warning on top. For example: “Done, but worth a careful look: this changes who can edit a staff member’s role, so it touches permissions. I opened it as a draft.”
- Back to you, with the reason. For example: “This one needs you — I can’t tell what done looks like.” or “Got stuck on this one — your team’s checks kept failing. I’ve assigned it back to you.”
What stays with your team
- AoTwin never merges or releases. Merging and closing pull requests are blocked.
- It never pushes to your default branch, and never force-pushes.
- One ticket, one change, on its own branch named after the ticket.
- If your checks fail, it tries once more with the error in hand. If they fail again, the ticket comes back to you.
- Instructions hidden inside a ticket don’t change its rules.
FAQ
What happens if my Jira ticket is vague?
It comes back to you with what’s missing. AoTwin doesn’t guess. Add the missing part and assign it back.
Which Jira tickets should I assign first?
Everyday work: copy changes, styling and layout fixes, a new column, a filter, simple create-and-edit screens. Tickets that say what done looks like work best.
Does a returned ticket cost anything?
A ticket AoTwin hands back costs at most one ticket. Every ticket has a cost ceiling.
Does it work with Linear too?
Yes. In Linear you pick AoTwin as the delegate on the issue instead of the assignee.
Does it work on mobile app tickets?
Yes, with a warning. Changes to iPhone or Android app screens always come back as drafts, so an engineer checks them on a device.
Assign your first ticket
Write the three lines, pick AoTwin, and see what comes back. Start free.