Bulk Operations
Change many work items at once. Pick a project, tick the items you care about, and set their state, priority, assignee or label in a single action — or archive or delete them together.
Bulk Operations is available on every plan, including Free.
What you can do
- Multi-select work items in a project with checkboxes (or select everything currently listed).
- Set the state on all selected items.
- Set the priority on all selected items.
- Set the assignee on all selected items, or clear it (Unassigned).
- Add a label to all selected items.
- Archive the selected items.
- Delete the selected items permanently.
Getting started
Open the page
- In the workspace sidebar, click Bulk Operations.
- Choose a project from the Select a project… dropdown at the top.
- The project's work items load into a list, with a count in the header row.
📷 Screenshot: The Bulk Operations page with a project selected and its work items listed, each row showing the item key, name, priority and state.
Select the items you want to change
- Optionally narrow the list first with the Filter by name… box — it filters the loaded items on their title as you type.
- Tick individual rows, or tick the checkbox in the header row to select everything currently shown. (If a name filter is applied, the header checkbox selects only the filtered items.)
- As soon as one item is selected, an action bar appears above the list showing how many are selected.
Applying a bulk edit
With items selected, use the dropdowns in the action bar:
| Dropdown | Effect |
|---|---|
| Set state… | Moves every selected item to that state. |
| Set priority… | Sets Urgent / High / Medium / Low / None on every selected item. |
| Set assignee… | Replaces the assignees on every selected item with the person you pick. Choosing Unassigned clears assignees. |
| Add label… | Adds that label to every selected item, keeping labels they already have. |
You can combine several of them — set a state and a priority and add a label — then click Apply. The change is pushed to each item in small batches, and you get a toast when it finishes. If some items could not be updated (for example, you don't have permission on them), the toast tells you how many succeeded and how many failed rather than silently swallowing the errors.
The list refreshes once the update completes.
📷 Screenshot: The bulk action bar with "12 selected", the four dropdowns, and the Apply, Archive and Delete buttons.
Archiving
Click Archive in the action bar and confirm. Archived items leave the active list and can be found in the project's archives.
Important: archiving only works on work items whose state belongs to the Completed or Cancelled group. If any item in your selection is still in Backlog, Todo or In Progress, the whole archive request is rejected and nothing is archived. Move those items to a done/cancelled state first, or deselect them.
Deleting
Click Delete and confirm. This permanently removes the selected work items — there is no undo.
Deleting in bulk requires the Admin role on the project. If you're a project Member, the delete will be refused; archive instead.
Tips
- Use the name filter as a poor man's query: type a keyword, hit the header checkbox to select all matches, then apply the change in one go.
- To move a batch of stale items out of the way, first bulk-set their state to a cancelled state, then bulk-archive them.
- Adding a label is additive, so you can safely tag a batch without disturbing the labels people have already applied.
Limits & good to know
- One project at a time. The page works within the project you select; it can't span projects.
- It loads the project's work items in a single page (up to 1,000). Very large projects may not show everything at once.
- The filter box matches on the item name only, and filters what's already loaded — it isn't a full search.
- You can add a label but not remove one, and setting an assignee replaces the existing assignees rather than adding to them.
- There is no bulk edit for cycle, module, due date or custom fields.
- Edits are applied per item. If a few fail, the rest still go through — the operation is not all-or-nothing (archive is the exception; see above).