Skip to content
Blockline
Menu
HelpRead risk across spaces

Read risk across spaces

The risk board for a space shows one team’s epics. Across spaces shows every team’s at once, which is where a blocker in one space holds up an epic in another.

Pick a scope

Open Apps › Blockline. Pick the kind of scope under Scope, on one line with the picker and the buttons:

  • Spaces: one or more spaces;
  • Saved filter: any filter you can open. Your favourite filters and your own come first; on a site with many, type part of a name to search the rest. Two filters with one name show their owners (and their ids when the owner is the same too);
  • JQL: any query, such as labels = q4 AND statusCategory != Done. Blockline asks Jira to check it first; a query Jira would not accept, or one naming a space or value that does not exist, shows Jira’s own sentence under the line instead of an empty board, and the board you had stays on screen.

Press Show risk. The page remembers the scope you last showed and opens on it next time, for you only; a link that names a scope opens that one instead and is not remembered. A Jira admin can set a default scope for anyone who has not shown one yet.

The risk board under Apps, with the Scope picker on Spaces and DATA, MAPP, PAYC and STOR chosen, then headed “10 of 20 At risk or Blocked” with the counts 4 Blocked, 6 At risk, 2 Watch and 8 OK, “20 open deliverables” in the line under it, and Copy link, Download Excel and Download CSV at its right. Worst first, the first twelve rows: STOR-9, MAPP-5, PAYC-1 and DATA-1 Blocked by circular dependencies, STOR-11, MAPP-1, STOR-2, MAPP-6, PAYC-6 and STOR-1 At risk because they are overdue or wait on a late blocker, then STOR-10 and STOR-13 Watch. Each row shows the risk, the reason, the date with its source, the owner, the space and its open blockers with their spaces.
The risk board across four spaces, worst first

Blockers outside the scope are still read, one link out, so a cross-team blocker is never invisible.