Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Setting up SLA for organization


I'm in the process of setting up SLA's in our cloud based Jira SM. We've got some clients with differing SLA's from the norm.


In my tests with a calendar I named "testorg" above pictured setup worked fine and the resolution SLA updated automatically as it should, but there's something in this that breaks things. Granted, that test SLA goal was only for requests, not incidents.

Can you have two different SLA goals that have the same "reported in organizationMembers" organization name but different ticket types (incident and service requests)?

1 answer

1 accepted

Hi @Juuso Ikonen ,

If you're referring to the Customer Request type by ticket type, you can use the following JQL coupled with reported in the clause:

"Request Type" = "IT help (DEMO)"

If you're referring to the issue type, you should use,

issuetype = "IT Help"

You can refer to the documentation too:

Please let me know if you have further questions.



Thank you, though I have might have left out a pretty big reason why the string is
>"Ticket category" = Incidents AND reporter in organizationMembers("ORG1")

We have different SLA's depending on the ticket category.

These are the categories I meant. The request type and issuetype would probably be too specific for our use, unfortunately.

I'm pretty sure the SLA's now work correctly, though, so I'll mark this as solved. Thank you!

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

314 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you