Dates and Deadlines
Set Issue due dates, scan due-state, and receive Inbox-first 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.
Issue due dates are not Linear target dates, Project Files roadmap dates, generic reminders, or SLA rule outcomes.
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. |
Completed and canceled Issues do not show SLA-style on-time, late, achieved, or failed labels for manual due dates.
Table controls
Team Issues, My Issues, and Feature 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
Manual Issue due dates are intentionally simple. Future SLA rules may derive or replace Issue deadlines with business-day logic, achieved/failed states, escalation, and rule evidence. Those SLA behaviors are separate from this due date field.