Modifying Multiple (Bulk) Issues

Bulk Operations enable operations to be performed on multiple issues at once. These operations are performed on the result set of a search. The following list details the available bulk operations:

  • Workflow Transition
    Lets you transition multiple issues through a workflow at once — e.g. resolve a collection of issues.
  • Delete
    Lets you delete multiple issues at once.
  • Move
    Lets you move multiple issues between projects and/or issue types. Please see the Bulk Move section for further details.
  • Edit
    Lets you edit multiple fields in multiple issues at once. Please see the Bulk Edit section for further details.
  • Watch / Stop Watching
    Lets you start or stop watching multiple issues.

On this page:

About the 'Bulk Change' Global Permission

In order to execute a bulk operation, you will need to be granted the appropriate project-specific permission and the global Bulk Change permission by your JIRA administrator. For example, you would need to be granted both the Move Issue and Bulk Change permissions in order to execute the Bulk Move operation.

The project-specific permissions are still respected for the collection of issues selected for the bulk operation.

Disabling Mail Notification for Bulk Operations

To disable mail notification for a particular bulk operation, deselect the Send Notification checkbox in the bulk operation wizard. In order for this option to be available, you must be an administrator or project administrator of all the associated projects on whose issues the bulk operation is being performed.

Performing a Bulk Operation

  1. Perform a search with the required filters to produce an issue result set.
  2. Select Tools > Bulk Change.
  3. The next screen allows the selection of the issues on which to perform the bulk operation.

  4. The next screen allows the bulk operation to be selected, see the table below for the operation you are performing.

    Operation Action
    Delete The final step is confirmation of the delete operation on the selected issues.
    Edit

    The next screen provides a list of the available edit operations that can be performed on the issues selected. After selecting the required Edit operation(s), the final step is confirmation of the edit operation(s) on the selected issues.

    Move The next screens allow a target project and issue type to be selected, with the ability to migrate workflow statuses and update required fields as necessary. Further details can be found in the Bulk Move section.
    Workflow Transition The next screen shows the available workflow transitions that can be performed on the issues. The transitions are grouped by workflow — along with a list of the affected issues for each workflow transition. Once an operation is selected, the appropriate field screen for that operation is displayed — allowing any necessary field edits that are required to complete the transition. It should be noted that only those issues associated with the selected transition will be updated. It is only possible to select one transition per bulk workflow transition operation.
    Watch The final step is a confirmation of the watch operation on the selected issues.
    Stop Watching The final step is a confirmation of the unwatch operation on the selected issues.

Bulk Operation Screens

See the images below for examples of the Bulk Operation workflow.

Step One Step Two
/download/attachments/185729606/bulkops-step1.1024x768.png?version=1&modificationDate=1367887066159&api=v2"/>
Step Three Step Four

Bulk Move

The Bulk Move operation allows multiple issues to be moved at once. It is possible to move a selection of issues to a new project, with the ability to select a new issue type in certain cases. 

The operation is completed as follows:

  1. Select Projects and/or Issue Types
  2. Select Projects and/or Issue Types for Sub-Tasks
  3. Select status migration mappings for invalid statuses
  4. Select values for required fields and fields with invalid values
  5. Confirm changes to be made and complete the operation
    Note that steps 3 and 4 will occur once for each different target project and issue type combination.

Select Issues

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 which 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.

Select Projects and Issue Types

The first step of the Bulk Move wizard is to choose which projects and issue types you will move your issues to. The target project and issue type will determine whether extra steps will be required to migrate statuses and fields.

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.

(info) Note: This does not apply to sub-tasks since they cannot be moved to a standard issue type.

Select Projects and 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.

Workflow Status Mapping

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, JIRA allows you to specify a mapping from invalid statuses to those available in the target workflow.

Field Updates

In order to adhere to the field configuration scheme associated with the target project and issue type, it may be necessary to update/populate required fields (e.g. fields that are required in the target project, but may not have been in the original project).

