Skip to content
Menu
HelpTell the team that holds up your Jira epic

Tell the team that holds up your Jira epic

Checked against Atlassian’s documentation on 7 October 2026.

New to blocking links in Jira? Start with What “blocks” means.

The team that is late is usually the last to hear it. Their API slipped a week, which was fine for their own sprint, and two other teams’ epics now miss their dates. On Atlassian Community it reads “will Team Member #2 be notified that his work will be delayed?”, or, from a Champion’s article, links are “invisible until you’re already looking at the item” (Community, August 2026). This page says what Jira can tell the blocking team by itself, then what Blockline shows them.

What Jira does by itself

  • Each work item lists what it blocks under Linked work items. The team sees it when it opens that work item.
  • No warning when a date slips. The requests to notify blocked work items (JSWCLOUD-9039) and to warn when a dependency will miss (JSWCLOUD-25384) were closed without a fix.
  • Automation reacts to events. A rule can run when a work item is linked, or when a field such as the due date changes.

An automation rule

For each blocker, a rule can tell the people waiting:

  1. Trigger: Field value changed, the due date (or Work item transitioned, for status).
  2. Condition: Related work items condition, linked work items of the type “blocks” exist.
  3. Branch: For linked work items, link type “blocks”.
  4. Action: comment on each linked work item, or send an email to its assignee, with the new date.

What it cannot see:

  • The other end’s date. The rule knows the blocker moved, not whether the waiting work item still makes its date, so it tells everyone every time.
  • The epic. The link is between stories; the epic that will miss its date is one level up and hears nothing.
  • What never changes. A blocker never started, with no date, or with nobody on it fires no event at all.

With Blockline

Blockline is our app. It shows the blocking team whom it is making late, and by how much, without anyone sending anything:

Jira with its left sidebar open on Spaces and the recent spaces listed. Beside it, the Storefront space with its tab bar, the Blockline tab picked, then Blockline’s count of epics At risk or Blocked, the levels and the first rows of the risk board.
A space’s Blockline tab: Jira’s sidebar open on Spaces, and the Blockline tab picked
  1. Open the space’s Blockline tab. When its work makes other spaces’ deliverables late, its second tab says how many: Holding up others (7).
  2. Open that tab. Holding up others lists each one, led by the work item here, whom it is assigned to, their work and its space, each in its own column, when they need it, and what it does to them: “45 days late”, “Circular”, “Not started”.
  3. On the blocker itself, the panel and the Details column lead with it: “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)”.
  4. Download, then Excel, on that tab takes the list to the conversation, and Map on a row draws the waiting epic’s chain.

Starting the conversation

The list is the agenda. A few habits make it work:

  • Look at it before the planning, not after. The blocking team can still move a story into the sprint, or tell the other team the new date while their own plan can change.
  • Lead with the date, not the blame. “STOR-1 needs PAYC-3 by its date, and PAYC-3 is due six days after it” is a question both teams can answer.
  • Fix the data first. A blocker with no date or nobody on it shows as Watch, not late. The Data health tab lists those, and an hour of dating and assigning makes the list honest.
  • Close what is done. A blocker finished in reality but open in Jira keeps another team waiting on paper.

The waiting team sees the same dependency from its side, on its epic (Find the epics blocked by another team). Nothing is sent and nothing is written to Jira: Blockline only reads, as each person looking (Permissions and data). More on the Blockline home page.

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.
Payments Core’s Blockline tab: holding up 7 deliverables in other spaces, each led by the PAYC work item that holds it up, with how late it makes them.

Try it on your own links

Free for up to 10 users, then billed per user by Atlassian.