Managing Portfolio dependencies
Administering Portfolio for Jira
On this page
Related content
- Your shared Bamboo configuration version is too old comparing to local node Bamboo version
- Bamboo fails to start up after upgrade to 8.0 or higher with upgrade task 70303 throwing FileNotFoundException
- Bamboo Upgrade Fails on task 51306 due to empty administration.xml file
- Bamboo fails to start when using MySQL after upgrading with AbstractMethodError
- Your Bamboo instance could not start because the Bamboo home directory does not match the database
- Bamboo upgrade fails with "FileAlreadyExistsException" for bamboo-mail.cfg.xml
- Fail to upgrade due to java.lang.StackOverflowError
- Bamboo Error: "Failed to load driver class com.mysql.jdbc.Driver from HikariConfig class classloader ParallelWebappClassLoader"
- Exception error java.lang.IncompatibleClassChangeError when starting/upgrading Bamboo with Java version 1.8.0_05
- Your shared Bamboo configuration version is too old comparing to local node Bamboo version
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.
To define dependencies:
- Ensure that you have issue links between dependent issues in Jira.
- Go to Portfolio (in header) > Administration > Portfolio Dependencies.
- Add the issue link types that you need.
- 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. - Select Save changes.
In Portfolio for Jira, the block dependency is set by default.
Last modified on Mar 22, 2019
Related content
- Your shared Bamboo configuration version is too old comparing to local node Bamboo version
- Bamboo fails to start up after upgrade to 8.0 or higher with upgrade task 70303 throwing FileNotFoundException
- Bamboo Upgrade Fails on task 51306 due to empty administration.xml file
- Bamboo fails to start when using MySQL after upgrading with AbstractMethodError
- Your Bamboo instance could not start because the Bamboo home directory does not match the database
- Bamboo upgrade fails with "FileAlreadyExistsException" for bamboo-mail.cfg.xml
- Fail to upgrade due to java.lang.StackOverflowError
- Bamboo Error: "Failed to load driver class com.mysql.jdbc.Driver from HikariConfig class classloader ParallelWebappClassLoader"
- Exception error java.lang.IncompatibleClassChangeError when starting/upgrading Bamboo with Java version 1.8.0_05
- Your shared Bamboo configuration version is too old comparing to local node Bamboo version
Powered by Confluence and Scroll Viewport.