For each field that needs to be populated, you will be prompted to supply a value. This value will be applied to all issues that are being Bulk Moved together.

For the following fields, JIRA provides a list of possible values for you to select from:

  • 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.

Retain Original Values

It is possible to retain original field values that are valid in the target destination by checking the Retain checkbox associated with the field. For example, some issues may already include a valid custom field value — these values can be retained, while issues that require an update will adopt the value specified on the Field Update screen.

  • Checked: the original value is retained where possible¹. The field will not be updated with the specified new value.
  • Unchecked: all fields will be updated with the specified new value.

Note that the 'Retain' checkbox is not available for the following fields, since an explicit mapping is required:

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

Bulk Move Confirmation

When all move parameters — e.g. target project, status mappings and field updates — have been specified for all issues, you will be presented with a confirmation screen displaying all changes that will be made to the issues being moved. The following details are displayed as applicable:

  • Issue Targets: the target project and issue type
  • Workflow: the target workflow and invalid status mappings
  • Updated Fields: new values for fields that require updating
  • Removed Fields: values to be removed in fields that are not valid in the target

The issues will only be moved once the Confirm button is clicked from the confirmation page. If the operation is exited anytime before this step, no changes will be made to the issues.

Bulk Edit

The Bulk Edit operations available depend on the issues selected and the nature of the field it changes.

Available Operations

The following table lists out the possible operations. Please note that all the conditions must be true for the corresponding operation to be available.

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

Change Sprint

You need to specify the sprint ID, even if you are using JIRA Agile 6.3.9 (which has the new Sprint field) or later with JIRA.

  • 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

Troubleshooting

Was this helpful?

Thanks for your feedback!

