Tasks marked as Overdue and/or Completed Late when complete on due date

[DICARLO_ ZARA E_]

Tasks with a Due Date of a given day are being marked as Overdue and/or Completed Late when completed on the same calendar day as the due date. This behavior impacts SLA tracking and employee performance metrics.

Is there a way to edit the SLA metric goal settings so that the deadline evaluates against End of Day (23:59:59) instead of the default midnight start of day (00:00:00).

[Varun Chillamcharla]

Hi Zara,

Yeah, this is a common gotcha, Jira's Due Date field is date-only (no time component stored), so when it evaluates "overdue," it's implicitly comparing against midnight (00:00:00) of that date, not end of day. That's why completing something on the actual due date still shows as overdue or late.

There's no setting inside the native Due Date/Overdue logic itself to shift that to 23:59:59, it's just baked into how the field works.

If this is being tracked through JSM SLAs specifically, you can work around it, SLA goals are configured with their own calendar and time-based rules, not tied directly to the raw Due Date field. You'd set up or adjust the SLA metric's "Time to" condition to reference a calculated field or the due date with an explicit end-of-day time built in, rather than relying on the default comparison.

If this is just native Jira "Overdue" styling or reporting (not a JSM SLA), the more reliable fix is Automation, run a scheduled or field-based check that compares resolutiondate (or the transition timestamp) against duedate using a date-only comparison instead of a strict datetime one, so same-day completions don't get flagged.

I've dealt with exact-day date comparisons like this before in Automation, happy to share the JQL/smart value pattern if that's the direction you want to go.

[DICARLO_ ZARA E_]

Thank you Varun, this was very helpful, if you don't mind sharing the JQL/smart value pattern with me that would be great.

[Varun Chillamcharla]

Sure thing, Zara.

The core idea is to compare Due Date and Resolution Date at the day level, not the full timestamp, so a completion at any time on the due date still counts as on time.

Automation setup:

1. Trigger: Issue transitioned (to your Done/resolved status)

2. Condition: compare two smart values using startOfDay so both sides drop their time component:

{{issue.resolutiondate.startOfDay}} <= {{issue.duedate.startOfDay}}

3. If true, branch into "on time" (set a custom field, add a label, whatever your reporting needs), if false, branch into "late"

If it's more for reporting/dashboard purposes than an Automation branch, you can build the same logic as a calculated field, or just use JQL directly, since JQL date comparisons default to date-only when you reference a plain date like duedate, this actually works out fine on that side. It's really the SLA/automation side where the time component sneaks in.

The startOfDay smart value is really the key part, it strips the time off both fields so you're comparing calendar days instead of exact moments.