Documentation

Where Blockline appears, how it judges risk, and what it reads and stores.

Getting started
Where Blockline appears in Jira Cloud once it is installed, and how to open each view: the issue panel, the Blockline tab, Apps › Blockline, the team matrix and the dependency map.
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 issue 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.
Exporting to CSV
Download or copy the risk board or the team matrix as CSV, after your filters, and what each column holds.
Permissions and data
The two permissions Blockline asks for, what it reads and as whom, what it stores in Forge storage and for how long, and why nothing leaves your Atlassian site.