Configuring issue dependencies
Administering plans
On this page
Related content
- Connecting to an LDAP Directory
- Configuring User Directories
- How to Retrieve LDAP Users and Groups from Various Organizational Units in Confluence
- Confluence to LDAP synchronization fails with 'Unable to find the username of the principal' due to LDAP configuration
- User cannot login to Confluence with LDAP synchronization enabled
- Managing Multiple Directories
- Requesting Support for External User Management
- Health check: User Directories
- The Difference Between Delegated and Connector LDAP User Directories
- LDAP synchronisation process takes too long if number of users or groups is large
If you've already configured issue links in Jira Software, you choose to use these issue links when defining scheduling dependencies in your plans.
When adding issue links to your plan, make sure to define the relationship between the issues to suit how your teams work.
Note that any changes you make to issue dependencies will apply to all existing plans.
To define dependencies:
- 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 May 15, 2020
Related content
- Connecting to an LDAP Directory
- Configuring User Directories
- How to Retrieve LDAP Users and Groups from Various Organizational Units in Confluence
- Confluence to LDAP synchronization fails with 'Unable to find the username of the principal' due to LDAP configuration
- User cannot login to Confluence with LDAP synchronization enabled
- Managing Multiple Directories
- Requesting Support for External User Management
- Health check: User Directories
- The Difference Between Delegated and Connector LDAP User Directories
- LDAP synchronisation process takes too long if number of users or groups is large
Powered by Confluence and Scroll Viewport.