BAĞ Proje Deposu

Due dates

Introduced in GitLab 8.7.

Please read through the GitLab Issue Documentation 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. Due dates require at least Reporter permissions to be able to edit them. On the contrary, they can be seen by everybody.

Setting a due date

When creating or editing an issue, you can see the due date field from where a calendar will appear to help you choose the date you want. To remove it, select the date text and delete it.

Create a due date

A quicker way to set a due date is via the issue sidebar. Simply expand the sidebar and select Edit to pick a due date or remove the existing one. Changes are saved immediately.

Edit a due date via the sidebar

Making use of due dates

Issues that have a due date can be distinctively 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 in the right.

Issues with due dates in the issues index page

Due dates also appear in your todos list.

Issues with due dates in the todos

The day before an open issue is due, an email will be sent to all participants of the issue. Both the due date and the day before are calculated using 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