Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Migrating to new SLA's

Kate Edwards
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 21, 2022

We have been running with a specific set of SLA's however, from 13th March 2022 we have entered into a new contract. So for any issues created prior to this date, we want them to remain on the old SLA, and from 14th March, all new issues should go against the new SLA's, however, I don't seem to be able to find an appropriate way to write the JQL to make this happen

1 answer

0 votes
Ravi Sagar _Sparxsys_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 21, 2022

Hi Kate,

Try this.

created < "2022-03-14"

Ravi 

Kate Edwards
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 22, 2022

I've been trying it like this: createdDate < "2022-03-14", but unfortunately, it's having no effect.

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, opsgenie migration, jira service management, incident response, on‑call management, alerting tools, migration guide, devops operations, service reliability, atlassian learning, migration best practices, opsgenie support, IT operations

Join the Opsgenie Migration group 🚚

Heads up! Opsgenie's features are moving to Jira Service Management and Compass. Planning your migration? Join our dedicated group for resources and tips from Atlassian and the Community to ensure a smooth transition.

Check it out ↗
AUG Leaders

Atlassian Community Events