Saving changes in Jira

This page refers to the usage of the improved planning interface in Portfolio for Jira (version 3.0 and later). If you're using a Portfolio for Jira live plan (any version from 2.0 to 2.27), refer to the documentation in this section.

Portfolio for Jira lets you make changes in your plan in a sandbox environment. While you're trying to create the ideal schedule for your team, you can make any changes and move issues around, without having to worry about how these changes impact the work of your teams in Jira.

As a best practice, we recommend that you review and save your changes in Jira as often as possible. This gives your teams access to the latest updates you've made for the work that they're doing.

Saving changes

To review the changes made in your plan, you'll need at least the Portfolio for Jira viewer permission. To save these changes in Jira, you'll need the Portfolio for Jira user permission. See Permissions in Portfolio for Jira for more details.

In the roadmap view of your plan, above the timeline section, click Review changes. The 'Review changes' dialog will display, with all changes selected by default.

While reviewing your changes, perform the following as needed:

  • To view multiple changes, expand the corresponding item in the 'What changed' column.
  • With all the checkboxes already selected by default, clear the ones for the changes you do not want to save in Jira. While these changes won't be saved in Jira, these will still exist in your Portfolio plan.
  • Select the checkboxes of the changes you want to save in Jira, then click Save selected changes in Jira.
  • To discard any changes, select the checkboxes of these changes, then click Discard selected changes. These changes will then be discarded from your plan, and the values will revert to the ones currently saved in Jira.
  • If you encounter some warnings when saving changes to Jira, we recommend fixing these warnings first, and then try saving the corresponding changes again. See the Troubleshooting section for some of the commonly encountered issues.

  • You need the  Portfolio for Jira user permission to save changes in Jira.
  • While the changes are being saved, you can make Portfolio stop saving the rest of the changes. By clicking Quit, Portfolio will still save the change it's currently working on, but will not save the rest.

Troubleshooting when saving changes

Required custom fields in Jira issues

When you have required custom fields in your Jira issues, this may cause problems when you try to save some of the newly created issues in your plan. This is because Portfolio for Jira would not have the columns for the custom fields in the plan itself.

Do any of the following, as needed:

  • Make the custom fields in your Jira projects no longer required.
  • If the required fields are really necessary, make sure to enter the details for the required fields in the dialog that will display.

Custom fields not supported for issues types or projects in plan

There may be times when a custom field is  not supported for the  issue types or  projects in the plan. If this is the case, and you set a value for this custom field in the plan, you may not be able to save this change in Jira. If you need this change to be saved in Jira, ask your Jira admin to make sure the issue type and project of the corresponding issue are supported. See  Configuring a custom field to learn more.

Child issues not saved to Jira

When you're creating a new parent issue and new child issues for it, the parent issue needs to be saved to Jira, so that the child issues will also be saved to Jira.

Let's say you've created the parent issue ABC-01, and the child issues TIS-001, TIS-002, and TIS-003.

If you were to select only TIS-002 and try to save that change to Jira, you won't be able to do this because its parent issue ABC-01 isn't saved to Jira.

最終更新日 2019 年 7 月 28 日

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

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