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
---
2021-09-04 01:27:46 +05:30
# Due dates **(FREE)**
2017-08-17 22:00:37 +05:30
2021-09-04 01:27:46 +05:30
Due dates can be used in [issues ](index.md ) to keep track of deadlines and make sure features are
2022-04-04 11:22:00 +05:30
shipped on time. Users need at least the Reporter role
2021-03-08 18:12:59 +05:30
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
2021-11-18 22:05:49 +05:30
text and delete it. The date is related to the server's time zone, not the time zone of
2019-09-30 21:07:59 +05:30
the user setting the due date.
2017-08-17 22:00:37 +05:30
2021-09-04 01:27:46 +05:30
You can also set a due date by using the issue sidebar. Expand the
sidebar and select **Edit** to pick a due date or remove the existing one.
2017-08-17 22:00:37 +05:30
Changes are saved immediately.
2021-09-04 01:27:46 +05:30
2017-08-17 22:00:37 +05:30
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-04-29 21:17:54 +05:30
You can see issues with their due dates in the issues list.
2021-03-08 18:12:59 +05:30
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.
2021-03-11 19:13:27 +05:30
To display issues 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
2021-11-18 22:05:49 +05:30
server's time zone.
2018-10-15 14:42:47 +05:30
2018-11-08 19:23:39 +05:30
Issues with due dates can also be exported as an iCalendar feed. The URL of the
2021-09-04 01:27:46 +05:30
feed can be added to calendar applications. The feed is accessible by selecting
the **Subscribe to calendar** button on the following pages:
2019-07-07 11:18:12 +05:30
2021-09-04 01:27:46 +05:30
- The **Assigned Issues** page linked on the right side of the GitLab header
- The **Project Issues** page
- The **Group Issues** page
