Introduction

The issue hierarchy is viewable in all issues in Jira projects added to the SAFe® hierarchy via My Organization.

It is either already available in an issue’s detail view or the hierarchy can be added by clicking the SAFe® Hierarchy button in the ‘Apps’ drawer of the issue view toolbar.

The core purpose of issue hierarchy links is two-fold and can be understood as follows:

• Provides the context of which higher-level work that the work of a team or an ART contributes to.

• Defines the visualization of ART feature swimlanes on the team boards.

Open

Constraints of Agile Hive Issue Hierarchy

The issue hierarchy link unveils how an issue in a project on one of the upper SAFe® hierarchy layers is being broken down into work at a lower level. It always displays the current issue’s hierarchical links (parent issue + children) if available.

• Parent-Child Relationships (general):

  • It links issues hierarchically, that are located on adjacent layers in the ‘My Organization’ project hierarchy.

  • Each issue can have exactly one parent issue (except for issues in Portfolio-level projects). This is always a one-to-one relationship.

  • Each issue can have multiple child issues linked to it (except for issues in Team-level projects). This is always a one-to-many relationship.

• Linking ART-level Projects:

  • When linking issues from ART-level projects to a parent, users can bypass the Large Solution layer (if configured) and create a direct hierarchical link to any Portfolio-level issue.

• Objectives Linking:

  • Objectives can only be linked to other Objectives.

  • Whether an issue is classified as an ‘Objective’ depends on the issue type mapping for the respective project. You can view this by navigating to the project in Agile Hive > Project Settings > Issue Types.

Extended Information

In case you need more detailed information on Agile Hive Issue Hierarchy / SAFe® Hierarchy, please also refer to the pages listed below: