Bulk Operations — Update Multiple Items at Once
When you're managing a sprint's worth of work, you don't want to click through 30 items one by one. Bulk operations let you update multiple items simultaneously — changing status, priority, assignees, or sprint for an entire selection in seconds.
Selecting Items
Selecting Individual Items
Click the checkbox on the left side of any item row in table view to select it. You can select items across different groups in the same view.
Selecting a Group
Click the group header checkbox to select all items in that group at once. If a group has a mix of selected and unselected items, the header shows an indeterminate state — click again to select all.
Selecting All Items
Use Cmd+A (Mac) or Ctrl+A (Windows/Linux) to select all visible items in the current view.
The Bulk Action Bar
When one or more items are selected, a floating action bar appears at the bottom of the screen. It shows how many items are selected and lists the available bulk operations.
Click anywhere outside the selection to deselect and dismiss the bar.
Available Bulk Operations
Update Status
Change the status of all selected items to a single target status. Useful after a sprint review to mark completed items as Done, or after a deployment to move items from Pending Production to Production Deployed.
Update Priority
Set priority across all selected items. Use this after sprint planning to align priorities across a sprint's items, or to bulk-update a set of backlog items when priorities shift.
Assign Sprint
Move items to a sprint in bulk. This is the primary tool for sprint planning — select the stories and tasks you want in the next sprint and assign them all at once.
Tip: Use bulk sprint assignment after a planning session. Filter the Estimation or Ready view to the items you agreed to pull in, select them all, and assign the sprint in one action. What used to take 20 minutes now takes 20 seconds.
Update Assignees
Assign one or more team members to all selected items. This is additive by default — it adds the selected assignees without removing existing ones. Use the "Replace" option to replace existing assignees entirely.
Update Stage
Change the deployment stage (Predev, Dev, Production) for all selected tasks. Useful when a batch of tasks moves together through the deployment pipeline.
Duplicate
Create copies of all selected items. Duplicates are created in the same board and group with "(Copy)" appended to the title. Useful for repeating work patterns, template stories, or setting up a new sprint based on an existing one.
Duplicates copy:
- Title and description
- Status, priority, assignees
- Custom fields
- Estimated hours
Duplicates do not copy:
- Comments and updates
- Time logs
- Activity history
- Dependencies
Archive
Archive all selected items. Archived items are hidden from active views but remain searchable. Use archiving to clean up completed or cancelled work without permanently deleting it.
Tip: Archive a sprint's worth of Done items at the end of each sprint to keep the board clean. Archived items are still visible in the Archive view and are included in reporting.
Delete
Permanently remove all selected items. A confirmation dialog lists the items to be deleted and requires explicit confirmation.
Deletion is irreversible. Consider archiving instead. Delete is appropriate for accidentally created items or test data.
Merge (Feature Requests boards only)
Combine duplicate feature requests into a single item. Select the duplicates, choose Merge, and designate one item as the "primary" — all votes, comments, and linked customer accounts from the secondary items are consolidated into the primary.
This keeps your Feature Requests board clean and ensures all customer input is captured in one place, rather than scattered across duplicates.
Duplicate Group
Beyond duplicating individual items, you can duplicate an entire group at once. Click the "..." menu on any group header and select Duplicate Group. All items in the group are duplicated in one action.
Common use cases:
- Duplicating a standard sprint template for a new sprint
- Creating a parallel track with the same structure as an existing one
- Setting up a new board structure based on a working pattern
Permissions
Bulk operations respect the same permissions as individual item edits.
- Viewers cannot use bulk operations
- Members can bulk-edit items they have access to
- Admins can bulk-edit all items on the board, including archive and delete
If you select items you don't have permission to edit, those items are skipped. The operation applies to the items you do have permission to change, and you'll see a summary of what was updated vs. skipped.
Board admins can configure who has access via Board Settings → Members (open your board → click the gear icon → Members tab). Role assignments there determine which bulk operations each team member can perform.
Tips for Using Bulk Operations Effectively
Sprint planning: Filter to the Ready pipeline view → select the stories you're pulling in → bulk assign to the sprint. Then expand to tasks and do the same.
Post-deploy cleanup: After a production deployment, filter to tasks in Pending Production Deploy → select all → bulk update to Production Deployed.
Priority alignment: After a stakeholder review reprioritizes a product area, filter to the affected epic → select all stories → bulk update priority.
Sprint retrospective: At sprint end, filter to Done items in the current sprint → select all → bulk archive to clear the board for the next sprint.
Tip: Combine bulk operations with views. Set up a saved view for "Current sprint, In Review" then bulk-update all those items to the next status after a code review session. Views + bulk operations are the fastest way to manage high-volume boards.