Where dates come from
Every work item gets one date, and the source of that date is written next to it, such as “(sprint end)”, or in the Date column under it. A reason gives the date alone, beside the Date column that says where it came from. A work item with no date shows “—”, or “no date” on the dependency map.
The order
Blockline takes the first of these that has a value:
- the due date;
- Target end, on sites with Plans;
- the end of the sprint the work item is in, the active one or the next;
- the release date of its earliest fix version;
- for a parent with none of the above, the date of its latest child, once every open child has a date.
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 once every open child has a date, each child’s read by the same order above, its sprint end included, and only when all of its children were read in the view. An open child with no date and in no sprint leaves the parent undated, “—”: a date from the dated children alone would be a guess.
Days
Dates are calendar days, and “today” is the current day in UTC. “6 days after this epic’s date” compares the blocker’s date with the waiting work item’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.