Skip to main content

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 the default customer satisfaction (CSAT) survey, make sure to disable this first.

Creating the google form

Once the Jira ticket is resolved, reporter of the ticket will get an email containing a link to a google form to collect feedback on the support received. Below is a sample of the google form that we can setup.


Follow instructions in here to create a google form with specific questions you need to include. Make sure there is a short text field for the Jira issue key. In that way we can make sure surveys are linked to a Jira ticket.

Getting a pre-filled link for the google form

Now that the google form is created, we need a way to auto populate the Jira issue key into the google form when the reporter clicks on the link.

This can be done by url parameters. We need to identify the ID of the "Jira issue key" field on the google form first. Then we can set a value to this field by updating the url.

In order to find the unique ID of the field, we need to get the "pre-filled link" of the google form we created. Follow below steps to get a "pre-filled link" with the "TEST-1" value set for the "Jira issue key" field.

Step 1 : Open the google form in edit view.
Step 2: Click the "Get pre-filled link" option under the three dots.

Step 3: A new tab will open with the google form. Then enter "TEST-1" into the "Jira issue key" field.
Step 4: Click on the "Get link" button at the bottom. 


Step 5: Then you will see a pop up on the bottom left of the screen. Click on the "COPY LINK" section in that pop up.


The link that was copied will look something similar to this (Below exact url has been disabled for privacy reasons) :

https://docs.google.com/forms/d/e/4FAIpQLScxLPjuQ4fvwE5eNLOl862w76S6M9aXtM1xEz0pCxJhqOdfig/viewform?usp=pp_url&entry.2000496593=TEST-1

Important part of this link is "entry.2000496593=TEST-1". The part "entry.2000496593" is the ID of the "Jira issue key" field in the google form and "TEST-1" is the value that goes in to this field.

Updating the Resolve notification to include the survey url

Now that we know the ID of the field, we can change the Request resolved customer notification in the Jira service management project to include the actual Jira issue key in the email to the customer. We can do this by replacing "TEST-1" with "${issue.key}" in the url.

Let's follow below steps to make the above change.

Step 1 : Navigate to the customer notification section in the Jira service management project

Step 2 : Open the "Request resolved" notification template by clicking on "Edit"
Step 3: Then update the notification template to include the pre-filled url of the google form and add entry.2000496593=${issue.key} to include the actual Jira issue key. 

Make sure to only keep "Reporter (customer)" in the "To" section. This will make sure only the reporter of the request receive the email containing the link to the survey.
Step 4: Save the changes.

Sample of the email that will be sent to reporter when the request is resolved.

Once the user clicks on the link in the above email, user will be directed to the below form where Jira issue key is auto filled.


Thank you for taking your time to read this blog. Hope this helps !


Comments

Popular posts from this blog

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

How to export Jira project lead email addresses to csv (Jira Data Center)

Hello All! Upgrading a large Jira Data Center instance is no easy task. One of the main steps of this process is communicating to project leads about this. When there are hundreds of Jira projects in your instance, it can be tedious to manually find the email address of each project lead. In this blog I will share how I exported all Jira project lead email addresses 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 this email list in 3 easy steps. Note: I assume that you have Python setup in your environment where you will run the script in Step 3 and you know how to run a python script. Also, that you have access to all Jira projects in the instance because REST API will only return data from projects where you have access.  Step 1: Login to your Jira instance. Go to the url https://your.instance.domain/rest/api/2/project?expand=lead. This url will return all projects in