Skip to main content

How to setup Jira ticket creation via email from a google form using app script



If you use Jira as your issue tracker and Google Forms to collect user feedback, you can streamline your workflow by automatically creating a Jira ticket for each new form submission. In this blog post, we'll walk you through the steps to set up an email script that sends form responses to Jira as tickets.Set up a Jira account

If you don't already have a Jira account, you'll need to create one. Go to the Jira website and sign up for a new account. Once you have an account, create a new project and note down the project key.Create a Google Form

Next, create a new Google Form to collect user feedback. In the form, add fields for the user's name, email address, and feedback. You can also add additional fields as needed.Set up a Google Apps Script

Open the Google Form and click on the three-dot menu in the upper right corner. From the drop-down menu, select "Script editor". This will open a new tab with the Google Apps Script editor.

In the script editor, create a new function and give it a name, such as "sendToJira". In the function, you'll need to write a script that sends an email to Jira with the form data.Write the email script

Here's an example email script that you can modify to fit your needs:




This script takes the form submission data and formats it into an email that is sent to your Jira email address. Make sure to replace "your_jira_email_address_here@yourdomain.com" with your actual Jira email address.Test the script

Before you can use the script to create Jira tickets, you'll need to test it to make sure it's working properly. To do this, go back to the Google Form and submit a test response. Then, open the script editor and click on the "Run" button. This will run the script and send an email to your Jira email address with the test response data.Set up the email trigger

Once you've tested the script and verified that it's working, you can set up an email trigger to automatically create Jira tickets for new form submissions. To do this, go back to the Google Form and click on the three-dot menu in the upper right corner. From the drop-down menu, select "Script editor". In the script editor, click on the "Triggers" button in the left sidebar. Click on the "Add Trigger" button and set up a trigger that runs the "sendToJira" function whenever a new form submission is received.Create Jira tickets from form submissions

With the email trigger set up, your script will automatically create a Jira ticket for each new form submission. The email script will send an email to your Jira email address, which will create a new ticket in Jira with the form submission data.

In conclusion, creating a Jira ticket from a Google Form submission can save you time and streamline your workflow. By following the steps outlined in this blog post, you can set up an email script that sends form responses to Jira as tickets. With this automation in place, you'll be able to quickly and easily create Jira tickets for user feedback, bug

Comments

Post a Comment

Popular posts from this blog

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...
Post a Comment
Read more

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...
Post a Comment
Read more

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:...
Post a Comment
Read more