Initiatives (issue hierarchy)
Using Initiatives as a data source
If you want to create a chart for one or multiple Initiatives, Features, Solutions, or another entity above epics, use the Issue hierarchy data source.
There are two options: Parent issues and Issue links.
Parent issues
Select Issue hierarchy > Parent issue in the Data sources section.
Use this option if you have the Parent/Child field in your Jira configuration. It allows you to track the progress of Initiatives, Features, or Solutions.
Settings
Hierarchy depth (1–3)
Level 1 – only direct children of the selected parent issue(s).
Level 2 – includes issues that are two levels below the parent.
Level 3 – includes issues that are three levels below the parent.
Selection methods
Basic: choose the parent issue (e.g., Initiative, Feature) from the dropdown. If it doesn’t appear, start typing its name to search. To add multiple parent issues, click Add issue.
JQL: define parent issues using a custom JQL query.
Example
In the example below, Initiative #1 (1️⃣) has a Parent/Child field (2️⃣) and is directly related to a set of epics (3️⃣). With hierarchy depth set to 2, the chart scope includes the work items under these epics.
You can include additional parent issues by clicking Add issues (4️⃣).
Issue links
Select Issue hierarchy > Issue links in the Data sources section.
Use this option if your hierarchy is built on custom issue types above epics: for example, Initiatives or Program Epics linked to Epics.
Settings
Hierarchy depth (1 or 2)
Level 1 – includes child issues of the epics directly linked to the selected Initiative(s).
Level 2 – includes child issues of the epics linked to the selected Initiative(s) through an intermediate entity.
Link type
Select a link type from your Jira instance (e.g., is parent of / is child of, is connected to / connects to).
Selection methods
Basic: choose the parent issue (e.g., Initiative, Feature) from the dropdown. If it doesn’t appear, start typing its name to search. To add multiple parent issues, click Add issue.
JQL: define parent issues using a custom JQL query.
Example
In the example below, Initiative #2 (1️⃣) is connected through the Issue Links field (2️⃣) with the link type Parent of (3️⃣) to a set of epics (6). With hierarchy depth set to 1 (4️⃣), the chart scope includes all work items under these epics (6️⃣).
You can add more issues besides Initiative #2 by clicking Add issues (5️⃣).