Prioritizing issues

このページの内容

お困りですか?

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

コミュニティに質問

To prioritize work for your teams, you can move an issue to a higher or lower row in the scope section. This moves the position of the issue in both the scope and timeline sections.

For instance, in the sample plan below, the issue IOS-26 is being moved from row #6 to row #5.

Prioritizing issues in the improved interface

  • In the scope section, when you move an issue that has child issues, the child issues will move with the parent issue. However, moving an individual child issue will only move that child issue.
  • The ranking of child issues is independent of the ranking of their parent issues. If you rank a parent epic higher, the ranking of its child issues in Jira will stay as is. This is helpful, especially if your teams have ranked their issues in their Jira boards — the child issues will retain their ranking as is.
  • プランを自動スケジュールする際は、親課題のランク付け方法は対応する子課題のランク付け順序には影響しません

  • It's important to note that the change in ranking behavior can produce different scheduling results between live plans (any version from 2.0 to 2.27) and plans with the improved interface (version 3.0 and later). For example, even if issues are placed in the same order across both types of plans, the resulting scheduling results between these types of plans will be different.

最終更新日 2019 年 9 月 20 日

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

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