Only project-related statuses are available to select when using the Jira project as a data source

We limited the list of statuses that users can see and select to those related to the selected Jira projects, making it easier to navigate between statuses:

Open

3 levels of hierarchy depth and a clear definition of what will be shown on the chart, when using the Issues hierarchy data source

After several conversations with our users, we realized that the interface for “Initiatives” can be a bit confusing. We identified three main issues and their corresponding solutions:

• Not everyone uses the term “Initiatives,” so we renamed the data source type to “Issue hierarchies,” which aligns more closely with the Atlassian glossary.

  Open

  

• Initiatives aren’t always parents of Epics, which in turn aren’t always parents of Stories. To accommodate different structures, we introduced more flexibility by allowing you to choose the level from which to display child work items.

  Open

  

• Two levels weren’t enough, so we’ve added a third.

  Open

  

Hierarchies built using issue linking remain supported, with an enhanced tooltip to improve usability and encourage adoption.

Open

JQL filter to select multiple items in the Issues hierarchy data source

When you need to select 10 or more Initiatives, Features, or Solutions to track your delivery progress in a Scaled Agile environment, adding them one by one becomes cumbersome. Starting with this version, we’ve added the ability to define parent issues in your issue hierarchy using a JQL query.

For your convenience, standard issue types and sub-tasks are excluded by default, so you only need to define the project where your Initiatives are stored.

Open

However, you can always specify the issue type in the JQL input and view the results accordingly.

Ability to select completed work items in the Issues hierarchy data source

You can now select completed work items to create charts for past projects, enabling pattern analysis and reporting.