Using Filters

With Hierarchy for Jira, you can use filters and set the top-level issues to determine the array and arrangement of the issues you see.

Using a saved filter

Use your saved filters to determine the issues displayed in a Hierarchy for Jira tree view.

  1. Create a filter you want to use if you do not already have one saved.

  2. Select Apps from the menu bar, then click Hierarchy for Jira.

  3. Select your top-level issue type from the menu.
    (For more information on the choices in this menu, check out the next section, All issues vs all top-level issues.)

  4. Click Select Project or Filter, scroll down to Saved Filters, then select your filter.
    Hierarchy for Jira displays the issues.

All issues vs all top-level issues

Hierarchy for Jira lets you select a top-level issue type to pair with your filter. If you’re using an issue hierarchy structure that has epics at the top level, you might choose to select Epic as your top-level issue type.

With Epic chosen, Hierarchy for Jira loads all epics in your filter at the top level of your tree view, then loads all children of those epics underneath them, and so on.

But what if you want to show multiple issue types at the top level, or you have issues that are not located under epics in some projects? You have two additional options: All Top Level Issues or All Issues In Filter.

All top-level issues

This option loads all issues which have no parent to be at the top level of the tree view. With this setting, Hierarchy for Jira only loads issues in your filter at the top level if they have no parent and would not be displayed elsewhere.

For example, if a story issue in your filter has a parent epic, it is not loaded at the top level. It is only loaded under its parent epic. If the story has no parent issue, though, it is displayed at the top level.

Use this setting if you want a tree view of all issues in your filter, with no repeats or "missing" issues.

All issues in the filter

This approach loads all issues in your filter at the top level, regardless of if they have a parent or not.

If a story in your filter has a parent epic, and that epic is also in your filter, both the story and the epic are loaded at the top level.

This means the story is loaded at the top level AND as a child of the epic. This may not be what you want. If you only want to show the story under its parent epic and not at the top level, you should choose a different option.

Using cross-project filters

Use the power of cross-project filters to track the progress of multiple projects, releases, and/or teams on a single page. Great for sharing with stakeholders!

  1. Create a filter for your top-level issue type across multiple projects and releases.
    In this example, we use our filter All Releases:

  2. Open up that filter directly in Hierarchy for Jira (Apps>Hierarchy for Jira) to track the progress of your filtered issues on a single page.

  3. Share this page with stakeholders by clicking Copy Link to save a shareable link to your clipboard.