Blog ·

Bulk operations in Jira: edit, move and delete in one pass

Bulk operations in Jira Cloud let you change many work items in one pass: edit their fields, move them through the workflow, move them to another space, change their work type, delete them, or watch and unwatch them. You start from a list of items (the List view, the backlog, a board, or the All work search), select the items, and pick the operation. Atlassian's documentation puts the ceiling for bulk edits and bulk deletes at 1,000 work items at a time, and every operation checks your permissions on every selected item. This guide walks through each operation as of October 2026, then covers the part most guides skip: what to do when you find yourself running the same bulk change every week.

Jira now calls issues "work items" and projects "spaces" in most of its interface, so the menu names below use the new words.

The bulk operations at a glance #

Operation What it changes Where you can start it Stated limit
Edit work items Field values (assignee, labels, priority, sprint, and more) List, backlog, board, All work search Up to 1,000 items
Change status Workflow status, through a transition List, backlog, board, All work search Not stated separately
Move work items The space, and the work type with it Backlog, board, List, All work search Not stated separately
Change work type Work type, inside the same space Backlog, board, List Not stated separately
Delete work items Removes the items for good List, backlog, board, All work search Up to 1,000 items
Watch / stop watching Your own notifications List, backlog, board Not stated separately

The backlog and board entry points only exist in software spaces. In a business space, start from the List view or from search.

How to select the items #

Every bulk operation starts with a selection, and the selection is where most mistakes happen.

  1. Build the list with a filter, not by eye. In the All work search, write a JQL query that returns exactly the items you mean, for example project = OPS AND status = "To Do" AND updated < -90d. A saved filter means you can run the same selection again next time.
  2. Check the count before you act. If the query returns more than 1,000 items, narrow it (by date range, by type) and run the operation in batches.
  3. Select the items. In the List view and the backlog, use the checkboxes, hold Ctrl (Windows) or Command (Mac) to add single items, or hold Shift to select a run of adjacent items. On a board, use Ctrl/Command or Shift.
  4. Open the operation. In the list, a toolbar appears with Edit and Change status. On a board or backlog, right-click or open More actions (•••) on one of the selected items and choose Bulk change. In search, open More actions (•••) and choose Bulk change work items, then tick the items.

Bulk edit fields #

Bulk edit is the operation people reach for most: reassigning a departed colleague's work, adding a label to a set of items, setting a fix version, or clearing a sprint.

From the List view, select the items and choose Edit. A bulk edit sidebar opens with the fields the selected items share. For multi-value fields, Jira offers a choice of what to do with the existing values:

"Replace all" on labels wipes every existing label on every selected item, so use "Add new" unless you mean it. Select Next to see a confirmation screen, then Confirm.

From a board or search, the older bulk change wizard does the same job: choose Edit work items, set the values, decide whether to send email notifications, review, and confirm.

Some fields come with conditions. Atlassian's field table says, for example, that bulk changing versions or components needs the selected items to be in one space, that the field must not be hidden in the field configuration, and that you need edit permission on every item. If a field you expect is missing from the sidebar, one of those conditions is the usual reason.

Bulk change status (transition) #

To move many items through the workflow at once:

  1. Select the items in the List view and choose Change status, pick the status, and submit.
  2. On a board, you can also select several cards and drag them into the target column together.
  3. From the backlog, choose Edit, then Status.

Items on different workflows are handled in groups. When the selected items do not share the same statuses or transitions, Jira opens the bulk edit sidebar and groups items from the same workflow, so you pick a new status for each group. A transition that requires a field (a resolution, a comment) asks for it once and applies it to every item in the batch.

The wizard version from a board or search shows only the workflow actions available to the items you selected. If the transition you want is missing, at least one selected item is in a status that does not offer it; split the selection by status and try again.

Bulk move items to another space #

Moving work items between spaces is a bulk change too: choose Move work items, pick the destination space and work type, fill any fields the destination requires, and confirm.

Three things to check before you move a batch:

Bulk change the work type #

Changing the work type of many items uses the same Move work items step: select the same destination space, choose the new work type, and confirm. It is the route for turning a batch of Tasks into Stories, or Bugs into Tasks, after a process change. The same field and status mapping applies.

Bulk delete #

Deleting is the one bulk operation you cannot take back, and it needs the Delete work items permission, which many teams do not grant to everyone. Atlassian documents a limit of up to 1,000 items per delete from the list, the backlog, the board or search.

Before you delete a batch, consider archiving instead: archived items leave your boards and searches but can be restored. We covered when to archive and how in Archive Jira issues.

Bulk watch and unwatch #

The quietest bulk operation is the one that fixes your inbox. Select the items, open Bulk change, and choose Watch work items or Stop watching work items. It changes only your own notifications, so it is safe to run on a large selection, and it is the fastest way to stop alerts from a project you have left.

Common mistakes with bulk changes #

Mistake What happens How to avoid it
Selecting by eye on a board Items off-screen are left out Build the selection with JQL in search
"Replace all" on a multi-value field Existing values are lost on every item Use "Add new" or "Find and remove"
Sending notifications on a big batch Every watcher gets an email per item Turn notifications off in the wizard where it is offered
Mixing workflows in one transition The transition you want is not offered Split the selection by status or workflow
Deleting when you meant to tidy Items are gone for good Archive instead

When the same bulk change keeps coming back #

A bulk change is a good tool for a one-off: a reorganisation, a departed teammate, a migration. If you run the same bulk change every week or every month, the bulk change is treating a symptom. A few common patterns, and what tends to fix the cause:

Jira Automation can also run some of these edits itself: a scheduled rule with a JQL query can edit or transition the items it finds. That works well for simple, mechanical changes, but each run counts against your automation allowance; we covered how usage is counted in Jira Automation pricing and the ceilings in Jira Cloud automation limits.

Create the routine items correctly in the first place #

For the first three patterns, the fix is to have the recurring items created on a schedule, already filled in. In Recurring Work Items for Jira, a rule stores the work type, summary, description, due date, assignee, reporter, priority, labels, custom fields and an ordered list of subtasks, and creates the item on the schedule you choose: daily, weekly, monthly or quarterly, with working-day and holiday handling. The text fields take tokens, so a monthly rule produces "Access review: October 2026" rather than a copy that still says September. The token vocabulary is on the tokens page, and the editor shows the next runs before you save. The app is turned on per space, so one team's rules never land on another team's board.

For the fourth pattern, a recurring "close out stale items" ticket that carries the JQL in its description puts the bulk transition on someone's board at the right time, with the exact query ready to paste. Our Jira hygiene guide lists the checks worth running and a filter for each.

When the manual way is enough #

Bulk operations need no app and no setup, and for most teams they are the right tool most of the time. Stay with the bulk change wizard when:

Reach for a schedule only when you notice the same selection, the same fields and the same day coming round again.

Frequently asked questions #

How many items can I bulk change at once in Jira Cloud? Atlassian documents up to 1,000 work items for bulk edit and bulk delete. For larger sets, narrow the JQL and run the change in batches.

Why is the Bulk change option missing? The selection has to come from a list, backlog, board or search, and you need the relevant permission on every selected item. The board and backlog entry points exist only in software spaces.

Can I undo a bulk change? Not with a single button. An edit or transition can be reversed with another bulk change on the same filter, which is one more reason to build the selection with a saved filter. A delete cannot be reversed.

Can I bulk clone items? Not from the bulk change menu. Our bulk clone guide covers the Automation and CSV routes, and Jira bulk create covers creating many new items at once.