JSD Data Center – Can an SLA target be dynamically based on the issue Due Date

Namrata Bhomkar

Hi Team,

We have a requirement in Jira Service Management Data Center to configure an SLA where the issue's Due Date should be used as the SLA deadline, instead of using a fixed duration such as 24h, 48h, etc.

Requirement

For example:

• Estimate = Large
• The team manually enters a Due Date on the ticket.
• The SLA should start when the Due Date is added.
• The SLA target/deadline should be the Due Date entered on that specific issue.
• If the issue is resolved before the Due Date → SLA successful.
• If the issue is resolved after the Due Date → SLA breached.
• If the Due Date is changed, the SLA target should ideally be recalculated accordingly.

Example:

Due Date: 30 Sep 2026, 17:00
SLA deadline: 30 Sep 2026, 17:00

We do not want to configure a fixed SLA goal such as 24h, because the required SLA duration will vary depending on the Due Date entered for each ticket.

Configuration tested

We tried configuring:

• Start: Issue Created / Due Date changed from Empty
• Pause: Due Date condition
• Stop: Resolution Set

However, the SLA Goal still requires a fixed duration (for example, 24h, 5d, etc.).

Question

Is there a native way in Jira Service Management Data Center to configure an SLA whose target/deadline is dynamically taken from the Jira Due Date field of each issue?

If not, what would be the recommended approach/workaround to achieve this requirement?

Thanks!

Josh

Hi — short answer for Jira Service Management Data Center: there is no native SLA goal type whose target is "whatever is in the Due Date field." SLA goals are still fixed durations (or calendars built from fixed durations). Your Start/Stop conditions can key off Due Date being set, but the Goal itself will always ask for something like 24h / 5d.

Workarounds teams use:

1. Automation (or ScriptRunner) to keep Due Date and SLA in sync the other way. Treat the SLA goal as the source of truth (fixed duration from "Due Date set"), and have a rule write now + that duration into Due Date — or the reverse if you must keep Due Date as the human input: when Due Date changes, set a custom "SLA hours" field to the difference and pick among several pre-built SLA goals (4h / 1d / 3d / 5d / 10d) with JQL conditions. Not elegant, but fully native if you bucket the durations.
2. ScriptRunner / Groovy SLA custom goal (DC only) if you already license it — that is the usual path for a true "deadline = Due Date" goal.
3. Don't use SLA for this metric. If the only need is "resolved before Due Date = success," a dashboard gadget or automation that compares Resolution date to Due Date can report compliance without fighting the SLA engine.

If Due Date changes mid-flight, native SLAs also will not re-aim the goal at the new timestamp — you'd need the scripted/custom path for recalculation too.

Worth a vote/watch on any open JAC for "SLA goal based on Due Date" for your DC version; until then, bucketed goals or ScriptRunner is the realistic answer.