Community
Q&A
Jira
Questions
Tasks marked as Overdue and/or Completed Late when complete on due date

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

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).

2 answers

2 accepted

1 vote

Answer accepted

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Answer accepted

Hi Zara,

The short answer: there's no per-field "evaluate against end of day" setting in native Jira — the behavior you're seeing is baked into how the Due Date field works, worth understanding why.

Due Date is a date-only field (no time-of-day component). Internally Jira anchors it to 00:00:00 on that calendar day. Your Resolved/completion timestamp is a full date+time value. So the comparison is really "exact timestamp vs. midnight at the start of the due date" — any completion after 00:00:00 on the due date itself reads as "after," hence Overdue/Completed Late, even though colloquially the due date hasn't "expired" until 23:59:59. This is documented, consistent behavior, not a bug.

A few things depending on what's actually driving this:

If it's the plain native due-date flag with no JSM SLAs involved, there's no UI control anywhere to shift it to 23:59:59.
If you do have JSM SLAs configured (Project settings → SLAs), the goal's calendar is the real lever — SLA goals run against a calendar with configurable business hours. Setting that calendar's hours to 00:00–23:59 (or modeling the goal in calendar days rather than a time target) effectively pushes evaluation to end of day.
If this is really a custom report/dashboard, the reliable workaround is to stop relying on the built-in comparison and do a date-only comparison yourself in Automation — format both {{issue.duedate}} and {{issue.resolutiondate}} to yyyy-MM-dd and compare those, then set a separate "On time" flag.

Worth clarifying which of those applies (plain due date vs. JSM SLA) — the fix path differs.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

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

2 answers

2 accepted

Suggest an answer

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PRODUCT PLAN

TAGS

Community showcase

Atlassian Community Events