2020-05-26 23:08:26 -04:00
---
stage: Plan
group: Project Management
2020-11-26 01:09:20 -05:00
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-05-26 23:08:26 -04:00
---
2021-05-24 11:10:27 -04:00
# Due dates **(FREE)**
2017-01-24 08:59:37 -05:00
2021-05-24 11:10:27 -04:00
Due dates can be used in [issues ](index.md ) to keep track of deadlines and make sure features are
2021-11-16 13:12:21 -05:00
shipped on time. Users need at least the Reporter [role ](../../permissions.md )
2020-12-21 10:10:05 -05:00
to be able to edit the due date. All users with permission to view
the issue can view the due date.
2017-01-24 08:59:37 -05:00
## Setting a due date
2020-12-21 10:10:05 -05:00
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-09-22 17:11:31 -04:00
text and delete it. The date is related to the server's time zone, not the time zone of
2019-07-03 20:55:35 -04:00
the user setting the due date.
2017-01-24 08:59:37 -05:00
![Create a due date ](img/due_dates_create.png )
2021-05-24 11:10:27 -04:00
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-01-24 08:59:37 -05:00
Changes are saved immediately.
2021-05-24 11:10:27 -04:00
![Edit a due date with the sidebar ](img/due_dates_edit_sidebar.png )
2017-01-24 08:59:37 -05:00
2020-04-27 11:10:16 -04:00
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-01-24 08:59:37 -05:00
## Making use of due dates
2021-03-24 11:09:19 -04:00
You can see issues with their due dates in the issues list.
2020-12-21 10:10:05 -05:00
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-01-21 13:09:11 -05:00
To display issues with the latest due dates at the top, select **Sort direction** (**{sort-lowest}**).
2017-01-24 08:59:37 -05:00
2020-09-16 11:09:32 -04:00
Due dates also appear in your [to-do list ](../../todos.md ).
2017-01-24 08:59:37 -05:00
2020-10-02 14:08:56 -04:00
![Issues with due dates in the to dos ](img/due_dates_todos.png )
2017-01-24 08:59:37 -05:00
2020-12-21 10:10:05 -05:00
The day before an open issue is due, an email is sent to all participants
2019-07-03 20:55:35 -04:00
of the issue. Like the due date, the "day before the due date" is determined by the
2021-09-22 17:11:31 -04:00
server's time zone.
2018-03-30 09:05:20 -04:00
2018-05-31 10:01:04 -04:00
Issues with due dates can also be exported as an iCalendar feed. The URL of the
2021-05-24 11:10:27 -04:00
feed can be added to calendar applications. The feed is accessible by selecting
the **Subscribe to calendar** button on the following pages:
2019-02-22 08:17:10 -05:00
2021-05-24 11:10:27 -04:00
- The **Assigned Issues** page linked on the right side of the GitLab header
- The **Project Issues** page
- The **Group Issues** page