Editing multiple issues at the same time

On this page

At some point, you may need to change multiple issues at the same time. You can do this by performing a bulk operation.

There are restrictions placed on some of the bulk operations. For example, if you select multiple issues with different workflows, you can only transition them in groups with the same workflow, and one group at a time. The restrictions are explained further in the relevant sections.

We've released a new board issue view for Jira Core, and for some Jira Software users as a Labs feature. Some procedures are slightly different when viewing issues from a board. Find out more about it, and other improvements to our issue view, here.

On this page:

Before you begin

To perform a bulk operation, you'll need the global Bulk Change permission and the relevant permission for each project. For example, you would need to have the Move Issue project permission and Bulk Change global permissions to move a group of issues at the same time. 

If you are a Jira admin or a project admin, we recommend deselecting the Send Notification option to avoid notification overload for everyone working on the issues being edited. 

How to transition multiple issues

This bulk change allows you to transition multiple issues through a workflow at the same time. You can only perform one transition bulk operation at a time. You will also need to provide any values required to complete the transition. For example, to close multiple issues, you will need to provide a value for the Resolution field, such as Done, Fixed, or Won't Fix.

  1. Perform a search with the required filters to produce a list of issues.
  2. Click more () > Bulk Change all <n> issues.
  3. Select the issues you'd like to perform the bulk operation on, and click Next.
  4. Select Transition Issues, and click Next.
  5. Select the available workflow action. The actions available are dependent on the issues (and their associated workflows) that you have selected. Click Next.
  6. Select a value for any required fields for this transition, and if available, decide whether you'd like to send email notifications. Click Next.
  7. Review your bulk operation, and click Confirm when you are happy with the operation.

How to delete multiple issues

This bulk change allows you to delete multiple issues at the same time.

  1. Perform a search with the required filters to produce a list of issues.
  2. Select more () > Bulk Change all <n> issues.
  3. Select the issues you'd like to perform the bulk operation on, and click Next.
  4. Select Delete Issues, and click Next.
  5. If available, decide whether you'd like to send email notifications. click Next.
  6. Review your bulk operation, and click Confirm when you are happy with the operation.

How to move multiple issues

This bulk operation allows you to move multiple issues at the same time. The issues you're moving need to be mapped to both a project and an issue type, and in doing this, you may need to also map the status and fields of the issues. Subtasks need to be mapped, too.

  1. Perform a search with the required filters to produce a list of issues.
  2. Click more () > Bulk Change all <n> issues.
  3. Select the issues you'd like to perform the bulk operation on, and click Next.

    More information...

    The bulk move operation can be performed on both standard issues and sub-task issues. Standard issues can be moved to another project and issue type, whereas a sub-task can only have its issue type changed. (Note that it is possible to convert a sub-task to an issue, and vice versa.)

    It is not possible to select both a sub-task and its parent to bulk move. This is so as to adhere to the parent/sub-task relationship (i.e. the sub-task is always located in the same project as the parent issue). Any sub-tasks of selected parent issues that were also selected will be automatically discarded from the move.

    For example, you have issue B being a sub-task of issue A and you try to bulk move both A and B simultaneously. You will see a warning message (see below) and will be prompted to select a target project and issue type for issue A. If you select a new project for A, you will be prompted to move the sub-task to a new issue type based on issue A's new project. If you don't change the project for issue A, the sub-task will not be required to be moved.

  4. Select Move Issues, and click Next.
  5. Enter the requested information for the issues you're moving. 

    Expand to see what information to enter...
    Info requested Details
    Select projects and/or issue types

    The target project and issue type will determine whether extra steps will be required to migrate statuses and fields. Note that this does not apply to sub-tasks, which can't be moved to a standard issue type. Selected issues are grouped by their current project and issue type. You can either select a new project and issue type for each one or choose to move all standard issues to a single project and issue type.

    Select projects and/or issue types for sub-tasks If you are moving issues with sub-tasks to another project, you will also need to move the sub-tasks to the new project. You can also elect to change the issue types of the sub-tasks being moved if you need to.
    Select status migration mappings for invalid statuses As multiple workflows can be active simultaneously, some statuses associated with the collection of selected issues may not be valid in the target workflow. In this case, you should map invalid statuses to valid statuses in your new workflow.
    Select values for required fields and fields with invalid values

    In order to adhere to the field configuration scheme associated with the target project and issue type, it may be necessary to update required fields. Note that the same field value will be applied to all issues being moved together. Check the Retain option to keep original field values.

    For the following fields, you will need to select a new field value:

    • Component
    • Affects Version
    • Fix Version
    • Custom fields of type 'Version-Picker'

    Note that versions which have been archived in the target project cannot be selected as the target when performing a bulk move. If you need to move issues into an archived version, you will need to first unarchive the version in the target project.

  6. Review all the changes and click Confirm

