Skip to main content
Issues and PRs > Due on
Tom Williams avatar
Written by Tom Williams
Updated over 3 months ago

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 equals to the earliest due date.

Source: Mixed

Transformation logic: Use 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)

milestone.due_on

Gitlab (PRs)

milestone.due_date

Gitlab (Issues)

due_date or milestone.due_date

Bitbucket (PRs)

N/A

JIRA (Issues)

last sprint "end at" or issue duedate

ClickUp (Issues)

list (column) due_date OR due_date

Trello (Issues)

due

Did this answer your question?