Move tasks to the next stage
A project's tasks sit in stages, such as Ideas, Building and Dev, with a step between each pair. Some steps run by themselves. Others wait for someone to press them: Start sends ideas to be built, Merge merges finished work into the integration branch, and Move to a stage sends work on to a later stage. You can press a step for one task or many at once. Releases into Production work differently; see Release to production.
Who can do this: whoever the project's pipeline lets press that step. If you may not, the bar doesn't offer it.
-
In the sidebar, select Tasks, then the project. The stage strip sits under the top line, with one section per stage below it.
-
Select the stage the tasks are in, on the strip or by scrolling to its section.
-
Tick the tasks to move: select ⋯ at the end of a row, then Select.
Tick tasks from one stage only: the bar offers a step only when every ticked task is in the same stage.
-
In the bar at the bottom, select the step's button with the count, such as Start 3, Merge 2 or Move to Staging 5. It sends at once, with no confirmation.
-
Read the bar's result, such as Started 3, Merging 2 or Moved 5. A step that holds some of them, for example for approvals or a freeze, adds how many are waiting; tasks it turned down are counted as refused.
-
Watch the tasks leave the stage. Started tasks queue and run; merged ones reach the next stage once their pull requests merge.
When the step's button is greyed out, hover it for why, such as At most 1000 at once. A step waiting on something shows a chip on the strip, such as 0/2 approvals or Frozen; hover it for every reason. If the step needs approvals, someone who may approve finishes the move: see Approve or reject tasks waiting at a step.
Related
- How tasks work: the states a task moves through as it is started, merged and finished.
- Task board › The pipeline: the stage strip and every button on the selection bar.
- Set up a project's pipeline: who may press each step, and which steps run by themselves.