Docs › Follow work through links
Read a 0/1 rollup
Which boards have this. Counts on linked work belong to boards whose own type sits outside every backlog. On a board of backlog items the link chip keeps the linked items and their states and drops the counts, as See exactly which items a count came from.
"Tell the claimant where their settlement has got to" links one backlog item, "Show settlement status to the claimant", which nobody has broken down yet. Its rollup reads 0/1 Backlog items, because the linked item is one unit of work whose state is known, so it counts as itself, and the word follows what was counted. When the linked item is a Feature or an Epic, the unit says so: 0/1 Features, never a silently borrowed "Backlog items".
Steps
- Find the card on the board over business requests; in the demo it sits in Triage.
- Look at the chip row along the foot of the card, without expanding anything. The count reads 0/1: the undecomposed item itself, not yet done. It carries no progress bar, and that is deliberate: one item is either done or it is not, so there is no proportion for a bar to show.
- Select the count. The flyout opens on the linked item's own row. There is nothing beneath it yet, because it has no children for the count to judge.
- Select the linked item's title to open it in the native work item form and break it down there.
What you should see
A quiet 0/1 where richer cards carry a bar and a larger fraction, and a flyout whose only row is the linked item itself. Once the linked item has children, closing the form is enough: the board asks for a refresh, the rollup notices that the linked item's revision moved, and the fraction grows to count the new children instead of the item, and the bar appears with them, since from that moment the count can be partial. Nothing on the card had to be reconfigured.
The same goes for a card linking two undecomposed items: there the bar is drawn, because 1/2 is a proportion and nothing else on the card face says how many of the two are done.
Notes
Beside a linked item that does have backlog items, an undecomposed Feature or Epic stays out of the card's total, which then counts backlog items only. It keeps its 0/1 on its own heading in the breakdown, the breakdown names it at its level (Features 0/1), and the rollup's tooltip says that the count leaves it out. What the rollup counts explains why the total does not simply add it.
Once children exist, the linked item's own state leaves the count again, because descendants are what is judged, and the item goes back to being their container. A genuine 0/0 still exists, and still means something: it appears when nothing under the linked item can enter the count, most pointedly when its only children were Removed. The structure existed and its owner deliberately killed it; counting the container again would resurrect that branch as pending work. (Children all excluded for other reported reasons, such as another project or a state no process can judge, read the same way, each dimmed into the flyout with its reason.)