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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Trigger sla to an issue based on customer who created it?

Is it possible to make the customer or customer organization the trigger for an SLA to an issue?

e.g. can I configure an SLA so that it is triggered based on which customer created the issue?

2 answers

@Matt Hackett -

Based on what I know of it, you should be able to constructed the proper JQL to query on the organization field when you setup the GOAL portion of an SLA setup.

2021-02-23_21-53-40.png

We have not tried that type of setup yet in our env, so I cannot 100% that it will work.  Let me know of your test result.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Thanks Joseph,

It's true you can add an Organization as a trigger using JQL, but the problem seems to be that Organizations can't have fields applied to them; so e.g. you can't construct a JQL query that would trigger an SLA based on it being created by any Organization of type x.

This means that every separate Organization would have to to be added after an OR function in the JQL query to make the trigger apply to all of those orgs. It seems like you'd have to update the query every time you added another customer org, which obviously would be impractical.

So far I've gotten around it by creating a multiple service-level field that applies different SLA rules. But those fields have to be manually applied to an issue by an agent after it is created by the customer, so it's not convenient over the long term.

Hi @Matt Hackett 

If Organisation`s name is in the custom field of tickets, you can try SLA Time and Report.

It allows set for SLA start/stop conditions any issue fields, inclusion Organisation.

2021-02-25_13-47-56.png

Hope it will help you

Regards

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Announcing Mindville Insight is now part of Jira Service Management!

Hello Community! We’re excited to announce that Mindville Insight’s asset and configuration management capabilities will now be integrated into Jira Service Management Premium and Enterprise plan...

754 views 12 15
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