Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

  • Home
  • Get Help
  • Troubleshooting
  • Salesforce to Jira Service Management: New Cases in SF not appearing dynamically in Jira Service Management.

Hi all :)

Curious to know how to make sure that each time there is a new Case careated in SF with record type X 

Jira Service Managment will create a new service request or Issue in Jira.

I am using the Salesforce Jira Zap template and my issue is that the cases created in Jira as Service requests are not dynamic but static. 

So each time I create a new case in SF from record type X, in Jira it will appear as the same case number that I used when testing the Zap (with the same static values).

To better illustrate this, I added a screenshot. So instead of the salesforce Subject fileds to have a dynamic value of each newly create case in SF, it shows me the same value: Test 23.06. Same goes for the Case Number filed, is constantly shows me the same number 00023774 and not the number of each new case created in SF.

 

What am I doing wrong? 

 

 



Anyone has this issue?

Hi @MoovOne Operations!

Is this happening while you’re testing the Zap in the editor, or when the Zap is published and running live?

If it’s during testing, that would simply require that you retrieve new test records from your trigger step, then use that in subsequent action steps. Based on your screenshot, it looks like you’ve mapped a field that would produce dynamic results when the Zap runs.

Reply


Terms & Conditions