Field description - Due date
"Due date" is a date - time field that represent when work on the issue should be finished, the issue deadline, so to speak.
Default name: Due date
Terminology variations: None
In-Use: Optional. This field can be set to be used in the issue field configuration.
Mandatory: Optional. This field can be set as mandatory, but need not be.
Data type: Date + Time. Both date and Time can be edited.
Access restrictions: (Default) Created: "Read/Write" for all internal users, and "No access" for external or support users. Editing: "Read/Write" for all internal users, and "No access" for external or support users.
Project > Settings > General, section "Sub-issues":
"Let parent inherit start date and due date from sub-issues" - If this setting is used, the Due date of an issue depends on the latest due date of any of its children, if any.
If you use both start date and due date, then the start date of an issue should always be before its due date.
Due date of an issue can be changed in many ways, including editing the issue, and changing it in the Timeline view (either editing the values manually, or dragging the issue to a new date)
Affected by these settings:
How the "Due date" date+time field looks like, depends on what date formats you use. See your user profile at top right, select Settings > Date and Time settings.
General > Settings > Issue configurations > Issue rules.
Due date can be used in issue rules, either as a criterion, or being set in the rule action.
Due date tells you when work should be finished on an issue, which is important when planning. Ideally, the Due date should also be the date when work is actually completed on the issue.
If an issue is active (not completed) and the Due date is passed, the Due date will be shown in red instead of black in the Issues list. This is so it is easier to see issues that needs looking at.