Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira Filters based on SLA Breach and Custom Field Date

I want to create an SLA that triggers 90 days after a date is entered into a custom field, and filter if any of the tickets created have breached that SLA. Is this possible or can I only trigger an SLA based on status or issue created date?

1 answer

0 votes

Hi @robert cortez 

To check the logic here...

  • The SLA should trigger for an Issue where the custom date field is 90 days after the date set in the field
  • If the SLA is not met, it should show as breached

If this is correct, a few questions...

  • What is the SLA checking for?
  • How long is the SLA?
  • Should the SLA not be set if a certain action has been performed in the 90 days?
  • What's the trigger for this SLA (eg. Issue Assignment, Status transition, etc)?

It'll be possible to do something here, but there's missing parts of the process here we'd need to establish :)


90 day sla, and just checking to see if 90 days have passed since the date entered into the custom field.

I believe that there is no exception or pause, and of the triggers I found the only one that may work is when the ticket status is set to 'open'. then they can enter the date when they move it to open. 


hopefully this helps

Hi @robert cortez 

It's not really an SLA though is it?

How does a user "breach" this SLA? What should happen within 90 days - the date should be entered within 90 days?

An SLA needs...

  • An amount of time
  • Something to limit it to a certain set of issues
  • A trigger to start the SLA
  • A trigger to end the SLA (i.e stop it breaching)


Sorry for the delay Stephen.


So the type of project this is, when a ticket is created they do not want to start an SLA timer for 90 days. Some prereq work has to be done and then a date is entered into a custom field, and they want to know how old the ticket is from the date that is entered into that same custom field or how much time is left, basically. 


sorry if that seems convoluted, basically we are looking for a 90 day SLA based on a date we choose to enter, and to see how much time is left. 

Hi @robert cortez 

So just to confirm the logic...

  • Issue is created - no SLA starts
  • Some prereq work is done - then a date is entered into a custom field
  • SLA is set to 90 days at that point - based on that date entered (not the date it WAS entered)

Is that correct?


Apologies - I'm a little confused about this sentence:

basically we are looking for a 90 day SLA based on a date we choose to enter, and to see how much time is left. 

I'm not sure when the 90 day SLA is set, nor what "how much time is left" means in this context.


Yes your bullet point list is correct. sorry my explanation of this is so confusing, and as for the last part, we can ignore it as I figured out a work around for them I believe. 


we just need to be able to tie a 90 day SLA to a custom field at this point. 


so we enter a date into a custom field, and then the SLA for 90 days starts once a date is entered, and is tied to that date. 


for example if a ticket is made today (24th), but we dont get the pre work done till the 26th, we want the 90 day SLA to start from the 26th. 


again i hope this makes better sense, and I thank you for your time and effort. 

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events