Cross-PI dependencies
The cross-PI page shows dependencies between ARTs

What is shown?
The cross-PI view displays issues with dependencies between different PIs for the selected period. Dependencies can be of the "parent-child" or the "blocks/is blocked by(*)" issue link type.
(*) Jira admins can change the issue link type used in Ativo. The default is 'blocks/is blocked by'.
Issues without cross-PI dependencies are hidden.

Programs and teams are visible if:
they are configured for the selected period, and
they have issues with cross-PI dependencies.
Replan
Drag & drop issues to replan them into another sprint. Click on the expand chevron to update the RAG status or risk/impediment of an issue.
Filter
Click on 'Filter' in the top navigation to filter on epics, programs (ARTs), teams, releases or issue types.

View options
Click on View options > Card layout to configure the fields that are visible on the card.

Issues in multiple PI's
Ativo displays issues only once on a Cross-PI board.
When issues belong to multiple PIs, they are shown only once on the Cross-PI board. Any duplicate instances are hidden, and a warning flag is displayed to the user. Additionally, a warning message appears in the footer of the page: "Some issues within the scope of multiple programs/teams are shown only once."

Issues belonging to multiple PIs may also affect their visibility on the Cross-PI board. An issue is displayed on the Cross-PI board only if it has a dependency link with an issue from another PI and does not already appear on the board of that other PI.

Permissions
Ativo Programs strictly respects the Jira security permission schemes. When a user doesn't have access to see issues in a team or program, a warning is shown instead of the issues.

Last updated