doc/user/project/issues/due_dates.md
{{< details >}}
{{< /details >}}
{{< history >}}
{{< /history >}}
Use due dates in work items to track deadlines, and make sure features are shipped on time.
Due dates are supported in:
The day before an open item is due, an email is sent to all participants.
<!-- For issue due timing source, see 'issue_due_scheduler_worker' in <https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/initializers/1_settings.rb> -->The notification is sent at 00:50 in the server's time zone (for GitLab.com this is UTC) for all open items with a due date of the next calendar day.
Due dates also appear in your to-do items.
You can see issues with their due dates on the Work items page. If an issue contains a due date, it is shown below the issue title:
Issue dates in the past are shown with a red icon ({{< icon name="calendar-overdue" >}}).
To view and sort issues containing due dates in your project:
All users with permission to view the issue can view its due date.
If you have the Planner, Reporter, Developer, Maintainer, or Owner role, when creating an issue, select Due date to show a calendar. This date uses the server's time zone, not the current user's time zone.
To remove the date, select the date text, then delete the text.
Prerequisites:
To do this:
To set a due date with quick actions in an issue's description or comment:
/due: Set the due date./remove_due_date: Remove an existing due date.Issues with due dates can also be exported as an iCalendar feed. The URL of the feed can be added to calendar applications.
Go to the page that contains the list of issues you want to subscribe to. For example:
On the right, from the Actions ({{< icon name="ellipsis_v" >}}) dropdown list, select Subscribe to calendar to display the .ics file.
Copy the full link to the page (including the full query string) and use it in your preferred calendar application.