Skip to main content

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.

  • IT team members put tickets in to "Pending" status when they are waiting for more information from the reporter. 
  • If there is no response from the reporter after 2 business days, a comment needs to be added to the ticket reminding the reporter that the IT team member is waiting on them.
  • If there is no response from the reporter after 5 business days, a comment needs to be added to the ticket reminding the reporter that the IT team member is waiting on them .
  • If there is no response from the reporter after 6 business days, resolve the ticket.

Tracking time spent in "Pending" status

Assumptions : Once a ticket is in "Pending" status it can only transition into "In Progress", "Waiting for support", "Resolved" and "Cancelled" statuses.
  • Key part of this solution is tracking the time elapsed since the status of the ticket changed to "Pending". 
  • We can do this by creating a new SLA metric named "Waiting for customer".  Goal for this SLA will be 48h (8x6). 
  • We will need to use a calendar which reflects correct time zone and business hours. 
  • SLA will start counting when the ticket is moved to the "Pending" status and the SLA will stop when a comment is added by a customer (reporter or request participants) or when the status moved out to any other status from "Pending".
  • By using the "status = Pending" JQL for the SLA, it will make sure the "Waiting for customer" SLA clock will only be visible when the ticket is in "Pending" status. 
Configure Jira SLA Metrics

Adding comments and resolving the ticket

Once we have setup the SLAs to track the time elapsed in "Pending" status, the next thing is to setup automations to add a comment to the ticket after 2 days, 5 days, and resolve the tickets after 6 days.

We will need 3 separate automations which will add comments after 2,5 days and resolve the ticket after 6 days.

Automation #1 - Comment on pending tickets after 2 day
Jira automations

Automation #2 - Comment on pending tickets after 5 days
Jira automations

Automation #3 - Resolve pending tickets after 6 days
Jira automations

That's it, configuring a new SLA along with three simple automations we have implemented "bump bump solve" in a Jira Service Management project. 

Thanks for taking time to read this post and hope this helps you !


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 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. Scenario: 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 Timezone Hours (M-F) Time to resolution Barcelona CET 9:00 AM - 5:00 PM 40h New York EST 9:00 AM - 5:00 PM 40h Los

How to send a survey with multiple questions in Jira Service Management (Jira Cloud & Jira Data Center)

Hello All, Out of the box Jira Service Management only allows to add one question for the customer satisfaction (CSAT) survey once a ticket is resolved. But most teams like to collect feedback on different aspects of the support provided to the customer by adding more than one question. In this blog I will go over a workaround to send multiple questions to the customer when a ticket is resolved.  Scenario Support team uses Jira Service Management to work on customer requests. Once a request is resolved an email needs to be sent to the customer with a survey including multiple questions. Survey response needs to be tied to the Jira ticket number. Solution In order to send multiple questions we will use a google form.  When the ticket is resolved the reporter will get an email with a link to a google form containing the survey questions.  The first field of the google form will contain (this will be autofilled) the issue key where the user received the survey. Given that we are not using