Overview
Bulk operations let you update multiple issues in one action from the list view. Select two or more issues to activate the batch actions panel.
Selecting Issues
In the list view, check the checkbox to the left of each issue to modify. Check the header checkbox to select everything on the current page.
The number of selected issues appears in the actions panel at the bottom of the page.
Available Actions
| Action | Description |
|---|---|
| Set status | Updates the status of the selected issues. A development status applies to tasks and bugs, a writing status to specifications and plans |
| Assign | Reassigns all selected to a user or team |
| Set release | Moves selected issues to a different release. Issues that are in a capability are skipped and counted in the message: they follow the release of their capability |
| Set cycle | Reassigns selected to a different cycle. A message then gives the load of each cycle concerned, before and after (“Cycle 2: 95% → 112%”), and names whoever goes above 100% |
| Add label | Adds a label to all selected issues |
| Set platform | Updates platform for all selected issues |
Common Use Cases
Sprint planning: filter issues for a release, select those that fit into the next cycle, assign them in one action.
Team reassignment: when reorganizing, quickly reassign all issues from a departing developer to another.
Backlog cleanup: select all issues without a release and bulk-assign them to the next planned release.
Status update: at the end of a sprint, mark all completed issues as done in one click.
Points to Note
Bulk operations are irreversible in a single action. Verify your selection before applying. For large selections, use filters to precisely isolate the affected issues before selecting.
The load message is a warning when a cycle or a person goes above 100%. It never blocks the change. The same message follows Add issues on the page of a cycle.