Creating issues

このページの内容

お困りですか?

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

コミュニティに質問

Before creating issues, make sure that you've already done the following tasks:

  • created the initiative issue type in at least one of the projects that's being used in your plan
  • configured the hierarchy levels of your plan, as needed
  • selected all available hierarchy levels for the hierarchy range in your plan

Otherwise, some of the issue types won't be available to use. See Configuring initiatives and other hierarchy levels for more details.

You can create issues directly in your plan without having to jump back to Jira, and there are several ways to do this in the improved interface:

Also, note that the default duration for issues would depend on the timeframe in which you're viewing the plan. You can always edit the duration after the issue is created.

  • 3M: 1 week
  • 1Y: 1 month
  • Fit: The default duration depends on the date range of the issues in the timeline, which affects the width of the issues in the timeline. If the width fit is small, then the default duration could perhaps be a week or a month.
  • Custom: The default duration depends on the duration that you set between the start and end dates. If you set a short period of time, then the default duration would be shorter as well.

If you've also customized and grouped the issues in your plan, you can also create issues in the specific groupings. See Grouping issues for more details.

Creating a child issue of an issue

A plan typically contains issues coming from multiple issue sources, such as boards, projects, or filters. As a best practice, it would help you plan work and create issues more efficiently if you keep in mind the issue source, and the parent issue of the issue you're creating. This helps you create child issues of issues across multiple issue sources, where it makes most sense.

Creating a child issue of an issue

To create a child issue of an issue:

  1. In the scope section of your plan, go to the parent issue for the issue you want to create.
  2. Hover on the parent issue > click + > select the hierarchy level for the issue you're creating. This will add a row for the new issue, right below the parent issue.
  3. In the new row, select the issue type for the new issue > select the corresponding project.
    Note that the chosen project will be selected by default the next time you create an issue. You can update the project as needed.
  4. Give the new issue a name, then click Enter.
  5. If already known, specify other issue details, like assignee, team, estimate, sprint, release, and target dates.
    • The details that you can specify for an issue will depend on the corresponding issue source. For example, if you're selecting a release for TIS-123, only  the relevant releases for the TIS project will be available.

    • If you're creating a sub-task, the issue will inherit certain values of its parent story, including sprints, releases, and teams.

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

Creating an issue of the same hierarchy level

You can also create a sibling issue — sibling issues are issues of the same hierarchy level.

Creating an issue of the same hierarchy level

To create an issue of the same hierarchy level:

  1. In the scope section of your plan, find an issue of the same hierarchy level of the sibling issue you want to create.
  2. Hover on the issue > click + > select the same hierarchy level. This will add a row for the new issue, right below the issue you'd referenced.
  3. In the new row, select the corresponding project.
    Note that the chosen project will be selected by default the next time you create an issue. You can update the project as needed.
  4. Give the new issue a name, then click Enter.
  5. If already known, specify other issue details, like assignee, team, estimate, sprint, release, and target dates.
    • The details that you can specify for an issue will depend on the corresponding issue source. For example, if you're selecting a release for TIS-123, only  the relevant releases for the TIS project will be available.

    • If you're creating a sub-task, the issue will inherit certain values of its parent story, including sprints, releases, and teams.

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

Creating an issue at any hierarchy level

If you're planning high-level work and just want to create issues fast, you can choose to create issues at any hierarchy level. This is helpful for when you have some issues to create, but you can't connect these to parent issues just yet.

Creating an issue at any hierarchy level

To create an issue at any hierarchy level:

  1. In the scope section of your plan, click + Create issue.
  2. Select the hierarchy level for the issue. This will create a new issue at the bottom of the scope section, along with other issues that don't have parent issues.
  3. Give the new issue a name, and click Enter.
  4. Specify the corresponding issue details as needed:
  5. If already known, specify other issue details, like assignee, team, estimate, sprint, release, and target dates.
    • The details that you can specify for an issue will depend on the corresponding issue source. For example, if you're selecting a release for TIS-123, only  the relevant releases for the TIS project will be available.

    • If you're creating a sub-task, the issue will inherit certain values of its parent story, including sprints, releases, and teams.

  6. 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.
  • When creating an issue at any hierarchy level, both the project and issue type of the previously created issue will be used by default. You can update these details as needed.
最終更新日 2019 年 6 月 27 日

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

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