How to edit multiple issues

This bulk operation allows you to edit multiple issues at the same time. The bulk edit operations available depend on the issues selected and the nature of the field/s you want to change.

  1. Perform a search with the required filters to produce a list of issues.
  2. Click more () > Bulk Change all <n> issues.
  3. Select the issues you'd like to perform the bulk operation on, and click Next.
  4. Select Edit Issues, and click Next.
  5. Choose what information to edit. 

    Information you can edit at the same time...

    Available Operations

    Conditions

    Change Affects Version/s

    • Selected issues belong to one project, and that project has version/s
    • This field is not hidden in any field configurations the selected issues belong to
    • Current user has 'edit issue' permission for all the selected issues

    Change Assign To

    • This field is not hidden in any field configurations the selected issues belong to
    • Current user has 'assign issue' permission for all the selected issues

    Change Comment

    • This field is not hidden in any field configurations the selected issues belong to
    • Current user has 'comment issue' permission for all the selected issues

    Change Component/s

    • Selected issues belong to one project, and that project has component/s
    • This field is not hidden in any field configurations the selected issues belong to
    • Current user has 'edit issue' permission for all the selected issues

    Change Due Date

    • This field is not hidden in any field configurations the selected issues belong to
    • Current user has 'edit issue' permission for all the selected issues
    • Current user has 'schedule issue' permission for all the selected issues

    Change Fix For Version/s

    • Selected issues belong to one project, and that project has version/s
    • This field is not hidden in any field configurations the selected issues belong to
    • Current user has 'edit issue' permission for all the selected issues

    Change Issue Type

    • Current user has 'edit issue' permission for all the selected issues

    Change Priority

    • This field is not hidden in any field configurations the selected issues belong to
    • Current user has 'edit issue' permission for all the selected issues

    Change Reporter

    • This field is not hidden in any field configurations the selected issues belong to
    • Current user has 'edit issue' permission for all the selected issues
    • Current user has 'modify reporter' permission for all the selected issues

    Change Security Level

    • This field is not hidden in any field configurations the selected issues belong to
    • All the selected projects are assigned the same issue level security scheme
    • Current user has 'edit issue' permission for all the selected issues
    • Current user has 'set issue security' permission for all the selected issues

    Change Custom Fields

    The 'Change Custom Fields' operation is available only if:

    • a global custom field exists OR
    • an issue type custom field exists and the issues are all of this specific issue type OR
    • a project custom field exists and the issues are all of the same project

    Edit a Closed Issue

    • Your workflow must allow editing of closed issues
    Change organization
    • Available for Jira Service Desk Cloud
    • Issues must be in the same project
    • You must have the agent role for the project
    Change Sprint

    You need to specify the sprint ID.

    • This operation only affects active and future sprints, i.e. closed/completed sprints are not included when bulk editing the Sprint field.

    Unavailable Operations

    The fields listed in this section have no operations for bulk editing. This is because there is an alternative method or it is not logical to perform bulk edit on them.

    The following system fields are unavailable for bulk editing:

    • Attachments
    • Summary
    • Description
    • Environment
    • Project — Please use 'Bulk Move' to move issues between projects
    • Resolution — Please use 'Bulk Workflow Transitions' to modify the resolution of issues
    • Time Tracking fields — Original Estimate, Remaining Estimate, Time Spent

    The following custom field types are unavailable for bulk editing:

    • Import Id
    • Read Only Text
  6. Select a value for any required fields and, if available, decide whether you'd like to send email notifications before clicking Next.
  7. Review your bulk edits and click Confirm.

How to watch or stop watching multiple issues

These bulk changes allow you to start watching or stop watching multiple issues at the same time.

To start watching multiple issues: 

  1. Perform a search with the required filters to produce a list of issues.
  2. Select more () > Bulk Change all <n> issues.
  3. Select the issues you'd like to perform the bulk operation on, and select Next.
  4. Select Watch Issues, and select Next.
  5. Review your bulk changes and click Confirm.

To stop watching multiple issues: 

  1. Perform a search with the required filters to produce a list of issues.
  2. Select more () > Bulk Change all <n> issues.
  3. Select the issues you'd like to perform the bulk operation on, and click Next.
  4. Select Stop Watching Issues, and click Next.
  5. Review your bulk changes and click Confirm.
Last modified on Oct 18, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.