Managing Portfolio dependencies
Administering Portfolio for Jira
このページの内容
関連コンテンツ
- What are the limitations of Code Coverage?
- What are releases in your plan
- Limitations of team-managed projects in your plan
- Known limitations of the repository labels
- How can I plan with releases on my project timeline?
- End of support announcements
- Using the later release
- Manage releases
- Preparing for Confluence 7.16
- Monitoring releases
You can configure Portfolio for Jira to use issue links in your Jira application, so that you can define scheduling dependencies. When adding issue links, you need to define the relationship between the issues to suit how your team works.
Note that any changes you make to issue dependencies in Portfolio for Jira will apply to all existing Portfolio plans.
依存関係を定義する方法
- Ensure that you have issue links between dependent issues in Jira.
- Go to Portfolio (in header) > Administration > Portfolio Dependencies.
- 必要な課題リンクのタイプを追加します。
- If necessary, click Swap to set the dependency order that suits your team.
For example, for the Blocks issue link, the default dependency order isIf A blocks B then A is scheduled before B. This means that if Issue A blocks Issue B, Portfolio for Jira will schedule Issue A before Issue B.
If the reverse dependency order suits your team better, you can swap the order around to:If A blocks B then B is scheduled before A. Portfolio for Jira will then schedule Issue B before Issue A. - [変更を保存] を選択します。
In Portfolio for Jira, the block dependency is set by default.
最終更新日 2019 年 7 月 28 日
関連コンテンツ
- What are the limitations of Code Coverage?
- What are releases in your plan
- Limitations of team-managed projects in your plan
- Known limitations of the repository labels
- How can I plan with releases on my project timeline?
- End of support announcements
- Using the later release
- Manage releases
- Preparing for Confluence 7.16
- Monitoring releases
Powered by Confluence and Scroll Viewport.