How risk is judged
Blockline builds one graph from the dependency links in a view, gives every work item a date, and runs seven rules over every link. Each rule raises a level and a one-line reason. No level is ever shown without its reason, and the level is always written out, never shown by colour alone.
The four levels
From best to worst: OK, Watch, At risk and Blocked, in green, yellow, orange and red, the word always beside the colour.
The rules
- Circular dependency (Blocked): work items wait on each other in a loop.
- Late blocker (At risk): the blocker’s date is after the waiting work item’s date, or the blocker is still open past both: it lands today at the earliest. “MAPP-4 (overdue since …) blocks this story · 3 days past this story’s date”.
- Stalled blocker (At risk): the blocker is still To Do within 10 days of the waiting work item’s date. When the blocker has a date of its own on or before the waiting work item’s, and that date has not passed, it is planned on time and the flag is Watch: “MAPP-4 blocks STOR-6 · not started · planned for … · 9 days to its date”. A date that has passed is no plan: “MAPP-4 (overdue since …) blocks STOR-6 · not started · 7 days to its date” is At risk.
- Overdue (At risk): the work item’s own date has passed and it is not done: “Overdue since … · still in progress”.
- Unscheduled blocker (Watch): the waiting work item has a date, the blocker has none: “DATA-2 (no date) blocks STOR-5”.
- Long in progress (Watch): the blocker has been in progress for 14 days or more.
- Unowned blocker (Watch): the blocker has no assignee and is in no open sprint.
The 10 and 14 days are the defaults; a Jira admin can change both in Settings. “Long in progress” counts from the blocker’s last change of status category, so a blocker that moved to In Progress three weeks ago and stayed there is long in progress.
Epics inherit what their stories wait on
An epic waits on everything its stories and subtasks wait on outside the epic. A blocker two levels down therefore flags the epic too, and the reason names the child it came through: “PAYC-3 blocks STOR-4”. A link between two children of the same epic is internal and does not count against the epic.
Rules judge every dependency, direct or inherited, against the waiting work item’s own date.
Rolling up
A work item’s level is the worst of its own flags and its children’s levels, so a late story turns its epic At risk, and the epic turns its initiative At risk. The reason shown for a work item is its most severe flag. Among equals, another team’s blocker comes first: the conversation to have is with the team you wait on, so “PAYC-3 blocks STOR-4” leads over a story of your own past its sprint. Then the earliest date impact.
A deliverable that is itself past its date, while another reason leads, says so in its reason on the board, in the downloads and on the gadget: “… 45 days after this epic’s date (overdue since …)”, or, when the reason does not name the epic’s date, “… · this epic (overdue since …)” at its end. Its level stays the same.
How a reason reads
Each part of a reason is one fact, the parts joined by “·”. Whatever is overdue says so right after it, in brackets: “PAYC-4 (overdue since …) blocks STOR-7 · 9 days past this epic’s date”. A reason gives a date without where it came from; the Date column beside it says that. The blocker comes first, then the work item it blocks: “MAPP-4 (overdue since …) blocks STOR-6 · 3 days past its date”.
What counts as done
Any status whose status category is Done. Renamed and custom workflows count the same way, whatever their status names. Done work items raise no flag, and a done blocker clears the flags it caused.
When a view is too large
A view judges up to 5,000 work items at once, counting the scope, every child and every linked work item. Past that it says so, with about how many work items the scope reaches, and shows no numbers rather than partial ones. Narrow the scope to fewer spaces, a saved filter or JQL.
A board of spaces (a space’s Blockline tab, the dashboard gadget, spaces picked on the Apps page) reads the spaces’ open work items and the work items done in the last 90 days, not every work item the spaces ever had, so a space with years of history still fits. Done work items raise no flag, and a done blocker is still read when an open work item links to it, so it still clears its flags. Its count of done deliverables covers those 90 days. A saved filter or JQL is read exactly as written.