Where dates come from

Every issue gets one date, and the source of that date is always written next to it: “14 Nov (sprint end)”. An issue with no date shows “—”, or “no date” on the dependency map.

The order

Blockline takes the first of these that has a value:

1. the due date;
2. Target end, on sites with Plans;
3. the end of the sprint the issue is in, the active one or the next;
4. the release date of its earliest fix version;
5. for a parent with none of the above, the date of its latest child.

A Jira admin can reorder the sources or switch any of them off in Settings. On a site without a Target end field, that source is skipped.

Latest child

A parent takes its latest child’s date only when all of its children were read in the view, so the date is never a guess from part of the tree.

Days

Dates are calendar days, and “today” is the current day in UTC. “6 days after this epic” compares the blocker’s date with the waiting issue’s date; “8 days to STOR-1’s date” counts from today.

Fields are found by type

Sprint and Target end are found by their field type, never by their name, in team-managed and company-managed spaces alike, so a renamed field still works.