Jira epic at risk: blocked, or short of time?
Atlassian’s side checked on 7 October 2026, the figures from our demo site on 10 November 2026.
When an epic is at risk, the fix depends on why. If it waits on another team’s work, the conversation is with that team. If its own people have no time, the fix is to move work. Jira shows neither answer on the epic. This page says what Jira shows by itself, then reads one at-risk epic with Blockline and Workline.
What Jira does by itself
- Blocked is a link, not a status. A work item is blocked when another work item blocks it through a link, and teams link the stories, so the epic has no Blocks link of its own.
- Dates are not compared. A search matches the link, whether or not the blocker is finished, and says nothing about whether its date lands before the epic’s.
- No weeks, no capacity. A search lists who holds the epic’s open work and their Remaining estimate, as one total, and the time tracking settings give one working week for the whole site.
So Jira can say what is linked and who holds what, but not whether the epic is waiting on others or short of time.
One epic, two answers
The example is Holiday checkout, STOR-1, an epic in the Storefront space of our demo site, with three stories.
Workline is our app. So is Blockline. Both read what Jira already holds, and each opens from View app actions, the hexagon under the work item’s title.
Why it is at risk, with Blockline

- At risk, because PAYC-3, Refund API, blocks the story STOR-4 and lands 6 days after the epic’s date.
- Waiting on lists all three blockers, each in another space: PAYC-3 at risk, DATA-2 on Watch with no date, MAPP-4 on track.
Blockline is on the Atlassian Marketplace; its page on lineset.dev has more.
Whether its people have time, with Workline
Workline’s panel on STOR-4, the story waiting on PAYC-3 (the picture under this page):
- 4h left for Mitch Davis, with no dates and no sprint, so it sits in no week yet. The panel says to add a due date or a sprint and Workline places it.
- Who has room for it: the people on the plan with the fewest hours in the next eight weeks, Cassi Owens with 10h, 3% of her hours, then Alana Grant, Emma Paris and Ada Isadora, each with a Move button.
So STOR-1 is not short of people: 4h of work, and room to take it. What holds it up is PAYC-3, so the conversation is with the team that owns it. When an epic’s own work is the problem, press Move to give a work item to someone with room (Move work). Workline changes nothing in Jira unless you press Move or Apply (on dates for work with none).
Who is over capacity across the plan is in Jira workload by assignee. Back to Workline.
