The app in Jira

Besides its own page, TreeCraft appears on projects, issues, boards and dashboards, and in Rovo. Each place shows only what the person looking at it may see.

The app's own page

TreeCraft: Issue Hierarchies, under Apps in Jira's top navigation, lists every hierarchy you can open and holds the tools described in Getting started. Each hierarchy has its own address, so you can bookmark it or paste it into a ticket.

The page opens on the last hierarchy you opened. For people who haven't chosen one themselves, admins can set the hierarchy it opens on, in Defaults.

Project pages

Each project has a Hierarchies tab. It opens on a tree of the project's issues, named after the project (for example "PLAN issues"), with top-level issues in rank order and their children under them. An issue whose parent is in another project doesn't appear in this tree, but a query or a saved hierarchy can show it.

From the bar at the top you can open one of your hierarchies, create one with New, and reach Manage hierarchies, Scratchpad, Help and App settings under More.

The project's admins can set a default hierarchy for the tab. Everyone who can open that hierarchy then lands on it, and everyone else sees the project's issues.

Project settings

In the project's settings, the Hierarchy settings page lets the project's admins:

• Turn the app off on this project's pages, so the project's tab and its issues' panel no longer show the app;
• choose the Default hierarchy the project's tab opens on.

Only the project's admins can change these. A Jira admin can also leave a whole project out of the app in App access, and this page then says so.

The issue panel

Each issue has an In hierarchies panel. It lists the hierarchies you can open that hold the issue, and shows where the issue sits in the one you pick: the rows above it and the first 100 rows under it. When the issue sits in several places in that hierarchy, the panel says how many and shows the first. Open goes to the hierarchy on the app's page.

The panel remembers your last choice. When the issue isn't in that hierarchy, the panel picks a favorite, or else the first by name. Admins can choose which hierarchy it shows first for everyone, in Defaults.

The panel never says where an issue you can't see is placed, and it leaves out hierarchies in which the issue isn't shown to you anywhere. If it couldn't check every hierarchy in time, it says that others may hold the issue too.

Boards

Open as a hierarchy, in a board's menu, opens a dialog where you can open one of your hierarchies or select Create one from this board. That makes a hierarchy of the board's issues as a tree, with top-level issues in rank order and their children under them, kept up to date from the board's query.

Dashboards

You can add two gadgets to any Jira dashboard.

Hierarchy grid shows a hierarchy's rows and columns, read-only. In its settings you choose:

• the Hierarchy;
• the Columns: a saved view, or nothing to use the hierarchy's default for gadgets;
• Levels open, from the top level only to all;
• Rows shown.

Hierarchy cumulative flow charts how many of a hierarchy's issues were in each status, day by day, over the number of recent days you choose. Bands can follow status categories or single statuses. The gadget reads each issue's history from Jira.

Each person who views the dashboard sees only what they may see in the hierarchy, and nothing if they can't open it.

Rovo

On sites with Rovo, the Hierarchy helper agent works in Rovo chat. It offers two conversation starters:

• Build a hierarchy from this description: describe what you want in plain words. The agent suggests rules that use your site's projects, boards, fields and link types, and adds them to the hierarchy once you confirm. Adding rules requires Automate access, as it does in the Rules panel, and the rules go through the same checks. The agent adds up to 10 rules at a time, at the end of the top level.
• Summarize this part of a hierarchy: the agent reads an outline of the hierarchy, or of the part under one issue, with each issue's key, status, summary and assignee, and summarizes it. The outline holds up to 300 rows.

The agent acts as you. It can't run a write-back, change an issue, or widen anyone's access. A Restricted item row, an issue you can't browse with issues you can see under it, appears in the outline with no key or summary. Rovo runs on Atlassian's platform, so using the agent sends nothing outside Atlassian.

Jira's mobile apps

The app's pages are web pages inside Jira. Atlassian decides which of them its mobile apps show, so some may not open there. On a phone or tablet, use Jira in the browser.

Questions about the app? Write to info@plugincraft.ca.