gitlab-org--gitlab-foss/doc/user/project/issues/due_dates.md

---
stage: Plan
group: Project Management
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
---

# Due dates

> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/3614) in GitLab 8.7.

Please read through the [GitLab Issue Documentation](index.md) for an overview on GitLab Issues.

Due dates can be used in issues to keep track of deadlines and make sure features are
shipped on time. Users must have at least [Reporter permissions](../../permissions.md)
to be able to edit them, but they can be seen by everybody with permission to view
the issue.

## Setting a due date

When creating or editing an issue, you can click in the **due date** field and a calendar
will appear to help you choose the date you want. To remove the date, select the date
text and delete it. The date is related to the server's timezone, not the timezone of
the user setting the due date.

![Create a due date](img/due_dates_create.png)

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.
Changes are saved immediately.

![Edit a due date via the sidebar](img/due_dates_edit_sidebar.png)

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.

## Making use of due dates

Issues that have a due date can be easily seen in the issue tracker,
displaying a date next to them. Issues where the date is overdue will have
the icon and the date colored red. You can sort issues by those that are
`Due soon` or `Due later` from the dropdown menu on the right.

![Issues with due dates in the issues index page](img/due_dates_issues_index_page.png)

Due dates also appear in your [to-do list](../../todos.md).

![Issues with due dates in the to dos](img/due_dates_todos.png)

The day before an open issue is due, an email will be sent to all participants
of the issue. Like the due date, the "day before the due date" is determined by the
server's timezone.

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
on the **Subscribe to calendar** button on the following pages:

- on the **Assigned Issues** page that is linked on the right-hand side of the GitLab header
- on the **Project Issues** page
- on the **Group Issues** page
Add latest changes from gitlab-org/gitlab@master 2020-05-26 23:08:26 -04:00			`---`
			`stage: Plan`
			`group: Project Management`
Add latest changes from gitlab-org/gitlab@master 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`
Add latest changes from gitlab-org/gitlab@master 2020-05-26 23:08:26 -04:00			`---`

Add due dates docs [ci skip] 2017-01-24 08:59:37 -05:00			`# Due dates`

Add latest changes from gitlab-org/gitlab@master 2020-02-06 10:09:11 -05:00			`> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/3614) in GitLab 8.7.`
Add due dates docs [ci skip] 2017-01-24 08:59:37 -05:00
New doc topic: issues 2017-05-08 04:35:38 -04:00			`Please read through the [GitLab Issue Documentation](index.md) for an overview on GitLab Issues.`

Fix notes and update links to issues doc After review, heading was changed and links to it needed to be updated, and minor tweaks to the issues docs such as note formatting 2019-07-03 20:55:35 -04:00			`Due dates can be used in issues to keep track of deadlines and make sure features are`
			`shipped on time. Users must have at least [Reporter permissions](../../permissions.md)`
			`to be able to edit them, but they can be seen by everybody with permission to view`
			`the issue.`
Add due dates docs [ci skip] 2017-01-24 08:59:37 -05:00
			`## Setting a due date`

Fix notes and update links to issues doc After review, heading was changed and links to it needed to be updated, and minor tweaks to the issues docs such as note formatting 2019-07-03 20:55:35 -04:00			`When creating or editing an issue, you can click in the due date field and a calendar`
			`will appear to help you choose the date you want. To remove the date, select the date`
			`text and delete it. The date is related to the server's timezone, not the timezone of`
			`the user setting the due date.`
Add due dates docs [ci skip] 2017-01-24 08:59:37 -05:00
			`![Create a due date](img/due_dates_create.png)`

Fix notes and update links to issues doc After review, heading was changed and links to it needed to be updated, and minor tweaks to the issues docs such as note formatting 2019-07-03 20:55:35 -04:00			`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.`
Add due dates docs [ci skip] 2017-01-24 08:59:37 -05:00			`Changes are saved immediately.`

			`![Edit a due date via the sidebar](img/due_dates_edit_sidebar.png)`

Add latest changes from gitlab-org/gitlab@master 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.

Add due dates docs [ci skip] 2017-01-24 08:59:37 -05:00			`## Making use of due dates`

Fix notes and update links to issues doc After review, heading was changed and links to it needed to be updated, and minor tweaks to the issues docs such as note formatting 2019-07-03 20:55:35 -04:00			`Issues that have a due date can be easily seen in the issue tracker,`
New doc topic: issues 2017-05-08 04:35:38 -04:00			`displaying a date next to them. Issues where the date is overdue will have`
Add due dates docs [ci skip] 2017-01-24 08:59:37 -05:00			`the icon and the date colored red. You can sort issues by those that are`
Fix notes and update links to issues doc After review, heading was changed and links to it needed to be updated, and minor tweaks to the issues docs such as note formatting 2019-07-03 20:55:35 -04:00			`Due soon` or `Due later` from the dropdown menu on the right.
Add due dates docs [ci skip] 2017-01-24 08:59:37 -05:00
			`![Issues with due dates in the issues index page](img/due_dates_issues_index_page.png)`

Add latest changes from gitlab-org/gitlab@master 2020-09-16 11:09:32 -04:00			`Due dates also appear in your [to-do list](../../todos.md).`
Add due dates docs [ci skip] 2017-01-24 08:59:37 -05:00
Add latest changes from gitlab-org/gitlab@master 2020-10-02 14:08:56 -04:00			`![Issues with due dates in the to dos](img/due_dates_todos.png)`
Add due dates docs [ci skip] 2017-01-24 08:59:37 -05:00
Send emails for issues due tomorrow Also, refactor the mail sending slightly: instead of one worker sending all emails, create a worker per project with issues due, which will send all emails for that project. 2018-03-30 09:05:20 -04:00			`The day before an open issue is due, an email will be sent to all participants`
Fix notes and update links to issues doc After review, heading was changed and links to it needed to be updated, and minor tweaks to the issues docs such as note formatting 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`
Resolve proclems with issues documentation Change csv import section to bullet list, add back missing bulk import section, and resolve minor issues raised in https://gitlab.com/gitlab-org/gitlab-ce/issues/64102 2019-07-04 02:24:39 -04:00			`server's timezone.`
Send emails for issues due tomorrow Also, refactor the mail sending slightly: instead of one worker sending all emails, create a worker per project with issues due, which will send all emails for that project. 2018-03-30 09:05:20 -04:00
Export assigned issues in iCalendar feed 2018-05-31 10:01:04 -04:00			`Issues with due dates can also be exported as an iCalendar feed. The URL of the`
Resolve proclems with issues documentation Change csv import section to bullet list, add back missing bulk import section, and resolve minor issues raised in https://gitlab.com/gitlab-org/gitlab-ce/issues/64102 2019-07-04 02:24:39 -04:00			`feed can be added to calendar applications. The feed is accessible by clicking`
Fix notes and update links to issues doc After review, heading was changed and links to it needed to be updated, and minor tweaks to the issues docs such as note formatting 2019-07-03 20:55:35 -04:00			`on the Subscribe to calendar button on the following pages:`
Ensure all lists are surrounded by new lines Markdown renderers find it easier to determine where lists start and end when lists are surrounded by new lines. For consistency, also ensure entries in the list are aligned when they span multipls lines. 2019-02-22 08:17:10 -05:00
Fix notes and update links to issues doc After review, heading was changed and links to it needed to be updated, and minor tweaks to the issues docs such as note formatting 2019-07-03 20:55:35 -04:00			`- on the Assigned Issues page that is linked on the right-hand side of the GitLab header`
Export assigned issues in iCalendar feed 2018-05-31 10:01:04 -04:00			`- on the Project Issues page`
			`- on the Group Issues page`