Skip to content
Menu

Which epics are at risk, and why.

From the Blocks links your teams already make. Nothing to set up.

Privacy first. No servers. Changes nothing in Jira.

The Blockline tab in the Storefront space, on the Risk board, headed “4 of 8 At risk or Blocked” with the counts 1 Blocked, 3 At risk, 2 Watch and 2 OK, “8 open deliverables” in the line under it, and Copy link and the Download menu at its right. Worst first: STOR-9 Returns portal Blocked by a circular dependency with a Mobile Apps work item, STOR-11 Guest checkout At risk because it is overdue, STOR-2 Gift cards and STOR-1 Holiday checkout At risk because of late blockers in PAYC, STOR-10 Order tracking and STOR-13 Store pickup Watch because a blocker has no date, then STOR-12 One-click reorder and STOR-3 Search facets OK, on track. Each row shows the risk, the reason, the date, the owner and the open blockers with their spaces, and Map.
The Blockline tab in every space. Map on a row opens its chain.

Every space, one board

Pick spaces, a saved filter or JQL. Every deliverable worst first, with its reason, its date and what it waits on.

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 and the Download menu 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.
Every deliverable across the spaces, worst first, with its reason, its date and what it waits on.
The Team matrix tab of Apps › Blockline over DATA, MAPP, PAYC and STOR, under the page heading and the scope row: each cell counts the row space’s open dependencies on the column space with the worst risk among them, for example STOR on PAYC 4 At risk, STOR on MAPP 2 Blocked, STOR on DATA 3 Watch. The STOR to PAYC cell is picked, listing STOR-4 waiting on PAYC-3, STOR-7 on PAYC-4 and STOR-14 on PAYC-10, all At risk, and STOR-17 on PAYC-9, OK, each with its reason.
Which space waits on which, and how badly, one cell for each pair; pick one to list the dependencies.
The Data health tab of Apps › Blockline over DATA, MAPP, PAYC and STOR, under the page heading and the scope row: Blockers with no date, 4 of 16, DATA-2, DATA-4, DATA-9 and DATA-10, and Blockers with no assignee, 2 of 16, DATA-4 and DATA-10, each with an Open in work item search link, then Deliverables with no date, 0 of 20.
The blockers with no date or no assignee, named, with a link to fix them in work item search.

The chain upstream of one epic

What it waits on, through its stories, three levels upstream, with the path that ends latest highlighted.

The dependency map of STOR-1, Holiday checkout, At risk, 6 days late, at the right. Its stories STOR-4, STOR-5 and STOR-6 are in the middle and what they wait on to the left: PAYC-3 Refund API At risk, 6 days late, DATA-2 Watch, no date, and MAPP-4 OK, on track, and further left DATA-4 Warehouse export, Watch, no assignee. Each box names its assignee, Unassigned on DATA-4. The path through PAYC-3 and STOR-4 is blue, the one that ends latest.
Show dependency map on the work item panel, or Map on any board row.

Every flag explains itself

The blocker, its date and where the date came from, on the epic itself.

The Blockline panel on the epic STOR-1, Holiday checkout: a grey line with its own date (a due date), at risk since the day PAYC-3 was linked as a blocker, waiting on 3 and holding up nothing, with the age and Recalculate at its right; then At risk, PAYC-3 blocks STOR-4 and lands 6 days after this epic’s date. Waiting on lists the three work items in other spaces it waits on, each with the story it blocks, its assignee, status, date, risk and reason: PAYC-3 Refund API At risk, DATA-2 Order events stream Watch with no date, and MAPP-4 Shared address SDK OK, on track. Under it, Holding up says nothing waits on this work item, then Show dependency map and Open in Blockline.
Work item panel: open it from View app actions (the hexagon under the title) on any work item.

The team holding others up sees it too

A space’s tab says how many deliverables in other spaces its work makes late, and lists them by its own work item, with how late.

