Documentation for JIRA 4.4. Documentation for other versions of JIRA is available too.
On this page:
'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:
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.
プロジェクト固有の権限は、一括操作に選択した課題のコレクションに対して尊重されます。
It 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.
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 issues are selected through the Issue Navigator as discussed above.
操作手順:
一括移動操作は標準課題とサブタスク課題の両方で実行できます。標準課題を別のプロジェクトや課題タイプに移動できるのに対し、サブタスクは課題タイプのみを変更できます。(サブタスクを課題に変換、およびその逆は可能です)
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.
一括移動ウィザードでは最初に、課題の移動先となるプロジェクトおよび課題タイプを選択します。ターゲットプロジェクトや課題タイプによって、ステータスやフィールドの移行に追加手順が必要かどうかが決定します。
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.
If 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.
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.
This step of the wizard will only appear if you have invalid statuses. If you are moving issues to different projects and issue types at the same time, you will complete this step as well as the next for each of the different target project and issue type combinations. To help you easily keep track of your progress, the current context, that is the target project and issue type, is highlighted in the left-hand 'progress' pane.
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 (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.
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.
次のフィールドでは明確なマッピングが必要なため、「保持」チェックボックスは使用できません。
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:
課題は、確認ページで確認ボタンを押すまで移動されません。この手順の前に操作を終了した場合、課題は変更されません。
Screenshot: Bulk Move Confirmation
The Bulk Edit operations available depend on the issues selected and the nature of the field it changes.
次の表は利用可能な操作の一覧です。対応する操作を利用するには、すべての条件が TRUE である必要があります。
利用可能な操作 |
条件 |
---|---|
変更が影響するバージョン |
|
Change Assign To |
|
コメントの変更 |
|
コンポーネントの変更 |
|
期限の変更 |
|
バージョンの修正を変更 |
|
課題タイプの変更 |
|
優先度の変更 |
|
報告者の変更 |
|
セキュリティレベルの変更 |
|
カスタムフィールドの変更 |
「カスタムフィールドの変更」操作は次の場合にのみ使用できます:
|
クローズドされた課題の編集 |
|
このセクションに記載されているフィールドには一括編集操作はありません。これには、代替方法がある、または一括編集の実行が論理的でないなどの理由があります。
次のシステムフィールドは一括編集を使用できません:
The following custom fields are unavailable for bulk editing: