Handing tickets to minions
A minion is an AI teammate you can assign tickets to. You hand work over the same way you would to a person: write on the ticket what needs doing and what “done” looks like. The advice in Writing tickets applies, and acceptance criteria matter most. A minion stops working once it judges that every acceptance criterion is met.
There are two ways to ask:
| Ask in chat | Leave it on the board | |
|---|---|---|
| Best for | One ticket, right now | Several tickets, taken on as the minion frees up |
| Setup | Paste the ticket’s tag into chat | Set the assignee and acceptance criteria, and put the ticket in a sprint |
| When it’s finished | The minion replies in chat | The minion moves the ticket to Review |
To try it out with one ticket, asking in chat is the easiest.
Before you start: add the minion to the project
Section titled “Before you start: add the minion to the project”Only project members can be assigned. A project admin adds the minion in the project’s Members tab (Project members and permissions). A minion that isn’t a member can’t update tickets.
Ask in chat
Section titled “Ask in chat”- Hover over a card and copy its tag with the button in the top right. If the details are open, Chat tag at the top copies it too
- Paste it into a chat with the minion and say what you’d like
Please take care of [task:…]. Once every acceptance criterion is met, set its status to Review.The tag reaches the minion together with the ticket’s title, status, due date and the start of its description. If you want the minion to work through the acceptance criteria, or to update the board when it’s finished, say so, as in the example above.
Leave it on the board
Section titled “Leave it on the board”A ticket assigned to a minion is picked up by that minion, which starts work on its own. Nobody has to prompt it.
However, a minion only picks up tickets that are in a started sprint and whose status is Todo or Doing. If minions started on anything left on the board, they would start on half-written tickets too. Starting a sprint is how a person says “anything in here is ready to go”.
Think of a sprint as a box for the tickets you’re handing over. It has no dates, and stays open until someone clicks Complete. When you’re starting out, keep one sprint started and put the tickets you want to hand over into it — that’s all you need.
The first time
Section titled “The first time”- Open the ticket you want to hand over, choose the minion as Assignee, and write at least one item under Acceptance Criteria. Set Status to Todo
- Create a sprint with + Sprint in the Kanban header. Any name you’ll recognize is fine, such as “Minion work”
- In the ticket’s details, choose the new sprint under Sprint
- Click ▶ Start
If the sprint can’t start, you’ll see which tickets are missing what (an assignee or acceptance criteria). Click one to open it, fill in what’s missing, and click start again.
Once it’s started, the minion picks up the ticket — in about 30 seconds at the earliest — and changes its status to Doing.
After that
Section titled “After that”The sprint stays open, so for each ticket you want to hand over you only need to:
- Set Assignee to the minion and Status to Todo
- Write the Acceptance Criteria
- Choose the started sprint under Sprint in the details
Tickets added after the sprint has started don’t go through the check that runs at start. Remember to set the assignee and acceptance criteria yourself: without an assignee nobody picks the ticket up, and without acceptance criteria the minion can’t tell when it’s finished.
While the minion works
Section titled “While the minion works”A minion that picks up a ticket receives its title, description, priority, due date and acceptance criteria, along with the project’s context and member list. The work runs in its own terminal session, which you can watch from the workspace’s terminal.
When the minion isn’t sure how to proceed, it doesn’t guess. It leaves the ticket in Doing and asks in a project thread. Reply in the thread.
Checking the result
Section titled “Checking the result”A minion that picked up a ticket from the board only changes its status from Todo → Doing (when it starts) and Doing → Review (when every acceptance criterion is met). It never moves a ticket to Done. Checking the result and moving it to Done is the job of whoever asked for the work.
Nothing notifies you when a ticket reaches Review. While minions are working for you, check the board’s Review column often.
If something needs fixing, add it to the description or acceptance criteria and move the ticket back to Todo. The minion picks it up again and works on the fix.
Custom fields and minions
Section titled “Custom fields and minions”Minions can read and write the values of custom fields. You can ask one to “fill in the estimate for this ticket”.
They can’t change field definitions (adding axes, changing options). Changing a rating axis silently changes what every ticket’s priority means, so that decision stays with people.
When a minion doesn’t pick up a ticket
Section titled “When a minion doesn’t pick up a ticket”Check these in order:
- Has the sprint been started? A sprint that’s only been created (still
planned) isn’t picked up from - Is the ticket in that sprint? Look at Sprint in the details
- Is the status Todo or Doing? Backlog, Review and Done tickets aren’t picked up. Tickets put into a sprint from the Planning view stay in Backlog, so move them to Todo
- Is the minion the assignee? If the minion has been removed from the project’s members, it won’t pick tickets up even if it’s still the assignee
- Is the minion busy? A minion runs at most two automatic jobs at a time, and shares that limit with workflow runs. It may be waiting for other work to finish. See Multi-Project Assignment
- Is the project archived? Automatic work stops in archived projects
Related
Section titled “Related”- Writing tickets — how to write acceptance criteria
- Board reference — the details of sprints
- Multi-Project Assignment — what to watch for when one minion is assigned to several boards