63 Archived comments

  1. User avatar

    Anonymous

    Retain value where possible seems to have extra comment, but where? I've had many problems with retain overwriting the assignees and reporters, even i it was checked. 

    04 Oct 2011
    1. User avatar

      Anonymous

      +1 i have the same problem

      20 Jul 2012
  2. User avatar

    Anonymous

    Its very nice feature .

    It is very useful for testing puprose

    10 Oct 2011
  3. User avatar

    Anonymous

    It would be great if we could ADD (not overwrite) attachments in bulk - IE - meeting notes where several Issues were discussed.

    22 Dec 2011
    1. User avatar

      Anonymous

      Agreed, Bulk attachments would preferably be enable-able. I know it is potentially destructive, but I'm working on a project for the US Government where this action has been considered, and approved for custom development.

      I would suggest as a healthy alternative, use a custom field to provide a link to an external document resource.

      21 Feb 2012
    1. User avatar

      Anonymous

      +1 have the same suggestion/problem

      11 Dec 2012
  4. User avatar

    Anonymous

    I'm not sure why "remaining time" shouldn't be bulk-edited.  At the end of the iteration, we want to zero out the remaining time on all closed tasks (i.e., to clean up after users who don't).

    15 Feb 2012
    1. User avatar

      Anonymous

      Agreed. If the issues are closed and they are not zeroed they still appear in the workload reports.

      30 May 2012
      1. User avatar

        Anonymous

        Or have an option in Time Tracking to automatically zero Remaining Time when an Issue is closed

        29 Jun 2012
  5. User avatar

    Anonymous

    I would like to know, if there is any way by which an administrator of a project (not system admin) in JIRA is able to undo the last bulk action performed on changing the labels?

    I have tried to bulk add a label to a group of issues in jira. I thought all previous labels will remain as it is. But unfortunately all previous labels were overwritten and only one label was assigned to all of them, which i did not want.

    Is there a way i can undo this label change in jira for the bulk issues and get the previous labels as before?

    27 Mar 2012
    1. User avatar

      Anonymous

      Please send me a notification to syedatasneemrumy@gmail.com

      27 Mar 2012
    1. User avatar

      Anonymous

      Did you ever figure out how to do this....I just did the same thing?

      01 Mar 2013
  6. User avatar

    Adam Cataldo

    Just a word of warning on the Bulk Change...If you're changing more than about 10 issues at a time, this is really slow. It can take minutes for each step of the change.

     

    03 Apr 2012
  7. User avatar

    Anonymous

    Question about Bulk Move - does it remove the items from the source project?  I am looking for a Bulk function which copies from one project to the other.  Does that exist?

    Thanks

    23 Apr 2012
    1. User avatar

      Roy Krishna [Atlassian]

      Bulk move does remove items from the source. JIRA does not have native bulk copy at this time.

      23 Apr 2012
  8. User avatar

    Anonymous

    I'm attempting to move 11 issues to a new project.  I'm getting an error stating I have to specify the reporter.  I have checked the check box to retain original values.  Is there a way to retain that information so that I don't have to edit each issue once it's moved?

     

    01 May 2012
    1. User avatar

      Anonymous

      +1.  This is also a problem for me.  Except I have to move 200.

       

      03 Aug 2012
    1. User avatar

      Anonymous

      I am encountering the same problem as well where I have to specify the reporter.

      29 Aug 2012
  9. User avatar

    Anonymous

    Can we add original estimate in the bulk edit screen, so that we can update the original estimate value. Reason why is, for some issues we dont want any estimated time.

    Could you please let us know whether this cam be possible.

    Thanks in advance,

     

    08 May 2012
  10. User avatar

    Anonymous

    There is an option of export to excel all the issues. Is there any option by which we can update the excel and then upload it to update issues in jira??

    22 May 2012
    1. User avatar

      Andrew Lui [Atlassian Technical Writer]

      Hi,

      You can export issues to Excel from JIRA. See Exporting Search Results to Microsoft Excel. You can import data in JIRA from a CSV file (see Importing Data from CSV), however the data needs to be in a specific format.

      Kind Regards,
      Andrew

      27 Aug 2012
      1. User avatar

        Anonymous

        Hi,

        Regarding CSV import, is it possible to import CSV files by non-admin users. I mean to say any group will do the CSV import other than jira-administrators?

         

        Thanks,

        Rambabu

        20 Jun 2013
  11. User avatar

    Anonymous

    It would be useful to bulk edit a series of subtasks without having to perform a search. If a parent task has a bunch of subtasks, I would like to assign the parent and all of its children to a new user or modify their fix version all at once, not one at a time. Performing a search first seems like a hassle when they're already visible in your face...

    14 Jun 2012
    1. User avatar

      Andrew Lui [Atlassian Technical Writer]

      Hi,

      Thanks for your feedback on this feature. Please feel free to raise a feature request for this at https://jira.atlassian.com/

      Kind Regards,
      Andrew

      27 Aug 2012
      1. User avatar

        Anonymous

        JRA-21470 - Bulk move on sub-tasks should support changing the parents Open

        26 Sep 2013
  12. User avatar

    Seb

    Hey (smile)

    Is it possible to disable e-mail notifications as default? If yes, how? If not, buh! (big grin)

    Cheers,

    Sebastian

     

    13 Jul 2012
    1. User avatar

      Anonymous

      HI,

       

      set the notification scheme to silent or just select none in the project administration

      13 Jul 2012
      1. User avatar

        Seb

        Hey (smile)

        Sorry i think i forgot to explain further. (sad)

        With "Is it possible to disable e-mail notifications as default?" i meant the option when bulk modifing issues. Step 3 offers the opportunity to disable e-mail notifications for this bulk modifiy operation.

        And that e-mail notification ist enabled by default... and i wanted to know if there's a chance to change this to disable (wink)

        Cheers,

        Sebastian

        16 Jul 2012
        1. User avatar

          Andrew Lui [Atlassian Technical Writer]

          Hi,

          This cannot be changed in JIRA. Please feel free to raise a feature request for this at https://jira.atlassian.com/

          Kind Regards,
          Andrew

          27 Aug 2012
  13. User avatar

    Anonymous

    Hi All - Could anyone please advise where I could use Bulk Workflow Transition? I want to change Resolution of issues.

    Resolution — Please use 'Bulk Workflow Transitions' to modify the resolution of issues

    25 Jul 2012
    1. User avatar

      Andrew Lui [Atlassian Technical Writer]

      Hi,

      You cannot bulk edit the resolution for issues that are already resolved, as the resolution is set when resolving the issue. You could try reopening the issues and resolving them again.

      Kind Regards,
      Andrew

      26 Aug 2012
  14. User avatar

    Anonymous

    Hi, 

    Is there a way to update existing issues from data held in excel? So, for every JIRA id in column 1 of excel, I want to update a specific field in the issue with value held in column 2.

    Thanks

     

    10 Aug 2012
    1. User avatar

      Andrew Lui [Atlassian Technical Writer]

      Hi,

      JIRA does not have any functionality to do this. Can I recommend that you post your query in https://answers.atlassian.com/?

      Kind Regards,
      Andrew

      26 Aug 2012
  15. User avatar

    John Lathrop

    I'm interested in more bulk options for our enterprise system.  I have need for bulk functionality for most available functions in JIRA.  The biggest for me right now is the ability to bulk add linked issues.  We have a custom tool that allows mass creation and we then bulk edit and transition those tickets. Bulk linking them to a parent issue would be magical!

    Thanks for all your hard work!

    17 Aug 2012
    1. User avatar

      Lionel Champalaune

      Due to the fact that the epic task relationship with user stories task in GreenHopper is not clear yet.

      I have the same requirement, I would like to do a bulk change on the link to an epic for more than one user stories but it's not possible yet.

      Thanks

       

      21 Aug 2012
      1. User avatar

        Andrew Lui [Atlassian Technical Writer]

        Hi John and Lionel,

        Thanks for your feedback on this feature. Please feel free to raise a feature request for this at https://jira.atlassian.com/

        Kind Regards,
        Andrew

        26 Aug 2012
  16. User avatar

    Anonymous

    Is there a way to do a bulk remove of a Fix Version?

    21 Aug 2012
    1. User avatar

      Andrew Lui [Atlassian Technical Writer]

      Hi,

      You can only set the Fix Version when bulk editing issues.

      Kind Regards,
      Andrew

      26 Aug 2012
  17. User avatar

    Anonymous

    Hey , is there a way for bulk editing description. It would be useful for related tasks to share the same desctiption, in my project.

    24 Aug 2012
    1. User avatar

      Andrew Lui [Atlassian Technical Writer]

      Hi,

      You cannot bulk edit the description. Please feel free to raise a feature request for this at https://jira.atlassian.com/

      Kind Regards,
      Andrew

      26 Aug 2012
  18. User avatar

    Anonymous

    Creating big amount of similar Issues would be very useful. Creating similar tickets with default data about 100 - 200 pcs is rather boring. For example test cases have often same basic data and even same labels.

     

    04 Oct 2012
  19. User avatar

    Anonymous

    Is there a way to resolve multiple issues at once?

    17 Nov 2012
  20. User avatar

    Anonymous

    Hi there? Is there any option on Bulk edit using which i can Bulk update the "status" of issues?

    Let me know.

    Thanks

    22 Nov 2012
  21. User avatar

    Ray Kiddy

    This seems really obvious, but is it true that one cannot bulk move a set of sub-issues from one parent (the same parent) to another parent?

     

    02 Jan 2013
  22. User avatar

    Anonymous

    Hello,

    After moving 200 issues, we found out that some fields were not updated i.e. Assignee, Reporter, etc. Can we retrieve that information automatically? Or we have to update every issue manually?

    Regards

    22 Jan 2013
  23. User avatar

    Anonymous

    Hello,

    Does bulk move, migrate issues as ranked so that the issues have the same rank as the old project?

     

    Thanks!

    31 Jan 2013
  24. User avatar

    Honeywell JIRA Admin

    Hi ,

    When I am doing bulk transition for "resolution","resolution" field is greyed out and not able to select the resolution?

    Regards
    Anoop

     

     

    19 Mar 2013
  25. User avatar

    Anonymous

    Xcellent! 

    19 Apr 2013
  26. User avatar

    Ronald Vallenduuk

    Bulk change - Current page doesn't work.

    Do a search, go to page 2 and select 'Bulk change - Current page' from the tools menu. Step 1 'Choose issues' shows the tickets from the first page of the search.

    20 May 2013
  27. User avatar

    Ronny Katzenberger

    How can one add versions to the Fix Versions field instead of replacing the current value via the bulk tool?
    The Fix Version field allows multiple values.

    01 Jul 2013
  28. User avatar

    Mark MacVicar

    When I use bulk change --> transition --> Close, it requires that resolution be set. I've found that removing "Resolution" from the Close transition screen makes this requirement go away. What I'd prefer is that resolution can be modified, but isn't required on a bulk close. How to I make it optional?

    01 Oct 2013
  29. User avatar

    Anonymous

    Is there a way to add the same set of sub-tasks to multiple issues once those issues are already created?

    07 Oct 2013
  30. User avatar

    Anonymous

    If I am doing a Bulk Edit and I choose a particular component in "Change Component/s" then does it set every ticket to have only that one component or does it append the component to the tickets' lists, where tickets do not already have it?

    17 Oct 2013
    1. User avatar

      Anonymous

      The behavior I have seen is that bulk changes clobber previous values, they don't append. That might be a nice feature.

      17 Oct 2013
  31. User avatar

    Anonymous

    Hi JIRA admin, is it possible to add batch operations that do small and specific modifications like "edit Assignee"? It's kind of slow to use the batch edit to pop out a large window.

    03 Feb 2014
  32. User avatar

    Yixin Dong

    Hi JIRA admin, is it possible to add bulk change operations that do small and specific modifications like "edit Assignee"? It's kind of slow to use the bulk edit to pop out a large window.

    03 Feb 2014
  33. User avatar

    Anonymous

    Hi JIRA Admin - I would like to know if there is a way to bulk edit a multi-select field without overriding the existing selections. For example, features A-Z are assigned to various combinations of projects (multi-select field has project A, B.and/or C selected).  Now I want to assign all of these features A-Z to a 3rd project.  How can I add this 3rd project to the multi-select field without overriding the current selections?  Thanks.

    08 Feb 2014
  34. User avatar

    Suresh Kumar

    Couldn't update more than 200 records at a time via Bulk change operation?

    Could any one help me to figure out the other way to fix this issue.

    27 Nov 2014
  35. User avatar

    Carine Chambon

    I need to unwatch issues for another user (as administraor of course, not enable this pour everyone)

    it's too bad we can't choose one user specificly for this watch / unwatch.

    17 Feb 2015
  36. User avatar

    Peter Saulesleja

    As an administrator, when a user leaves the company, and his email is autoforwarded, I need a way to bulk-unwatch for that user, to eliminate the email torrent to the autoforwardee.  

    Bulk edit needs an "add watcher" and "remove watcher" other than the currentuser.

    20 Mar 2015
  37. User avatar

    Kyle Pennell

    "Perform a search"

     

    ????

     

    I just simply want to grab all the issues I have and delete them.  I don't want to search for them.  I don't know how I would search for them.  I simply, again, just want to select all the issues and use your clunky bulk tool to delete them.  That's it.  That's all I want.  I work with all sorts of software and cannot figure out yours when I try to.

    29 Jun 2015
  38. User avatar

    Kyle Pennell

    Add this text in:

     

    If you wish to work with all the issues you have, simply enter a blank in the search.

     

    29 Jun 2015
  39. User avatar

    Nithya Venugopal

    We had to do a bulk deletion of issues for projects:

    •         124_Mobile Apps_Clubcard_Native_iOS (MACN)
    •         124_Mobile Apps_Clubcard_Android (MACA)
    •         124_Mobile Apps_Clubcard_Native_Android (MCNA)

    These projects can now be deleted. 

    19 Aug 2015
Powered by Confluence and Scroll Viewport