Skip to content
Menu
HelpDocumentation

Documentation

Start here, a short course in four lessons, then the views to go further, then how Blockline judges risk and what it reads and stores.

Start here

  1. What “blocks” means

    Lesson 1: a “blocks” link joins two Jira work items. A blocks B means B waits on A. How it reads from each side and how an epic inherits a blocker.

  2. Link a blocker

    Lesson 2: link one Jira work item as blocked by another, in your space or across spaces, step by step with images, and how to remove the link.

  3. Add dates and owners

    Lesson 3: give epics and blockers a due date, give each blocker an owner and move its status, so Blockline can say how late an epic will be.

  4. See what holds up an epic

    Lesson 4: where Blockline appears in Jira Cloud once installed: a work item, the Blockline tab in a space, Apps › Blockline and the dashboard.

Go further

  • Read risk across spaces

    Pick spaces, a saved filter or a JQL query on Apps › Blockline and read every team’s epics on one risk board, worst first.

  • See which teams hold you up

    Holding up others shows whom your team makes late; the team matrix counts open dependencies between spaces, with the worst level in each cell.

  • Trace a chain with the map

    Open the dependency map of an epic: what it waits on, upstream, with each work item’s date and risk, and the path that ends latest in blue.

  • Fix gaps in your data

    The Data health tab lists blockers with no date or owner and deliverables with no date, each with a Jira search link and the lesson that fixes it.

  • Put risk on a dashboard

    Add the Blockline gadget to a Jira dashboard: the count of epics At risk or Blocked in a scope, worst first, with a link to the whole board.

  • Exporting to Excel or CSV

    Copy a tab as text, or download the risk board, Holding up others or the team matrix as Excel or CSV, after your filters.

Reference

  • How risk is judged

    The seven rules Blockline applies to every dependency, the four levels, how an epic inherits what its stories wait on, and what counts as done.

  • Where dates come from

    How Blockline picks one date for every work item from the due date, Target end, sprint end, release date or latest child, and how the source is shown.

  • Settings

    The site-wide settings a Jira admin can change: link types and direction, date sources, thresholds, deliverable levels and the default scope.

  • Privacy, permissions and data

    The two permissions Blockline asks for, what it reads and as whom, what it stores and for how long, and why nothing leaves your Atlassian site.

All guidesFAQ