Settings

Jira admins change Blockline for the whole site under Jira settings › Apps › Blockline settings. Only Jira admins can save: the save is refused unless Jira confirms the person has the Administer Jira permission. Every view rebuilds on its next open after a save.

Link types that mean “waits on”

By default Blockline reads the built-in Blocks link type: “A blocks B” means B waits on A. Tick any other link type your teams use, such as “depends on”, and say which way its outward phrase reads: either the other issue waits, or this issue waits. At least one link type must be ticked.

Where an issue’s date comes from

The date sources in order: due date, Target end, the end of the active or next sprint, the release date of the earliest fix version, and the latest child. Move them up and down, or switch them off; at least one must stay on.

Thresholds

• Stalled: a blocker still To Do this many days before the waiting issue’s date. Default 10.
• Idle: a blocker in progress for this many days. Default 14.

Deliverables

Which hierarchy levels are rows on the risk board. Epics by default; on a site with a level above epic, such as initiatives on Premium, tick that level too. Levels are chosen by their place in the hierarchy, never by issue type name.

Default scope

The scope Apps › Blockline opens with for anyone who has not saved one of their own: a set of spaces, or none, so everyone picks their own.

Reset

Reset to defaults puts every setting back as it was on install.