12. Hierarchy Report - 6.5.7

The Hierarchy report displays the list of linked issues in a hierarchical relationship for a defined hierarchical structure. The issue list is fetched based on the filter condition applied at the first hierarchy level. The next level of issues gets fetched regardless of the filter condition. The various hierarchical report types available are:

1. Issue → Sub-Task

2. Epic → Issue

3. Epic → Issue → Sub-Task

4. Issues → Linked Issue

5. Epic → Linked Epic → Issue

6. Issue → Linked Epic → Issue

How do the Hierarchy Report types work?

1. Issue → Sub-Task

• Step 1: All the Standard Issues (Non Sub-tasks) which satisfy the filter for the report will be fetched.

• Step 2: All the Sub-tasks for the issues found in step 1 will be fetched regardless of the filter condition.

2. Epic → Issue

• Step 1: All the Epics which satisfy the filter for the report will be fetched.

• Step 2: All the Stories for the Epics found in step 1 will be fetched, regardless of the filter condition.

3. Epic → Issue → Sub-Task

• Step 1: All the Epics which satisfy the filter for the report will be fetched.

• Step 2: All the Stories for the Epics found in step 1 will be fetched, regardless of the filter condition.

• Step 3: All the Sub-tasks for the Stories found in step 2 will be fetched, regardless of the filter condition.

4. Issues → Linked Issue

• Step 1: All the Issues (Including Sub-Tasks) which satisfy the filter for the report will be fetched.

• Step 2: All the issues linked to the issues found in step 1 will be fetched regardless of the filter condition.

5. Epic → Linked Epic → Issue

• Step 1: All the Epics which satisfy the filter for the report will be fetched.

• Step 2: All the Epics linked to the Epics found in step 1 will be fetched, regardless of the filter condition.

• Step 3: All the Issues for the linked Epics found in step 2 will be fetched, regardless of the filter condition.

6. Issue > Linked Epic > Issue

• Step 1: All the Issues which satisfy the filter for the report will be fetched.

• Step 2: All the Epics linked to the Issues found in step 1 will be fetched, regardless of the filter condition.

• Step 3: All the Issues for the linked Epics found in step 2 will be fetched, regardless of the filter condition.

Creating Hierarchy Report

To create a Hierarchy report, follow the steps below:

1. Click New Report > Custom Report to open the Report Designer interface.

2. Select the report Type as Hierarchy.

3. Select the type of report to view from the drop-down Hierarchy Type. The Issue → Sub-Task report is selected by default.

• For the report-type Issue → Sub-Task, to include the issues without sub-tasks, select Include issues without sub-tasks.

  Open

  

• For the report-type Issue → Linked Issue, Epic → Linked Epic → Issue, and Issue > Linked Epic > Issue, to view the link type, select Include link type.

  Open

  

4. To view the required fields in the report, add the fields from the left panel by clicking ‘+' sign next to the field name. The fields list contains all standard Jira fields, custom Jira fields for the instance, and calculated fields created using Reports and Timesheets for Jira app. The fields with an symbol are explained in detail here. Fields can be dragged and dropped in the Fields section to rearrange the columns.

5. Specify filter criteria to search for issues using a JQL statement, Jira Favorite Filter, or Reports Custom Filter builder in the Issues Search panel.

6. Click Run to view the results in the bottom pane.

7. Click Save to save the report for future use. To view saved reports, navigate to My Area → My Reports.

Sample Hierarchy Reports

Below are a few sample reports with configurations and results. More sample reports can be found at Help → Sample Reports.

Hierarchy Type: Epic → Issue → Sub-Task [The report displays the hierarchical structure of Epics with linked stories and with status In progress.]

Hierarchy Type: Issue → Linked Issue [The report displays the hierarchical structure of Issues with Linked issues and the Link type.]