Set only what you want to change — anything left on keep current or empty is untouched.
Placeholders are filled for each ticket. A block a ticket already has is not added twice.
Create tickets from a plan — modules, Epics & User Stories
Draft the plan from a scope document— the AI reads it and writes modules, cross-module work, Epics and User Stories; nothing is created until you press Create
My tickets
Loading…
Board
Drag a card to another column to change its status — or use its ⋯ menu
Ticket pools
Loading…
Never two on the same repo.
Added ahead of each ticket's own instructions when the pool runs; the tickets themselves are not changed.
Run order
Drag a row, or use ↑ ↓, to change the order.
Add tickets from the board
Loading…
Tick the tickets you want and press Run selected — they run in the order shown,
whatever their current status. New ticket files one straight into Jira and
Edit changes an existing one and Delete removes it (after you confirm) — the same as
agentos ticket create|update|delete. Watch progress live on the Dashboard
and the log on Run & Logs.
A pool keeps up to 50 tickets together — a module's tickets, say — in the order
you choose, with instructions for all of them; Run starts them as one batch,
several at a time (same as agentos pool run NAME).