JIRA Bulk Change and Import
Editing issues one by one works for small jobs. A release rename that touches two hundred issues would eat an entire day. JIRA solves this with bulk change tools and CSV import. A few clicks update many issues at once, and a spreadsheet creates new issues in bulk.
Layman's View: Relabeling Parcels
A warehouse worker who needs to change the address on fifty parcels would not rewrite each label by hand. A label printer stamps all fifty in one run. Bulk change acts as the label printer for JIRA issues.
Search for issues
|
v
Select the issues to change
|
v
Choose an operation
|
v
Fill in the new values
|
v
Review and confirm
Bulk Change Operations
Operations Available in Bulk Change
| Operation | What It Does | Sample Use |
|---|---|---|
| Edit Issues | Changes field values in every selected issue | Set a new Fix Version on 80 issues |
| Transition Issues | Moves issues through a workflow step | Close all issues from an old sprint |
| Move Issues | Sends issues to another project or issue type | Shift a backlog to a new project |
| Watch or Unwatch | Adds or removes watchers | Add the support lead to key issues |
| Delete Issues | Removes issues permanently | Clean test data from a practice project |
Running a Bulk Edit
- Run a search with JQL or a saved filter.
- Open the tools menu in the results area and choose the bulk change option.
- Tick the issues to change.
- Pick the operation, such as Edit Issues.
- Choose the fields to edit and type the new values.
- Review the summary page and confirm.
JIRA caps the number of issues in one bulk operation. Large jobs run in several batches.
Permissions and Notifications
Users need permission to edit, move, or delete the selected issues. Some operations demand a special bulk change permission. Each changed issue may trigger an email. A big job can flood inboxes, so the bulk screen includes a switch that turns notifications off for the run.
Importing Issues from CSV
CSV files store tables in plain text. Teams import them to create many issues from a planning spreadsheet or to move data from another tool.
A Simple CSV File
Summary,Issue Type,Priority,Assignee,Description Create login page,Story,High,asha,Build email and password form Add password reset,Story,Medium,ravi,Send reset link by email Fix slow search,Bug,High,meena,Search takes ten seconds
Import Steps
- Prepare the spreadsheet with one row per issue and one column per field.
- Save the sheet as a CSV file.
- Open the external system import option in the administration area.
- Choose the file and the target project.
- Map each column to a JIRA field.
- Map text values, such as High, to the matching JIRA values.
- Run the import and read the log for errors.
Exporting Issues
Search results export to CSV or spreadsheet formats. Teams export issues to share status with people outside JIRA, build custom charts, or keep a backup of a filtered set.
Safety Checklist
Before Any Bulk Action
| Step | Reason |
|---|---|
| Test with five issues in a practice project | Mistakes stay small |
| Check the search count against expectations | A wrong filter selects the wrong issues |
| Export a backup of the selected issues | Restoring becomes possible |
| Turn off emails for large runs | Inboxes stay calm |
| Read the final summary before confirming | Deletes cannot be undone |
Common Mistakes
- Importing without mapping text values, which leaves priorities empty.
- Using a date format that JIRA cannot read.
- Running a bulk delete on a filter that returns more issues than expected.
- Importing straight into a live project without a trial run.
Real-World Example
A product manager plans a launch in a spreadsheet with sixty tasks. She saves the file as CSV, maps the columns, and imports the data into a practice project. Everything looks correct, so she repeats the import in the live project. Two days later, the release name changes. A single bulk edit updates the Fix Version on every task.
Summary
Bulk change edits, moves, transitions, and deletes many issues in one pass. CSV import creates issues from a spreadsheet, and export shares data outside JIRA. Permissions and notification settings need attention before any large run. A small test and a backup protect the team from costly mistakes.