2020-06-23 00:09:42 +05:30
---
stage: Plan
group: Project Management
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-06-23 00:09:42 +05:30
---
2017-08-17 22:00:37 +05:30
# Due dates
2020-03-13 15:44:24 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/3614) in GitLab 8.7.
2017-08-17 22:00:37 +05:30
Please read through the [GitLab Issue Documentation ](index.md ) for an overview on GitLab Issues.
2019-09-30 21:07:59 +05:30
Due dates can be used in issues to keep track of deadlines and make sure features are
2021-03-08 18:12:59 +05:30
shipped on time. Users need at least [Reporter permissions ](../../permissions.md )
to be able to edit the due date. All users with permission to view
the issue can view the due date.
2017-08-17 22:00:37 +05:30
## Setting a due date
2021-03-08 18:12:59 +05:30
When creating an issue, select the **Due date** field to make a calendar
appear for choosing the date. To remove the date, select the date
2019-09-30 21:07:59 +05:30
text and delete it. The date is related to the server's timezone, not the timezone of
the user setting the due date.
2017-08-17 22:00:37 +05:30
2019-09-30 21:07:59 +05:30
You can also set a due date via the issue sidebar. Expand the
sidebar and click **Edit** to pick a due date or remove the existing one.
2017-08-17 22:00:37 +05:30
Changes are saved immediately.
2020-05-24 23:13:21 +05:30
The last way to set a due date is by using [quick actions ](../quick_actions.md ), directly in an issue's description or comment:
- `/due <date>` : set due date. Examples of valid `<date>` include `in 2 days` , `this Friday` , and `December 31st` .
- `/remove_due_date` : remove due date.
2017-08-17 22:00:37 +05:30
## Making use of due dates
2021-03-08 18:12:59 +05:30
You can see issues with their due dates in the [issues list ](index.md#issues-list ).
Overdue issues have their icon and date colored red.
To sort issues by their due dates, select **Due date** from the dropdown menu on the right.
Issues are then sorted from the earliest due date to the latest.
To display isses with the latest due dates at the top, select **Sort direction** (**{sort-lowest}**).
2017-08-17 22:00:37 +05:30
2020-11-24 15:15:51 +05:30
Due dates also appear in your [to-do list ](../../todos.md ).
2017-08-17 22:00:37 +05:30
2021-01-03 14:25:43 +05:30
2017-08-17 22:00:37 +05:30
2021-03-08 18:12:59 +05:30
The day before an open issue is due, an email is sent to all participants
2019-09-30 21:07:59 +05:30
of the issue. Like the due date, the "day before the due date" is determined by the
2018-10-15 14:42:47 +05:30
server's timezone.
2018-11-08 19:23:39 +05:30
Issues with due dates can also be exported as an iCalendar feed. The URL of the
feed can be added to calendar applications. The feed is accessible by clicking
2019-09-30 21:07:59 +05:30
on the **Subscribe to calendar** button on the following pages:
2019-07-07 11:18:12 +05:30
2019-09-30 21:07:59 +05:30
- on the **Assigned Issues** page that is linked on the right-hand side of the GitLab header
2018-11-08 19:23:39 +05:30
- on the **Project Issues** page
- on the **Group Issues** page
