Skip to content
Menu
HelpBlockers before the next release in Jira

Blockers before the next release in Jira

Jira Cloud, links, due dates and failures. The figures from our demo site on 10 and 12 November 2026.

A blocker that lands after the work it holds up is a risk to the next release. Jira shows the link between two work items, not whether the blocker’s date is later than the work’s. This page says what Jira shows by itself, then reads one epic’s blocker with Blockline and the failures of earlier releases with Changeline.

What Jira does by itself

  • A link, not a date order. A Blocks link says one work item blocks another. Jira does not compare the two work items’ due dates, so a blocker due after the work it holds up is not flagged.
  • One release, one fix version. The next release is an unreleased version. Jira shows which work items name it under Fix versions, but not whether their blockers are dated before the release.
  • Failures are a type of work item. A Bug that names a release under Affects versions shows against that release, and Jira does not count how many releases have failed.

One epic, two answers

Changeline is our app. So is Blockline. Both read what Jira already holds, and Changeline only reads Jira and changes nothing in it. The example is One-page checkout, an epic in our demo’s Checkout space with an open child, Address book sort order, for the unreleased version Checkout 2.0.

What holds it up, with Blockline

Blockline’s panel on the epic CHK-62: At risk, ACCT-36 blocks CHK-65, lands 24 November, eight days after its date; under it the work item waited on, ACCT-36 Card network rules for split payments, In Progress, due 24 November, At risk.
Blockline’s panel on the epic CHK-62: At risk, ACCT-36 blocks CHK-65, lands 24 November, eight days after its date; under it the work item waited on, ACCT-36 Card network rules for split payments, In Progress, due 24 November, At risk.
  • At risk, eight days after its date. ACCT-36, in the second space, is due after CHK-65 is. Blockline reads the Blocks link and the two due dates, so the epic turns At risk with the reason beside it.
  • The reason names the blocker. The epic waits on ACCT-36, and the reason says how late it lands against the child it blocks.

Blockline is on the Atlassian Marketplace; its page on lineset.dev has more.

How often releases fail, with Changeline

The picture under this page is Changeline’s Failures tab. Changeline lists the failures that are not recovered yet first, and the release each one points at. Here CHK-34 and CHK-141 are open against releases 1.7 and 1.9, so the next release’s work sits beside two failures that have not closed. Failures and recovery time says how a failure is counted, and Changeline’s Trends tab charts them week by week. Back to Changeline.

DORA here is the research programme at Google behind deployment frequency and three other keys, not the EU’s Digital Operational Resilience Act. DORA is a trademark of Google LLC, and Changeline is not made or endorsed by Google.

Changeline’s Failures tab over Checkout and Accounts, from its tab strip down: eight failures, the two not recovered yet first and marked Open, CHK-34 against release 1.7 and CHK-141 against 1.9, then the six recovered failures with their recovery time.
Changeline’s Failures tab: the failures not recovered yet, first, with the release each points at.

Changeline is coming to the Atlassian Marketplace

Get one email the day it’s live.