Editing multiple issues in bulk

このページの内容

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

You can assign a specific value to or remove a specific value from multiple issues. This way, you don't have to make the same change for several issues over and over again.

Available bulk actions

You can perform the following bulk actions:

  • You need the Portfolio for Jira user permission to save changes in Jira.
  • Sub-tasks inherit certain values of its parent story, including sprints, releases, and teams. You'll need to update such values of the parent story instead.

Assigning issues to an assignee

This section applies to issues that have never been assigned to an assignee, or issues that you want to reassign to a different assignee.

  1. In the scope section, select the checkboxes for the corresponding issues.
  2. Click the Bulk actions menu > Assignee.
  3. Choose the corresponding assignee for the selected issues.
    To remove the current assignees for the selected issues, choose Unassigned instead.
  4. Click Apply. The issues will be assigned to the selected assignee.
    Note that the issues will remain selected in the scope section.
  5. 次のように変更を保存します。
    1. [変更をレビュー] をクリックします。[変更をレビュー] ダイアログが表示され、既定ですべての変更が選択されます。
    2. Make sure the checkboxes for the assignee changes are selected, then click Save selected changes in Jira.

    You need the Portfolio for Jira user permission to save changes in Jira.

Assigning issues to a team

This section applies to issues that have never been assigned to a team, or issues that you want to reassign to a different team.

  1. In the scope section, select the checkboxes for the corresponding issues.
  2. Click the Bulk actions menu > Team.
  3. Choose the corresponding team for the selected issues.
    To remove the current values for the selected issues, choose None instead.
  4. Click Apply. The issues will be assigned to the selected team.
    Note that the issues will remain selected in the scope section.
  5. 次のように変更を保存します。
    1. [変更をレビュー] をクリックします。[変更をレビュー] ダイアログが表示され、既定ですべての変更が選択されます。
    2. チームの変更に関するチェックボックスが選択されているのを確認してから、[選択した変更を Jira で保存] をクリックします。

    You need the Portfolio for Jira user permission to save changes in Jira.

Updating the parent of issues

To update the parent of issues, the issues must be of the same hierarchy level. Also, issues of the highest level in the hierarchy can't be moved to a new parent since these issues can't be moved any higher.

  1. In the scope section, select the checkboxes for corresponding issues.
  2. Click the Bulk actions menu > Parent.
  3. Choose the corresponding parent for the selected issues.
    To remove the current values for the selected issues, choose None instead.
  4. Click Apply. The issues will be moved to the selected parent.
    Note that the issues will remain selected in the scope section.
  5. 次のように変更を保存します。
    1. [変更をレビュー] をクリックします。[変更をレビュー] ダイアログが表示され、既定ですべての変更が選択されます。
    2. Make sure the checkboxes for the parent changes are selected, then click Save selected changes in Jira.

    You need the Portfolio for Jira user permission to save changes in Jira.

Updating the rank of issues

  1. In the scope section, select the checkboxes for corresponding issues.
  2. Click the Bulk actions menu > Rank.
  3. Choose the new rank for the selected issues:
    • Top of plan: To rank the issues as highest priority and move these to the top of the plan
    • Bottom of plan: To rank the issues as lowest priority and move these to the bottom of the plan
    • Above issue: To rank the issues above a specific issue that you'll have to choose. You'll also be shown the new rank that the issues will have once the changes are applied.
    • Below issue: To rank the issues below a specific issue that you'll have to choose. You'll also be shown the new rank that the issues will have once the changes are applied.
  4. Click Apply. The issues will be moved to the new rank.
  5. 次のように変更を保存します。
    1. [変更をレビュー] をクリックします。[変更をレビュー] ダイアログが表示され、既定ですべての変更が選択されます。
    2. Make sure the checkboxes for the issue rank changes are selected, then click Save selected changes in Jira.

    You need the Portfolio for Jira user permission to save changes in Jira.

When you're reranking issues, the issues may appear to be ranked lower or higher than their actual rank. This is because in Portfolio, the issues will be visually ranked according to the parent-child relationships that these may have.

However, when you view these issues in Jira, the new rank of the issues will be more directly discernible. This is because issues in Jira do not have any parent-child relationships, and are then ranked in a flat list in Jira.

But because the parent-child relationships of the issues will persist in Portfolio for Jira, then an issue that appears to be ranked higher in a Portfolio plan may actually be ranked lower in Jira.

Updating the release of issues

To update the release of multiple issues, the issues must belong to the same project.

  1. In the scope section, select the checkboxes for the corresponding issues.
  2. Click the Bulk actions menu > Release.
  3. Choose the corresponding release for the selected issues.
    • Only the releases that are associated with the projects of the selected issues will be available.
    • To remove the current values for the selected issues, choose None instead.
  4. Click Apply. The issues will be added to the selected release.
    Note that the issues will remain selected in the scope section.
  5. 次のように変更を保存します。
    1. [変更をレビュー] をクリックします。[変更をレビュー] ダイアログが表示され、既定ですべての変更が選択されます。
    2. Make sure the checkboxes for the release changes are selected, then click Save selected changes in Jira.

    You need the Portfolio for Jira user permission to save changes in Jira.

Updating the sprint of issues

  1. In the scope section, select the checkboxes for corresponding issues.

  2. Click the Bulk actions menu > Sprint.
  3. Choose the corresponding sprint for the selected issues.
    To remove the current values for the selected issues, choose None instead.
  4. Click Apply. The issues will be moved to the selected sprint.
    Note that the issues will remain selected in the scope section.
  5. 次のように変更を保存します。
    1. [変更をレビュー] をクリックします。[変更をレビュー] ダイアログが表示され、既定ですべての変更が選択されます。
    2. Make sure the checkboxes for the sprint changes are selected, then click Save selected changes in Jira.

    You need the Portfolio for Jira user permission to save changes in Jira.

Updating the target dates of issues

  1. In the scope section, select the checkboxes for the corresponding issues.
  2. To update the target start date of issues:
    1. Click the Bulk actions menu > Target start.
    2. Choose the corresponding target start date for the selected issues.
      To remove the current values for the selected issues, choose None instead.
  3. To update the target end date of issues:
    1. Click the Bulk actions menu > Target end.
    2. Choose the corresponding target end date for the selected issues.
      To remove the current values for the selected issues, choose None instead.
  4. Click Apply. The dates will be updated for the issues.
    Note that the issues will remain selected in the scope section.
  5. 次のように変更を保存します。
    1. [変更をレビュー] をクリックします。[変更をレビュー] ダイアログが表示され、既定ですべての変更が選択されます。
    2. Make sure the checkboxes for the target date changes are selected, then click Save selected changes in Jira.

    You need the Portfolio for Jira user permission to save changes in Jira.

Removing issues from a plan

  1. In the scope section, select the checkboxes for the corresponding issues.
  2. Click the Bulk actions menu > Remove from plan.
  3. 確認ダイアログで [削除] をクリックします。
  4. 次のように変更を保存します。
    1. [変更をレビュー] をクリックします。[変更をレビュー] ダイアログが表示され、既定ですべての変更が選択されます。
    2. 削除したいチェックボックスが選択されているのを確認してから、[選択した変更を Jira で保存] をクリックします。

    You need the Portfolio for Jira user permission to save changes in Jira.

  • Issues that are already saved in Jira will be removed from the plan, but will remain in Jira.
  • Issues that aren't saved in Jira just yet will be permanently deleted from the plan.
最終更新日: 2019 年 12 月 30 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.