Bulk actions on tasks
Change many tasks at once — and what still fires when you do.
Busy season generates the same edit fifty times. Bulk actions do it once.
Where to find it
Tick the checkbox on each task you want. The bulk action bar appears once something is selected.
The usual pattern
Filter first, then select.
Filtering down to exactly the set you mean, then selecting all of it, is both faster and safer than scrolling a long list ticking boxes — and it means the set you're acting on is one you can describe.
What you can change
Reassign, change status, change office, add a tag, and reschedule.
Adding a tag in bulk only adds. Tasks that already carry the tag are left alone rather than being toggled off, so re-running the same bulk tag is harmless. There's no bulk remove — to strip a tag from many tasks, either remove it individually or merge the tag into another if you're retiring it entirely.
Automations still fire
This is the part worth understanding.
A bulk status change is not a quiet database update. It goes through the same path a single edit does, so the same events fire — automations run, notifications go out, and anything downstream of a status change happens for every task in the selection.
That's usually what you want: moving forty returns to Ready for review should notify the reviewer. But it means a bulk change across two hundred tasks does two hundred tasks' worth of downstream work. Check what's wired to a status before you move a large selection into it.
Notes and limits
- The selection clears after the action runs.
- Bulk edits respect permissions — tasks you can't edit aren't changed.
- A bulk status change into a Complete-role status closes those tasks out and they leave the active view.
- Single-row inline edits go through the same path, so a one-task change behaves identically to a bulk change of one.