What you need to know
From a 's board, you can act on one task across many projects at once: move them to a stage, skip them, or put a person on them. You tick the tasks first. Before you confirm, the button says how many would be refused. Each task is then done, or refused, on its own.
Before you start
- The group must be open, with the projects you want in it.
- To move or skip, you need to be a contributor, a department manager or a company administrator in the department. An executive with read-only reach does not reach these acts. To assign, you need to be a department manager or a company administrator.
What to do
Before you do this
A move or a skip changes every ticked task at once, on each project, and each change goes into that task's history. There is no undo for the batch: to put a task back, move it again, or bring it back from its project's page, one by one.- Open the group's board. Select the name on the card of the task you want.
- Tick the rows to act on, or tick the box in the header to select all. Nothing is ticked when the screen opens.
- Choose what to do:
- To move, choose a stage in Move to. If that stage asks for an , choose it in Ending. Then select the Move button.
- To skip, select the Skip button.
- To assign, select the Assign button, tick one person, and pick their role if they have more than one. Then select the button at the bottom of the dialog. The person goes on exactly the ticked tasks: unlike Assign on one task, it lists no other tasks of the job role.
- Read the question. It names the group, the task and how many are ticked, and lists what would be refused, one line per reason, with how many it covers. Select the button to confirm, or Cancel.
Each button gives a forecast. As soon as you tick rows, and again when you change the stage or the person, Workflow checks each ticked task as if you acted on it alone. Nothing changes yet. The button then shows the result, for example "Move 4 · 1 will be refused", or "Skip 3 · all 3 will be refused" when none would go through.
The forecast is not a promise: each task is checked again when you confirm. Common reasons a task is refused:
- Its project's template has no stage of that name: “This project's template has no stage named "Filed".”
- Your company has switched on the rule that work must follow the transitions, and the template does not allow that move: “The template does not allow that move from this stage.” Ask tech whether your company uses this rule.
- You are not a manager and not on the task, for a skip.
- The task needs an approval and you may not give it, for a skip. Only a person who may give every approval it needs may skip it.
- The person cannot work on that project, for an assign.
- Someone changed the task since the screen loaded.
Confirm it worked
One message at the bottom right says how many went through, for example "Moved 3 of 4 to Filed.". Each reason for a refusal has its own message, with how many tasks it covers. The tasks that went through are unticked; the refused ones stay ticked, so you can fix the cause and try them again.
If it did not work
- A message says “This property was deleted on 10/06/2026; its work is paused until it is restored.” The work's property or engagement was deleted, and nobody can change its work until the record is restored. See A project or its tasks disappeared.
- There are no tick boxes: the group is closed, or your role allows none of the three. A closed group says “This group is closed. Reopen it to change its members or act on its tasks.”
- The Move button stays grayed out: choose a stage in Move to, and an ending in Ending if it shows.
- A skip was refused: see Skip was refused.
- A move was refused: see I can't move a task to the stage I want.
Good to know
A skipped task leaves the group's board. To bring one back, open its project's page. See Skip a task, and bring it back.