Fix gaps in your data

Blockline adds no fields and asks for no process: it judges risk from what your teams already keep in Jira. The more of it is there, the more it can tell you. Where something is missing, the board’s Data health tab lists the work items, with a link to each list in Jira’s work item search.

Where gaps show

The Data health tab, beside the risk board and the team matrix, counts for its scope:

• the open blockers with no date, out of all open blockers;
• the open blockers with no assignee;
• the open deliverables with no date, out of all of them.

Each line says what the gap does to risk, names the first ten work items by key and summary (each opens in a new tab), and has a link that opens exactly those work items in Jira’s work item search, where they can be fixed. A long list is split into several links. When there are no dependency links at all, or at least half the blockers or half the deliverables have no date, a note over the board says so and opens the tab.

The tab comes from the same build as the board, so it costs nothing extra and is as old as the board (“Updated 3 min ago”).

Close a gap

Each line of the tab has a lesson that fixes it:

• No dependency links, or blockers not linked. Link the work that waits with Blocks: Link a blocker.
• A deliverable or blocker with no date. A due date, a Target end on sites with Plans, a place in a sprint that has an end date, or a fix version with a release date: Add dates and owners. Where dates come from lists every source in order.
• A blocker with no assignee. An assignee, or a place in an open sprint: Add dates and owners.
• Statuses that never move. Stalled blocker and Long in progress read the status category: Add dates and owners.

Everyone sees their own

Blockline reads Jira as the person looking, so these lists hold what you can see: a work item you cannot open is neither counted nor linked, and a colleague with wider access may see a longer list. Permissions and data says why.