Create SLA based on due date

[Antonia]

Is there a possibility that if you have a due date, for example, August 30, 2025, the SLA date will also be postponed? Because currently, the SLA date is created depending on the creation date of a work item.

If I postpone the due date, the SLA should also be postponed.
I have already tried to create a rule, but I cannot find any actions with SLAs.

Example: creating an SLA based on due date | Atlassian Support | Atlassian Documentation

I have read through the page here, but that is not exactly what we want. We do not want to stop SLA, but rather extend the due date.

Example:
If the due date is August 30, 2025, the SLA should also be due.

[Marc - Devoteam]

Hi @Antonia 

This is not an option.

The link you used is also a DC option, not a cloud option.

An SLA has a goal, as the goal is 24 days, this is the goal of that SLA you can't base an SLA on the value set in a due date.

A SLA has start/pause and stop actions, these are based provided options.

A SLA can't be a dynamic option, SLA's a metrics caught based on provided options and set goals to measure this.

[Tuncay Senturk _Snapbytes_]

Hi @Antonia 

SLAs are driven by the start/stop conditions, not by the issue’s Due date field. Changing the due date won’t automatically shift the SLA target.

If you want the SLA target to move with the due date, you can change the SLA’s stop condition so it’s calculated relative to the Due date.

Or you can use automation to set a custom date/time field (used in the SLA) whenever the due date changes.

If you are open to use an app for this Time to SLA is the best option for this, you can easily configure your SLA and select Due Date as the target dynamic date field.

[Alina Kurinna _SaaSJet_]

Hi @Antonia 

Hi! Yes, this is possible; you can achieve exactly that with the Negotiated date SLA type from the SLA Time and Report app.

If your SLA goal is linked to the Due date and you've configured it to trigger at 9:00 AM, and your issue has a due date of August 30, the SLA breach will occur at 9:01 AM on August 30.
If you later change the due date to September 2, the SLA will automatically adjust, and now will be exceeded at 9:01 AM on September 2.

This SLA goal type tracks your Target date field (like Due date) and dynamically updates the SLA based on changes to that field. It’s a great way to align SLAs with deadlines or commitments that shift over time.

A bit more about the Negotiated date SLA in our app:

• You choose any date field (like Due Date or a custom “Negotiated Delivery Date”) as the SLA deadline.

• The timer adjusts whenever the field changes.

• You can combine this with calendar settings and even automated actions upon SLA breach.

Let me know if you’d like help setting it up — or feel free to book a 1:1 demo call with our Product Manager.
Regards!