JIRA 4.3 : Modifying Multiple ('Bulk') Issues
This page last changed on Jan 17, 2011 by rosie@atlassian.com.
On this page: About Bulk Operations'Bulk Operations' enable multiple operations to be performed on multiple issues at once. The bulk operations are performed on the result set of a search. The following list details the available bulk operations:
About the 'Bulk Change' Global PermissionIn 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 must 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 OperationsIt is possible to disable mail notification for a particular bulk operation by de-selecting 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
Bulk MoveThe 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 issues are selected through the Issue Navigator as discussed above. The operation is completed as follows:
Select IssuesThe 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 TypesThe 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. This screen shows all selected issues 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. To do this, select the check box with the label Use the above project and issue type pair for all other combinations and the selected project / issue type will apply. Note that this will not apply to sub-tasks since they cannot be moved to a standard issue type. Select Projects and Issue Types for Sub-TasksIf you are moving issues with sub-tasks to another project, you will also need to move the sub-tasks to the new project. On this screen you can elect to change the issue types of the sub-tasks being moved if you need to. Workflow Status MappingAs 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 UpdatesIn 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 (see 'Retain Original Values' below for more details). For the following fields, JIRA will provide a list of possible values for you to select from:
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 ValuesIt 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.
Note that the 'Retain' checkbox is not available for the following fields, since an explicit mapping is required:
Bulk Move ConfirmationWhen 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:
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. Screenshot: Bulk Move Confirmation Bulk EditThe Bulk Edit operations available depend on the issues selected and the nature of the field it changes. Available OperationsThe following table lists out the possible operations. Please note that all the conditions must be true for the corresponding operation to be available.
Unavailable OperationsThe 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:
The following custom fields are unavailable for bulk editing:
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
Document generated by Confluence on Mar 27, 2011 18:27 |