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.

Link work in Jira
Link a blocker and date the work in Jira’s own fields and Blockline reads them: no spreadsheet to keep.
Link a blocker
Pick Link work item from the plus menu on the work item that waits.

Choose is blocked by
Open the link type list and pick is blocked by.

Date the epic
Set its Due date in Details, and give each blocker one too.

See the risk
Blockline shows the epic’s risk and why, with nothing to set up.

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 chain upstream of one epic
What it waits on, through its stories, three levels upstream, with the path that ends latest highlighted.

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

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.

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.

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.
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.

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?
The built-in Blocks link type, out of the box: “A blocks B” means B waits on A. If your teams use another link type, such as “depends on”, a Jira admin can add it in Blockline settings and say which way it reads.
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?
All questions →Doing it with Jira’s own tools? Step-by-step guides →
Works well with
SumlineHow much of each at-risk epic is doneSee them on one epic
LoglineWhere the hours on a late epic wentSee them on one epic
WorklineWho has room to take on an at-risk epic’s workSee them on one epic
ChangelineHow often releases ship, and how often they failSee them on one epic
See what your epics are waiting on
Install it. Open any epic. Its blockers are there.
Get it on Atlassian Marketplace