Blockline in the Payments Core space, on Holding up others (7). Each row is one line: the PAYC work item, its assignee, the other team’s deliverable it holds up and that team’s space, when it is needed and the effect: PAYC-3 makes MAPP-1 45 days late and STOR-1 6 days late, PAYC-4 makes STOR-2 6 days late, PAYC-5 is in a circular dependency with DATA-1, Blocked, PAYC-10 makes MAPP-5 and STOR-9 20 days late, and PAYC-11 makes MAPP-6 3 days late.
The Holding up others tab, on a space’s Blockline tab.

What is at risk, on a dashboard

The deliverables At risk or Blocked in the spaces you choose, each with its date and reason, and Open in Blockline for the whole board.

The Blockline gadget across a Jira dashboard named Delivery risk: a grey first line, “10 of 20 At risk or Blocked · in DATA, MAPP, PAYC, STOR”, then all ten, worst first, each with its date and reason: four Blocked by a circular dependency, STOR-9, MAPP-5, PAYC-1 and DATA-1, then six At risk, from STOR-11, overdue, to STOR-1, where PAYC-3 blocks STOR-4, the age, “Updated just now”, at the right of the first line, and Open in Blockline under the list.
The Blockline gadget, added to a dashboard like any other.

How risk is judged

  • Every flag says why

    One line per flag: the blocker, when it lands and how late that makes the epic. Every date says where it came from, such as its due date or its sprint end.

  • Stories count toward their epic

    An epic waits on everything its stories wait on outside it, and takes the worst level among them.

  • “Done” follows Jira’s status category

    Done work items raise nothing, and a done blocker clears the flags it caused.

  • You only see work items you can open

    Blockline reads Jira as the person viewing, with that person’s permissions.

All seven rules →

What you get

Views

On every work item
What it waits on, what waits on it, and what its stories wait on.
Risk board
Every deliverable, worst first, with filters, sorting and a saved scope.
Team matrix
Which space waits on which, with the worst risk per pair.
Data health
Undated and unowned blockers, each list a link into Jira’s work item search to fix them.
On the dashboard
The epics At risk or Blocked in the spaces you choose.
The map
The chain upstream of one epic, a level on every node, the path that ends latest in blue.

Also

Works on install
Blocks links, due dates and epics are read as they are.
Dates that say where they came from
Due date, Target end, sprint end, release date or the latest child.
Excel and CSV
The board, the matrix and every dependency, as filtered.
What changed
The rows that changed since you last looked, and what they were.
Links you can share
Copy link opens the same board, with its spaces, filters and sort.
Always says when
Every view says when it was updated. Recalculate rebuilds it.
Admins choose
Link types, date sources, thresholds and the deliverable levels.

Dark mode, too

Every Lineset app follows your Jira theme, light or dark.

Blockline’s tab in the Storefront space in Jira’s dark theme: “4 of 8 At risk or Blocked” and eight deliverables with their risk, reason, date, owner and open blockers, on a dark background.

Secure and private

Runs on Atlassian
Your data stays on your Atlassian site.
No servers
None of ours, and no outside services: nothing is sent anywhere.
Changes nothing
It reads Jira and writes nothing back.
Reads as you
It sees only what your permissions allow.

Built on Atlassian Forge. No tracking. What it reads and stores →

Pricing

Free up to 10 users

The price per user drops as you grow

  • Billed by Atlassian
  • Every feature on the free tier
  • 30-day free trial

Questions

Doesn’t Jira Plans already show dependencies?

Inside a plan, on Jira Premium, once someone has set the plan up. Blockline works on install, without Premium and without a plan: it reads the links your teams already create, judges every epic against seven rules and says why each one is at risk.

Which links does it read?

Does an epic have to wait on another team to count?

No. A wait inside the same space counts too, and so does an epic whose own date has passed. In the team matrix each space is a team, so teams that share one space show there as one.

Does it need Jira Premium?

No. Epics are the deliverables by default, and everything works on Standard. On sites with a level above epic, such as initiatives on Premium, an admin can make those rows on the risk board too.

All questions →Doing it with Jira’s own tools? Step-by-step guides →

Works well with

See what your epics are waiting on

Install it. Open any epic. Its blockers are there.

Get it on Atlassian Marketplace