Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Migrating to new SLA's

Kate Edwards
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!
Get involved
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

Answer
Watch
Like Be the first to like this
202 views

1 answer

0 votes
Ravi Sagar _Sparxsys_
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.
Get recognized
March 21, 2022

Hi Kate,

Try this.

created < "2022-03-14"

Ravi 

View More Comments
Kate Edwards
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!
Get involved
March 22, 2022

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

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira Service Desk
Jira Service Management
TAGS
AUG Leaders

Atlassian Community Events

    See all events