Managing Portfolio dependencies
Administering Portfolio for Jira
On this page
Related content
- Using scope and dependencies
- Displaying the dependency columns in a plan
- 6. Working with your plans
- Mapping issue assignees to team members
- Showing Portfolio custom fields in Jira
- 3. Creating Portfolio plans
- Configuring the scope view
- Scheduling behavior
- Configuring the scheduling of dependencies
- Dependencies report
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.
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 Jul 28, 2019
Related content
- Using scope and dependencies
- Displaying the dependency columns in a plan
- 6. Working with your plans
- Mapping issue assignees to team members
- Showing Portfolio custom fields in Jira
- 3. Creating Portfolio plans
- Configuring the scope view
- Scheduling behavior
- Configuring the scheduling of dependencies
- Dependencies report
Powered by Confluence and Scroll Viewport.