Dates and Deadlines
Set Issue due dates, understand SLA deadlines, and follow deadline notifications.
Issue due dates are app-owned execution dates for Team work. Use them when an Issue needs to be finished by a specific calendar day.
An Issue has either a due date or an SLA. Setting a due date removes its SLA; setting an SLA removes its due date.
Due date property
Each Issue can have one nullable due date. The date is stored as a calendar date, not a time of day.
You can set, change, or clear the due date from:
- The Issue create dialog.
- The Issue detail property area.
- Issue table rows where the Due Date property is visible.
People with normal Issue work-field edit access can change the due date. Direct-shared viewers can see a display-safe due date for the shared Issue, but they cannot edit it or enumerate private Team options.
Due-state display
Issue tables and detail surfaces show the due date with a current-state tone:
| State | Meaning |
|---|---|
| Overdue | The due date is before today. |
| Due today | The due date is today. |
| Due soon | The due date is within the next week. |
| Later | The due date is farther out. |
| No due date | No manual due date is set. |
| Completed or Canceled | The Issue is terminal, so active urgency is muted. |
Manual due dates use the due-state labels above. SLAs use a deadline with a time of day: Low risk, Medium risk, High risk, or Breached while open, then Achieved or Failed when completed. An open Issue that passes its SLA deadline records one SLA breached entry in Activity within five minutes.
Table controls
Team Issues, My Issues, and Project Issue tables can show the Due Date property where the Issue table supports display controls.
Use Dates filters to narrow Issue rows by:
- Due date windows such as overdue, today, upcoming ranges, custom date/timeframe, and no due date.
- Created date windows.
- Updated date windows.
You can also sort or group by due date on supported Issue tables. Hidden private-Team Issues do not contribute private titles, counts, labels, or options to table controls.
Deadline notifications
Integrity can queue deadline notifications for active Issues with due dates:
- Due-soon notifications are created around the recipient-local day before the due date.
- Overdue notifications are created after the recipient-local due date has passed.
- Recipients are the current assignee and current Issue subscribers who still have access.
- Inbox rows are created first and remain the durable notification record.
- Email delivery is derived from unread deadline Inbox rows and follows the existing Issue/email notification preference.
Deadline notifications are not created for completed, canceled, archived, deleted, permanently deleted, inaccessible, or stale-date Issues.
Changing or clearing a due date resolves the old open deadline state without deleting historical notification evidence.
SLA boundary
Due dates and SLAs replace each other in both directions. A due date or an SLA set by hand takes precedence over rules. Removing an SLA by hand keeps that no-SLA choice on later edits. Setting a due date replaces that choice; clearing the due date lets rules apply again.
SLA rules can assign deadlines in hours, days, weeks, or business days. Completing an Issue records whether its SLA was achieved or failed; canceling it or marking it as a duplicate removes the SLA. Issue CSV exports include the SLA deadline and its current status, with empty cells when there is no SLA.