Here are the changes we document in the Release Notes:
- New Features - Brand new functionality designed to make Hierarchy for Jira exceptional.
- Updates - Changes we’ve made, large and small, that we want you to be aware of.
- Bug Fixes - Issues we’ve resolved to make the app work as intended.
14 November 2022
- We made the filter name persist throughout the app experience. Now when you open Hierarchy for Jira filter or when the page is refreshed, the name of the filter in use consistently displays in the Select project or filter field.
We made the Hierarchy Tree view responsive to your screen resolution to improve the app experience for those using large monitors.
Thanks for the suggestion! 💡
We made this update because you, our users, requested it on the Hierarchy for Jira Nolt board.
Visit the board to suggest your own ideas for new features and app improvements, and vote for the best ideas you see. We're listening!
- Fixed an issue that caused custom-issue icons to display incorrectly in the Hierarchy Tree view for some project types.
- Fixed an issue that caused menu items to collapse and display incorrectly when the JQL editor was in use.
02 November 2022
- Fixed an issue that prevented the Hierarchy Tree view from loading properly (infinite loop) when users made a child issue the parent of its parent.
12 October 2022
The Active Hierarchy dropdown was improved and moved to a more useful place within the app to give you the ability to customize the way your issues display in the app's Hierarchy Tree view. Now you can opt to filter the view by specific link types in order to see issues linked in ways other than Jira's default hierarchy view.
Click Active Hierarchy to browse the filter options via the dropdown list as well as the show/hide options for Jira's default hierarchy view. The link types that appear in the drop-down list reflect those that exist in your instance. And with this release, existing Hierarchy for Jira Cloud users can rename the previously configured "Agile Docs Parent" link to any preferred name that better suits their needs.
How filtering used to work
Previous to this feature release, the Hierarchy Tree view only allowed users to view Jira's default hierarchy (Epics > Stories > Subtasks) or the Agile Docs Parent view, which is a custom link type that displays both parent-child linkages as well as Jira's default hierarchy. This new feature allows users to hide the default hierarchy from the Hierarchy Tree view.
The new hierarchy filtering option is also available at the issue level in the progress summary detail.
- Links to helpful resources have been added to a Help dropdown.
Links contained in the dropdown list include the following:
- Getting started
- Contact support
- Suggest a feature
- Write a review
13 September 2022
- A supplemental video demonstration has been added to Creating Custom Issue Hierarchies. Same info, different format.
We improved the text search so that returned search results are highlighted. Parent and child issues are also visible in search results, explained as follows.
For example, if you search for a top-level issue, the search results display all existing child issues, e.g., PE-20 and PE-21 below:
If you search for a child issue, the search results include the issue's parent as well as the parent's parent:
If a search key returns an issue at the lowest child level, e.g., PE-21 in the image above, the search results only display parent and child issues, not sibling issues (other same-level child issues that share the same parent).
- Fixed an issue that caused board issues to sort and display inconsistently while using predefined filters versus the issue display of an equivalent JQL query.
30 August 2022
New time unit 📅
The week time unit has been added to the app for improved progress feedback and clearer estimations.
Note: One week is equal to five workdays (1w = 5d).
Original Estimate Progress: Improvements for estimations and reports 💪
You now have the ability to track progress against original effort estimates.
Access the new option in the Settings menu by clicking .
There are a few reasons we added this feature, all of which relate to limitations within native Jira tracking and reporting. For example:
- In Jira, reports are only available for specific scrum boards, making it impossible to track progress outside of sprint.
- Native Jira progress tracking does not communicate whether completed sprint work is under- or over-committed.
- Measuring your team's actual capacity is difficult in Jira because efforts that fail to exactly match original estimate values aren't taken into consideration in regard to actual sprint work. Valuable information like time spent and remaining estimates can be beneficial to spotting potential delays and making accurate projections of completion dates.
With the new time-tracking perspective of Original Estimate Progress, you can easily evaluate and compare your project's sprint-completion numbers to the original estimates, which allows you to more accurately gauge velocity and fine-tune adjustments for subsequent sprints.
See Monitor Progress to learn how to use the Hierarchy for Jira's Original Estimate Progress and Current Estimate Progress to improve your estimations and reports.
- We changed the Status Category column header to Status.
18 July 2022
Brand new look and feel 🕶️
Hierarchy for Jira just got a major makeover! There are so many new things to show you!
Not only does the app look better, but it's more customizable and more eloquently nested within Jira, which allows it to work much faster than the previous version.
Search with JQL 🔎
JQL (Jira Query Language) search is now available! Use Atlassian's handy range of fields, operators, and values to customize your search results like never before. Once you’ve entered a JQL query (or selected a filter), the app returns all of the issues in a nested tree view.
In addition to JQL search, basic project and filter searches are also available. Toggle between the two options by clicking Switch to JQL and Switch to Basic.
This update to Hierarchy for Jira changes the way filters display issues. If your filters only includes issues at the top level, you need to edit the filter to include ALL issues in your hierarchy. The previous version of the app displayed children issues automatically, but the latest version of the app applies filter logic more strictly.
To make sure the tree view works as intended, we’d recommend refining the JQL filter to query all issues and their subordinate issues, such as this:
parentEpic in (AP-9,AP-7,AP-123)
Please note! ⚠️
Hierarchy custom fields cannot be used in JQL searches at this time.
Search with text 🕵️
Text search for key and summary details is also now available! Returned items populate in the table view and include the parent issue.
New sum option for issue estimates 🔥
Now there's a new way to view and measure your project efforts called Sum-up values.
From the table view, click the Settings cog to select your estimation preferences.
The new option, Sum-up, is the total value of child-issue estimates (story points or time) INCLUDING parent estimates.
To illustrate the differences between the two estimate options, see the following examples:
If a parent issue has no story-point value assigned, Hierarchy for Jira totals the story points from all of the child issues directly below it and adds that total number of story points to the parent issue. If a parent issue has an assigned story-point value, Hierarchy for Jira takes no action.
- Sum-up value
The story-point sum for parent and child issues, which appears on the parent issue.
The impact of filters
Roll-up and Sum-up values, for both story-point and time estimates, are calculated based on view parameters. If a filter is applied to hide issues, those filtered/hidden issues are not included in Roll- or Sum-up values.
Use table context to create JQL filters 👀
There's a new Scope option at the footer of the table view that, when you hover over it, shows you the current view's JQL query.
Click Scope to copy the query to your clipboard. With the query copied, you can navigate to the Filters section and create a new filter just by pasting the query, naming it, and then saving the new filter.
All issues in your hierarchy must now be included in your filter 💡
In the previous version of Hierarchy for Jira, your filter only needed to include the issues at the top level, and the app would retrieve and display all children issues. In this new version of the app, all issues in your hierarchy must be included in your filter.
- Super speed! ⚡ Hierarchy for Jira works faster than ever—no more long waits for loading screens!
You can now edit issue details within Jira—no more clunky new tabs to deal with. Simply click an issue-key link, and edit within Jira, just as you'd expect.
Don't forget to refresh! 🔄
Any changes made to an issue from the issue view will not display in the table until you click Refresh, either above the table or in the table footer.
Refresh above the table:
Refresh in the footer:
Edit the Summary field directly from the table view by double-clicking the existing summary. Press
Enteror click outside of the cell to save the new summary.
Using the new UI, you can customize columns to track only the information you need and nothing else.
Simply click the add icon to the right of the column headers, then select new columns to add one at a time.
To remove a column, hover over a column name and click the small x.
Some columns, by default, are permanent and cannot be removed. Also, columns cannot be reordered at this time.
Viewing options for Hierarchy custom fields have changed. 👀
Previously, custom fields could be viewed directly on the issue details view. In this new version, you need to click Click to view on Progress summary to expand the custom fields section.
The Hierarchy for Jira custom fields cannot be used in JQL queries at this time.