Release Notes

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.

18 July 2022

New Features

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:

  • Roll-up value
    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.

Updates

  • 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 Enter or 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.

    Column limitations

    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.

    JQL limitations

    The Hierarchy for Jira custom fields cannot be used in JQL queries at this time.