Skip to main content

How to setup Jira SLAs for global teams across multiple time zones (Jira Cloud & Jira Data Center)

Hello All!

Being a global company creates the need to have IT teams across different parts of the world in different time zones. When you have team members working in different time zones you also need the ability track SLAs for the work they do. In this blog I will go over a solution to track Jira request SLAs for global teams across multiple time zones.

  • IT department have three teams in three different time zones (Barcelona, New York,  Los Angeles). 
  • Employee requests are processed by the IT team assigned to the location of the employee.
  • All three IT teams work from 9:00 AM to 5:00 PM (Monday - Friday) in their respective time zones. 
  • Every request submitted to IT needs to be resolved within 40 business hours. 
  • Requests can be transferred to another team and the SLA clock should be updated to use the respective time zone of the teams location. 

Office Location


Hours (M-F)

Time to resolution



9:00 AM - 5:00 PM


New York


9:00 AM - 5:00 PM


Los Angeles


9:00 AM - 5:00 PM


Setting up request types
  • IT department is using a Jira Service Management project to intake requests from employees.
  • In order to identify the location of the employee submitting the request, we need to add a mandatory field named "Work Location" to all request types on the IT service management portal. 
  • This field is a single choice select list field with the options "Barcelona", "New York" and "Los Angeles" which represents different office locations for the company.
Jira create issue screen

Setting up SLA Calendars

  • In order to track time in different time zones, we will have to create three different calendars under SLA configurations for each time zone. 
  • Calendar will have working days as Monday - Friday and working hours as 9:00 AM - 5:00 PM.
  • Timezone will contain the correct time zone for the office location.
Jira SLA Calendar

Setting up SLA Metric - Time to resolution

  • Time to resolution SLA will start counting when a ticket is created or when the resolution is cleared and the SLA will finish counting when the resolution of a ticket is set.
  • We will need to create three SLA goals one for each location using the relevant SLA calendar.
  • Based on the value selected for the "Work Location" field, Jira will use the relevant calendar to calculate the "Time to resolution" SLA for each request.
Configure Jira SLA

  • If the "Work Location" field value changed for a request, Jira will check the matching goal for the SLA based on the "Work Location" value and update the SLA based on the time zone.
  • Ex: If the request "Work Location" changed from "New York" to "Los Angeles" and the time of that change is 9:00 AM EST, the SLA clock will not start counting until 12:00 PM EST which is 9:00 AM in PST.

Thanks for taking your time to read this post. Hope this helps !


Popular posts from this blog

How to export a list of Jira custom fields to csv (Jira Data Center)

 Hello All ! As a Jira administrator it is very important to keep an eye on the number of custom fields you have in your instance because the number of custom fields directly impact your instance performance. Atlassian also has confirmed this in their documentation .  One of the important strategies to keep your custom field number low is to reuse them as much as possible across projects. When you get a request from a user to create a custom project, you can provide a list of custom fields upfront, and ask the user to choose existing fields instead of creating new ones. Out of the box, Jira doesn't provide an easy way to export the custom field list to a csv file to share with non Jira admin users. In this blog I will share how I exported all Jira custom fields into a csv file using Jira REST API and Python. This solution was tested on Jira Data Center version 8.x, Python3 and Windows 11. Let's see how we can get the custom field list in 3 easy steps. Note : I assume that you

How to setup bump bump solve in Jira (Jira Cloud & Jira Data Center)

Hello All ! One of the pain points of working on support tickets is following up on tickets when more information is needed from the reporter. This can take quite a bit of time from support agents when they have to go into each "Pending" ticket daily and add a comment for the reporter reminding that more information is needed to process the ticket. If there is a way to setup auto follow ups on tickets and resolve them if there is no response from the reporter ( bump bump solve ), this will reduce a considerable amount of work from support agents daily. Out of the box Jira doesn't provide an option to set this up. After doing some thinking, I was able to come up with a solution using SLAs and Jira Project automations to implement "bump bump solve" for a Jira Service Management project. In this blog I will go over the solution and how I set this up in Jira. Scenario: IT team members put tickets in to "Pending" status when they are waiting for more inform