See what holds up an epic
Lesson 4 of 4
You have linked blockers and given the work dates. This lesson shows where Blockline says what holds up an epic: on the work item, in the space and across spaces. It needs nothing set up. A Jira admin can change how it judges later in Settings.
Risk is judged as you see it. Blockline reads Jira as the person looking, with their permissions. A link to a work item you cannot open is left out, as in Jira, so a colleague with wider access may see a different level, reason or data health for the same epic, and your “changed since your last visit” is yours alone. Permissions and data says more.
Where to find it
Blockline is in each of these places in Jira:
- Apps › Blockline in Jira’s sidebar: the risk board for any set of spaces, a saved filter or a JQL query. See Read risk across spaces.
- A Blockline tab in every space, beside the space’s own tabs: under More when Jira’s tab bar is full. See In a space.
- The Details column of a work item with dependency links or sub-tasks, and of every epic and initiative: a Blockline group with its level and reason. See On a work item.
- The Blockline panel on any work item: open it from View app actions, the hexagon under the work item’s title. See On a work item.
- The Blockline gadget on any dashboard: add it in the dashboard’s Edit view like any other gadget. See Put risk on a dashboard.
Jira admins find its settings under Jira settings › Apps › Blockline settings. See Settings.


On a work item
The Details column. A work item with dependency links, a work item with sub-tasks, and every epic and initiative has a Blockline group in the right-hand column, laid out as Jira’s own Details: rows for its Risk, its Date with the source, since when it has been at that level for you (for an open epic), and what it waits on and holds up, with the first few keys. Under the rows, the reason in the colour of its level. A blocker that is on time itself but makes other work late leads with that, at the level it causes: “At risk: Makes 2 work items late: MAPP-1 by 45 days (MAPP-3 waits on it), STOR-1 by 6 days (STOR-4 waits on it)”, then “Its own risk: OK. …”. Last, the age of the answer and Recalculate, bottom left. It is there as soon as the app is installed, with nothing to add; Jira may show the group closed until you open it. A work item with no links and no sub-tasks below epic level can neither wait on anything nor hold anything up, so it has no group; its panel still opens.
The Blockline panel. Open it from View app actions, the hexagon under the work item’s title. On a site Jira has not moved to that row yet, it is a named Blockline button in the same place. The panel shows:
- the work item’s own level and the one-line reason for it, such as PAYC-3 blocking STOR-4 and landing 6 days after this epic’s date, or “OK · Waits on nothing” for a work item that waits on nothing, itself or inside it. A story with no date of its own cannot be late itself, so when its epic is late because of what the story waits on, the story says so: “No date of its own. Through this story, STOR-1 is At risk: PAYC-3 blocks STOR-4 · … · 6 days after STOR-1’s date”. A blocker that is OK or Watch itself but makes other work late leads with what it makes late, at the level it causes (“At risk · Makes 2 work items late: MAPP-1 by 45 days (MAPP-3 waits on it), STOR-1 by 6 days (STOR-4 waits on it)”), with “Its own risk: OK. Nothing it waits on is late, …” under it (“Its own risk: OK. Waits on nothing” when it waits on nothing); one small line follows with its date, since when it has been at its level and what happened that day, from Jira’s change log (“At risk since …, when PAYC-3’s due date moved past this epic’s date”; left out when the log cannot say), and how many work items it waits on and holds up;
- Waiting on: every work item it waits on, including what its stories and subtasks wait on outside it, each with the child it comes through (“blocks STOR-4”) and whom it is assigned to, its status, date, and the level and reasons that blocker causes on the work item, on its stories, and on its epic through it;
- Holding up: every work item that waits on this one, with the risk this work item causes it, so the team that blocks sees whom it is holding back;

Show dependency map draws the chain upstream of the work item.
In a space
Open the Blockline tab at the top of the space (under More when the space has many tabs). The page opens on the answer: how many deliverables are At risk or Blocked (“4 of 8 At risk or Blocked”), the count at each level, then a small line with how many open deliverables and work items were read and how old the answer is.
The risk board lists every open deliverable, worst first: the work, its level, the top reason, its date with the source under it, its owner, its space (when there are several; its name opens Blockline’s tab in that space) and its open blockers with the spaces they are in (“3 · DATA, MAPP, PAYC”: which teams to call). Filter by space, risk, owner and type with the chips over the board (a picked one says its value, “Risk: At risk or worse”). Space and Owner pick several (“Space: STOR, PAYC”), and a row matches any one picked; Risk offers Watch or worse, At risk or worse, and Blocked. When every deliverable is of one work type, there is no Type chip. A space narrows the board at once, with nothing read again. Choose an order under Sort by, and press Map on any row with a blocker for its dependency map. A board of five rows or fewer keeps only the Risk filter and Sort by. Copy link and Download sit above the tabs, at the right of the count of deliverables at risk, and save the tab you have open.
More tabs. Beside the risk board are Holding up others, the blocking team’s view (See which teams hold you up), the Team matrix, and Data health (Fix gaps in your data). All the tabs come from the same build, so switching between them is instant.
What changed. A row that changed since your last visit to the board says so under its level: what it was (“Was Watch”), “New on this board” for one created or reopened since, or “Reason changed” when the level is the same but the reason is not (hover for what it was). A deliverable whose own date moved says so on a line of its own: “Date moved” with the old date and the new. The line under the counts says how many changed, and Changed since my last visit in the filter row shows only those. A visit ends after an hour without opening that board; your first visit marks nothing.
Freshness
Every view says how old it is (“Updated 3 min ago”), and every page and panel has a Recalculate button beside it. On a dashboard the gadget has none of its own: Jira’s reload icon on the gadget, or the dashboard’s Refresh, recalculates it. Results are kept for up to 10 minutes per person and view, and reloading the page shows the kept result. Recalculate rebuilds the view; in the first minute after a build (ten seconds on a work item) it would show that same build, so in its place the words say when it is back: “Recalculate in 1 min”, then “Recalculate in a few seconds”.
Every Blockline site shares one hourly allowance of Jira requests, so each person can build only so many fresh views in an hour. Past that, the views they opened in the last hour still show, with a line saying when fresh builds are back. Work item panels and the Details column are not limited, and nobody else is affected.