Jira Bulk Change: Edit Many Work Items at Once
Short answer: In Jira Cloud, search for the work items you want, then open More actions (•••) > Bulk change all work items. A four-step wizard lets you edit fields, transition, move, delete, or watch up to 1,000 work items in one go. You need the global Make bulk changes permission plus the normal permissions in each space, and there is no undo, so check your search before you start.
Bulk change is one of those Jira features people use a few times a year: closing out an old sprint, reassigning a leaver's work, fixing labels after an import, setting the missing resolution that keeps reports wrong. This guide walks through the native wizard, the JQL that makes it safe, the limits that trip people up, and what to do when the people who need bulk edits shouldn't be given the global permission.
What bulk change can do
Jira's bulk change works on the results of a search. From those results you pick one operation:
| Operation | What it does | Typical use |
|---|---|---|
| Edit | Change fields on all selected work items | Set a fix version, add labels, change priority or assignee |
| Transition | Move work items through the workflow, filling any required fields | Close a batch as Done with a resolution |
| Move | Move work items to another space or work type | Reorganise after a team change |
| Delete | Delete the work items | Remove test or duplicate items |
| Watch / Stop watching | Add or remove yourself as a watcher | Follow a set of work items for a release |
Which fields you can edit depends on the work items you selected. If they come from spaces with different field configurations, Jira only offers the fields they have in common.
How to bulk change work items in Jira Cloud
- Go to Search and select View all work items.
- Filter the list to the work items you want. Switching to JQL is the most reliable way to do this (see the next section).
- Select More actions (•••) > Bulk change all n work items.
- Choose work items. Every result is ticked. Untick anything you want to leave out, then select Next.
- Choose operation. Pick Edit, Transition, Move, Delete, or Watch, then Next.
- Operation details. Set the new values. For Edit, tick each field you want to change and give it a value. For Transition, pick the transition and fill in any fields it requires, such as the resolution.
- Decide on notifications. Untick Send mail for this update if you don't want everyone involved to get an email for every work item.
- Confirmation. Read the summary and select Confirm. Jira shows a progress page while it works through the items.
JQL to pick the right work items
The search is the most important part of a bulk change, because the wizard changes everything the search returns. A few patterns that come up often:
project = SUP AND statusCategory = Done AND resolution is EMPTY
Done work items with no resolution. These are the reason many reports and dashboards miscount closed work; bulk edit the resolution to fix them.
sprint in closedSprints() AND statusCategory != Done
Work left over in sprints that are already closed, ready to move to the backlog or a new sprint.
project = WEB AND updated < -90d AND statusCategory != Done
Open work nobody has touched in 90 days, a good candidate for a clean-up transition.
labels = legacy-import AND priority is EMPTY
Imported items still missing a priority.
Before you run a bulk change, read the result count and open a few results. If the number surprises you, the query is wrong. Saving the query as a filter also leaves you a record of exactly which work items were changed.
Limits to know before you start
Atlassian's documentation lists a few rules that explain most "why can't I do this" moments:
- You need the global Make bulk changes permission. Without it, the bulk change option is missing from the menu. On top of that you need the usual permission for the change in every space involved, such as Move work items to move them.
- Up to 1,000 work items at a time. A larger search has to be split, for example by space or by created date.
- Transitions go one workflow at a time. If the selected work items use different workflows, Jira groups them and you transition one group at a time. Only one bulk transition can run at a time.
- Moving can lose data. Fields that don't exist in the target space or work type are dropped.
- There is no undo. The history of each work item shows what changed, but reversing a bad bulk change means another bulk change, if the old values are even known.
The permission is the one that hurts most in practice. Admins are often careful with it, because one bulk change can touch a thousand work items across every space the person can edit. That leaves team leads and support staff asking an admin every time they need to reassign or relabel a batch of work.
Bulk changes without the global permission
Script Toolkit for Jira includes seven ready-made bulk tools for exactly that situation:
| Tool | What it does |
|---|---|
| Bulk Transition | Moves work items to a status, using whichever transition each one has available |
| Bulk Set Resolution | Sets the resolution on work items closed without one |
| Bulk Assign | Assigns work items to one person, or unassigns them |
| Bulk Add Comment | Posts the same comment on every matching work item |
| Bulk Edit Labels | Adds and removes labels, leaving other labels in place |
| Bulk Set Priority | Sets the priority on many work items at once |
| Copy Custom Field Values | Copies one custom field into another of the same type |
An admin decides who can use each tool under Jira settings > Apps > Script Toolkit > Tools: nobody (the default), admins only, admins and chosen groups, or everyone. So you can open Bulk Assign and Bulk Edit Labels to your team leads group without handing anyone a site-wide bulk permission.
People open Apps > Script Toolkit Tools, pick a tool, type a JQL query (it suggests fields and values and flags invalid JQL as you type), and run it on up to 5,000 work items per run. Two details make this safe to hand out:
- Tools run with the person's own Jira permissions. Access to a tool grants no new rights. If someone can't edit a work item, that item fails with an error instead of changing silently.
- Every item gets a result. Progress is shown as the tool runs, and failed items say why.
Like the native wizard, these changes can't be undone, so the same habit applies: check the match count first. The tools don't move or delete work items; for those, use Jira's own bulk change. The tools guide covers access and limits, and the launch post shows what else the app does.
Repeat bulk updates with Automation
If the same bulk change keeps coming back, such as "every Monday, set the resolution on Done items that have none", don't run it by hand. Use Jira Automation:
- In Space settings > Automation (or global automation for several spaces), create a rule with the Scheduled trigger.
- Turn on the option to run a JQL search and act on each work item it finds, and paste your query.
- Add an action such as Edit work item, Transition work item or Assign work item.
- Turn the rule on and check its audit log after the first run.
Automation rules count toward your plan's automation usage, so very frequent rules over large searches are worth a second look. For logic a rule can't express, a Script Toolkit scheduled job runs your own JavaScript on a cron schedule.
A safe bulk change checklist
- Write the JQL first, read the count, and open a few results.
- Save the query as a filter so you know exactly what was changed.
- Turn off email if the change is housekeeping that nobody needs to hear about.
- For transitions, check which workflows are involved and what fields each transition requires.
- Split anything over 1,000 work items (or 5,000 with Script Toolkit) into smaller searches.
- Afterwards, check a few work items and the reports that depend on them. If you track flow metrics such as time in status, a mass transition will show up there, so note the date. Our guide to Jira reporting for product managers covers which reports are most affected by missing resolutions and stale statuses, and the Jira reporting dashboards setup shows how to keep an eye on them.
Frequently asked questions
How do I bulk edit in Jira Cloud?
Search for the work items, then select More actions (•••) > Bulk change all work items, choose Edit, tick the fields to change, give them values and confirm. You need the global Make bulk changes permission.
Why can't I see the bulk change option?
You probably don't have the global Make bulk changes permission. Ask a Jira admin to grant it, or to open a bulk tool to your group in an app such as Script Toolkit for Jira.
How many work items can I bulk change at once?
Up to 1,000 work items in one bulk change in Jira Cloud. Split larger searches into batches. Script Toolkit's tools run on up to 5,000 work items per run.
Can I undo a bulk change in Jira?
No. Each work item's history records what changed, but there is no button to reverse a bulk change. Save the search as a filter and check the result count before you confirm.
How do I bulk delete work items in Jira?
Use the same wizard and choose Delete. You need the Delete work items permission in each space as well as the global bulk permission. Deleted work items are gone for good, so consider transitioning them to a closed status instead.
Can I stop Jira from emailing everyone during a bulk change?
Yes. In the operation details step, untick Send mail for this update.
Try it
Next time someone asks you to "just close all of these", start with the JQL, then the bulk change wizard. If the people who need bulk edits shouldn't get the global permission, install Script Toolkit for Jira, free on the Atlassian Marketplace, and open the tools they need to their group. The tools guide takes a few minutes to set up.
Top comments (0)