Managing Portfolio dependencies
Administering Portfolio for Jira
このページの内容
関連コンテンツ
- Bamboo fails to start when upgrading to version 9.2.7 or later with "Could not load bootstrap from environment java.lang.RuntimeException: Cannot set any global DeserializationFilter filter"
- Issues resolved in Confluence 2.9
- Performance issue with Red Hat Enterprise Linux (RHEL)
- Bamboo Java Specs scanning fails with "artifacts could not be resolved" error
- Error when creating an issue in JIRA from Bamboo
- Creating Jira application issues from a build
- Analyse File System Problems on Windows - MS Process Monitor
- Bamboo Support Policy
- Bamboo Specs troubleshooting
- Bamboo doesn't start up: Your build of Bamboo is too old to work with the data in your Bamboo home directory
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, except classic 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.
最終更新日: 2018 年 12 月 18 日
関連コンテンツ
- Bamboo fails to start when upgrading to version 9.2.7 or later with "Could not load bootstrap from environment java.lang.RuntimeException: Cannot set any global DeserializationFilter filter"
- Issues resolved in Confluence 2.9
- Performance issue with Red Hat Enterprise Linux (RHEL)
- Bamboo Java Specs scanning fails with "artifacts could not be resolved" error
- Error when creating an issue in JIRA from Bamboo
- Creating Jira application issues from a build
- Analyse File System Problems on Windows - MS Process Monitor
- Bamboo Support Policy
- Bamboo Specs troubleshooting
- Bamboo doesn't start up: Your build of Bamboo is too old to work with the data in your Bamboo home directory
Powered by Confluence and Scroll Viewport.