Drill-down

Three things in the tile take you further than the number in front of you: the issue key on every issue row, the N unest. badge on a row with children, and the +N … chip that appears on very large trees. The value in the Σ column itself is plain text — it is the answer, not a link.

Issue links

Every issue key in the tree is a link — click it and the issue opens in Jira in a new tab. The provenance of any number is one click away, which is the difference between a report people trust and a report people re-check in JQL.

The unest. badge

The amber N unest. badge sits on rows whose subtree contains issues with no value in the field; it counts those issues, not the containers above them (the exact rule is in How rollups work).

On a row with children the badge is a button. Click it and the gadget switches to unestimated only: the tree expands and prunes to exactly the branches that lead to an unestimated issue, and the line [ unestimated only ] · Show all appears under the header. Open the issues, estimate them, click Show all to return.

On a single issue the badge is plain information — that row is the unestimated item, so there is nothing further to drill into. Hovering it says so: No value in the selected field on this issue. Under the count operation there is no badge at all, since nothing is estimated or unestimated there.

This turns the badge from a passive statistic into a grooming workflow: before sprint planning, click the badge on your epic, and you are looking at precisely the work that still needs sizing. Two details to know while you work through the list:

• The tile shows the stored copy of your projects, so an estimate you enter in Jira appears after the next hourly update, not the moment you save it. When the last one is done, the mode reports No unestimated issues — everything here is estimated.
• The mode is remembered in your browser for 12 hours, together with the rows you opened and your scroll position, so a reload brings the tile back the way you left it.

Loading more rows

On a very large portfolio the tile does not send every row at once. Every row you see carries totals computed over its whole subtree, but the deepest rows are held back until you ask for them: a row whose children were held back carries a +N … chip in its right-hand column (click to load them — totals already include them), and how it’s counted in the footer counts what is currently not listed. Click the chip and exactly that branch loads, with a small spinner while it is on its way. Within one level, 100 rows are shown at a time, then a Show 100 more row pages through the rest. The 50,000-issue read limit and how detail loads on demand are described under Very large portfolios.

When a branch cannot be loaded, the notice says why, and its control matches the reason. Could not load these rows — try again in a moment, with a Try again link, appears only when trying again can help: Jira did not answer the permission check, or the request itself failed. Every other refusal names its cause — the app still needs your permission, you have no Browse permission on these projects, the field the gadget counts is no longer in Jira, the saved filter behind the gadget could not be opened, the subscription is inactive — and offers Refresh the gadget instead. If the gadget itself asked for rows that do not exist, the notice links to support.

A branch can also arrive incomplete. When the stored copy was read up to its size cap, the rows under the parent are some of them, not all, and asking again returns the same set. The row then carries a partial chip with no click, and the numbers on that row cover only what was read.

In Hierarchy Progress there is no +N … chip: a row whose children were all held back has an ordinary ▸ that loads them as it opens, and a row delivered in part shows a load N more link beside its key.

Keyboard

The rows share one tab stop. Press Tab to reach the current row, then:

• ↑ / ↓ move between rows; Home / End jump to the first and last row.
• → expands the focused row, or moves down when there is nothing left to expand; ← collapses it, or moves to the parent when it is already closed.
• Enter or Space expands or collapses a row with children, loads the next page on a Show 100 more row, and opens the issue in Jira on a single issue. Project rows and the two containers have no issue to open. On a row whose children are still held back, Enter opens that issue too — Tab to its +N … chip and press Enter to load the rows instead.
• Tab once more reaches the row’s issue key, its +N … chip or its unest. badge; Enter or Space there opens the issue, loads the held-back rows, or enters unestimated only.

Screen readers announce the table as a tree grid, with each row’s level and position in its group.