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

How to configure SLAs for customers in different time zones?

We have customers in three different time zones, GMT+00:00, GMT-04:00 and GMT+09:00. 

What would be the best practice to set up SLAs for customers based on these three different regions?

1 answer

1 accepted

2 votes
Answer accepted

Hi @Debora Silva 

The first thing to check is that you have a way of distinguishing which customers, or more accurately which issues, relate to which timezone. 

Once you can identify them in this way you can then use different calendars for each set of issues based on the JQL you have used to define which relate to which timezone. 

I did write a few years ago on using different SLAs for different timezones which is loosely related to this (it shows how you can define different SLAs for different times of the year)


Hope this points you in the right direction to solve your challenge. 



Many thanks, Phill.

I'm looking for a way to distinguish the customers.

I come from OTRS and am running a trial to migrate our service desk. I'm sure I can customize this sort of thing in OTRS, but I'm still learning about Jira.

Kind regards,


Hi @Debora Silva 

One thought that might help you in identifying the timezone of your user is to look at the API for the user /rest/api/2/user and store this timezone information away in your ticket using one of the automation tools.  You can use a hidden field to hold this information.

You could then set your automation up to correctly attribute a timezone to each ticket on creation.

Note however that if a user has not updated their preferences they will get the system default timezone. 


Hope this helps



Many thanks, @Phill Fox 

As we are considering opening tickets via email as well as the portal, I'm not sure it's possible to have this information linked to a ticket.

As we currently have a customer database, I'm thinking about creating a dynamic field (eg region) in "Organizations" to define where the customer is based.

I only need to define 3 different time zones as follows:

EU - For customers in Europe

US - For customers in America

APAC - For customers in Asia and the Middle East.

As I have this information defined by the customer, I can use the information in this field + the priority to define a calendar to be used in the SLA.


JQL: Priority = High AND (region)

Use: 10-16 weekday calendar - US

Is it possible?

Thanks again,


Suggest an answer

Log in or Sign up to answer
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...

241 views 7 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