The initiative queue
Line up initiatives in the order you want them built. Taiga plans and runs the first, opens a pull request, and starts the next when you merge it.
Add initiatives to a project's queue and put them in the order you want them done. Taiga plans the first, runs it, and opens a pull request; merging that starts the next. One initiative at a time, per project.
The next one is planned after the previous merges rather than when its run finishes, because planning reads the repository as it stands. The queue moves at the speed you review pull requests.
A failed plan or run halts the queue instead of skipping past it. Retry the plan, retry the run, or open a fresh pull request, and it resumes within about half a minute. An initiative blocked by unfinished dependencies waits for you to press Resume.
Taiga does not touch the order. Nothing is added, reordered or promoted automatically. Removing an initiative from the queue, and resuming a stopped one, are recorded in the audit log; both would otherwise leave no trace.
Park joins build, queue and cancel as a fourth state, for work you intend to return to. A parked initiative sorts to the bottom of the backlog and stops offering to plan itself, while its plan, its run and any open pull request stay as they were. Queueing a parked initiative unparks it.
Urgent security fixes run outside the queue, so a queue of features cannot delay a vulnerability fix.