Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: due_on
Type: Datetime
Description: The due date of the item. This due date takes into account resolved issues. E.g., a pull request resolving multiple issues will have a due_on value equal to the earliest due date.
Source: Mixed
Transformation logic: Use the native field by default. For pull requests resolving multiple issues, the due_on is calculated using the earliest of the pull request native due_on and resolved issues due_on.
From: |
|
Github (PRs, Issues) |
|
Gitlab (PRs) |
|
Gitlab (Issues) |
|
Bitbucket (PRs) | N/A |
Azure DevOps (PRs, Issues) | N/A |
JIRA (Issues) | last sprint "end at" or issue |
ClickUp (Issues) | list (column) due_date OR |
Trello (Issues) |
|
Reporting Use Cases
The Due On field is critical for planning, prioritization, and monitoring on-time delivery. As a timestamp, it allows you to filter for time-sensitive work, visualize upcoming deadlines, and calculate lateness.
Filtering for Prioritization: The most common use of due_on is to filter items based on their deadlines, allowing teams to focus on what's most urgent.
Overdue Items: Create reports that list all open work past its deadline by using a filter like
Due On before today. This is the foundation for any "Overdue Items" widget.Upcoming Work: Scope your widgets to the current sprint or work cycle with a filter such as
Due On within the next 14 days.Unplanned Work: You can also identify items that haven't been scheduled by filtering where
Due On is null.
Reporting on Workload Distribution: Using
Due Onas a dimension in your reports helps you visualize how work is distributed over time.A column chart with
YEAR_MONTH(due_on)as the dimension andCOUNT()as the metric can show you how many items are due each month, helping you spot potential crunches and plan capacity more effectively.
Custom Formulas for Urgency: You can use
Due Onin custom formulas to create dynamic, at-a-glance indicators of an item's status.Days Overdue/Remaining: A custom dimension can show exactly how late an item is with a formula like
IF(due_on < NOW(), CONCAT("Overdue by ", ROUND((NOW() - due_on) / DAY()), " days"), "On Track"). This adds valuable context to your list reports.Prioritization Score: You could even create a more advanced priority score that combines the due date with other factors, such as
IF(due_on < NOW(), 10, 5) + story_points, to help rank items in your backlog.