On this page

Every item has a Start date and a Due date. They drive Gantt charts, overdue flags, and date-based automations. There are two ways they get filled in, and you should decide which your teams rely on.

By hand#

In the sidebar, click Start date or Due date, type a date or pick one from the calendar, or click Today. Clear removes it. With the field focused, t sets today and Delete clears. Past-due items show (Overdue). Dates can also be edited in tables, on boards, and by dragging bars on a Gantt.

Start and due date fields

Changing a parent's start date may prompt Update Subtask Start Date? so subtasks keep in step.

Created, last updated and completed dates#

The Dates group also shows three read-only dates, together in one small card below the Start and Due fields: Created date (when the item was entered), Last updated and Completed date (Not completed until the item is done). An admin can hide or reorder each of them per item type under Data Model → Sidebar Field Order; with all three hidden, the card disappears.

From the cycle#

If a team works in sprints or other cadences, you want items to take their dates from the cycle they are placed in, not from someone typing. That is controlled organization-wide in Configure Settings → Admin → Global Automations: Sync work item dates with their cycles, on by default.

The Global Automations settings page with Sync work item dates with their cycles ticked.

With it on, placing an item on a cycle board sets its start and due dates to the cycle's timebox. You can still shorten an item's due date inside the cycle, for example to make a dependent item wait for it mid-sprint. Move the item to another cycle and it adopts that cycle's dates again, so re-apply any custom date afterwards.

Which should you use?

Teams on cycle boards: leave sync on and stop typing dates. Teams on perpetual boards or date-driven projects: set dates by hand or on the Gantt, and consider Link Mode so dependent dates move together.

Next: Progress Tracking.

Powered by DevStride