Feature Comparison
Use this page to compare the features of the old version of Hierarchy for Jira to the newest version of the app.
| Feature | Old Version | New Version |
|---|---|---|
Table filters - Pulling issues to the table view | You can only select Projects, Releases, or Saved Filters. | You can select Projects, Releases, and Saved Filters. You can also make JQL searches directly from the app. |
Link-based hierarchy | You can create custom hierarchies using the Agile Docs Parent link type. | You can define any link type to create Creating Custom Issue Hierarchies. You can view linked issues in the nested tree structure without the default Jira Hierarchy. You can change the link direction to reverse the hierarchical order. |
Track Story Point Progress | The app uses Roll-up : If a parent issue has no story-point value assigned, Hierarchy for Jira totals the story points from all child issues directly below it and adds the 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. | You can choose which estimate configuration suits your needs: Roll-up values Sum-up values |
| Track Progress by Time |  Not available | Time tracking allows users to measure progress against Current Estimates or Original Estimates. |
Issue details view - View and edit issue details | Clicking on the issue key will open a new tab. If users want to edit the issue details and reflect the changes in Hierarchy for Jira, they must navigate back to the app and refresh the browser. | Users can open the issue details view modal directly from the app. Once they edit the issue fields, simply reload the table to see the latest updates. |
H4J custom fields from the issue details view | Users have access to several rolled-up estimate fields (numeric fields), which can be configured to display inside each issue. |
|
Issue Search |
| Search for issues in the table by issue key or summary. |
Quick Filter |
| You can apply additional filtering layers to the hierarchy table by creating JQL queries and saving them as quick filters. |