Managing Portfolio dependencies
Add-on administration
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 to define scheduling dependencies.
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 correct dependency orders.
- Portfolio for JIRA's schedule will now consider the issue links as scheduling dependencies.
- Select Save changes.
Example
If issue A is "blocked by" issue B in your JIRA application, this means you want Portfolio for JIRA to always schedule issue B before issue A.
- Go to Portfolio > Administration > Portfolio Dependencies and add the "blocks" link type.
- If necessary, click Swap to ensure ordering reads "If A blocks B then A is scheduled before B".
- Click Save changes.
In your plan, click Recalculate.
Note
In Portfolio for JIRA, the block dependency is set by default.
Last modified on May 30, 2018
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.