About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Map multiple choice Priority selection from Google Form to Jira

  • 16 July 2021
  • 3 replies
  • 318 views
D

I’m attempting to create a JIRA ticket from a Google Form.

In the Google Form, I have the user select the Priority of the ticket using a Multiple Choice field (see Image1); however, the zap attempts to create a Jira ticket with a Priority using the text string selected.  The JIRA issue creation process is expecting a numeric value for Priority.  Since I do not want my users selecting a number (10000, 5, 4, etc.) for the Priority, how can I map the text selection to the number necessary for Jira issue creation?

Image1
​​​​
Priority selection in Zapier “set up action” section
Error received since JIRA is expecting a numeric value for Priority field

 

icon

Best answer by Wemakefuture 18 July 2021, 23:36

View original
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

Wemakefuture
Userlevel 6
Badge +7

Hi @djairship ,

Great question. You can either do this with:

  1. A “Formatter by Zapier” action 
  2. A code action with some javascript in it for example.

The fastest way is to use the Zapier formatter → Utilities → Lookup Table. In here you can make a table which maps each item to a new different item. See below.

Hope this helps you. Please let me know!

~Bjorn from Wemakefuture

https://www.wemakefuture.com/
D

Thanks @Wemakefuture!  The problem now is that the JIRA item is being created before the formatter can make the change.  I think this is happening because I’m using two different zaps to accomplish 1. the formatter and 2. the JIRA ticket creation.  If I upgrade to a paid account, I can add more than one action to my zaps.  So, I’m thinking that once I do that, I will combine the actions into one zap that will format the fields and then create the JIRA ticket.  Do you think that will work?

nicksimard
Userlevel 7
Badge +11

Hi @djairship!

I think that would definitely help with your problem :) By adding the actions into a single Zap you can define the order in which those should happen. When you have separate Zaps, you can’t *really* control which one will trigger first, unfortunately.

Terms & Conditions