Guides

What Jira does by itself and where it stops, then what Blockline does.

• Cross-team dependencies in Jira, without Premium

  Jira Standard draws dependencies inside one space. How far a search and Plans go across spaces, and how to see which epics are at risk, and why.

• Jira dependency apps compared: maps, planners and risk views

  Portfolio suites, dependency maps and risk views for Jira side by side: what each kind answers, after what Jira does by itself.

• Find the Jira epics blocked by another team

  A JQL search finds blocked stories, not the epics they hold back. Where Jira’s search stops, and how to see every epic at risk, with the reason.

• A Jira dependency report for the steering meeting

  Plans’ dependencies report needs Premium. How to build a dependency register from Jira’s export, and how to export one already judged.

• A Jira dependency map of one epic’s chain

  Jira’s timeline draws arrows inside one space. How to trace an epic’s blockers across spaces by hand, and a map with the risk each one brings.

• Tell the team that holds you up, before the date slips

  Jira tells nobody when a blocker makes another team late. What an automation rule can and cannot do, and the blocking team’s own view.

Short answers are in the questions on the home page.