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.

Integration Type: Jira to Azure DevOps

Is it possible to update a field other then Status when performing the Jira Update action?  It is the only field that appears in the Setup.  I am trying to stop Zapier from creating duplicates when I create a work item on a Jira issue update.  My solution is to create a custom field that I can set the value to a specific value after the work item is created.  That way I can do a check for the updated value and avoid creating a duplicate every time the sync happens.

 

Thanks!

Hi @ChadUnbehaun 

Just with Jira app in Zapier, you can only update the status of an issue. However, you can use “Webhook by Zapier” to make API request to Jira in order to make update other than status.

To prevent duplication, you can use “Find Issue” to search an issue whether it exists. Alternatively, you can store the issues ID and corresponding data in Azure in a google sheet, so that you can check whether it exists or not.

Thanks!  So if I understand this, Zapier does not keep track of the metadata associate with Jira or DevOps issues such that Zapier can determine if a particular field has changed.  To do this, the user has to keep track of the field values they are interested in to check to see if something has changed?

Just wanted to follow up here to note add that there’s an existing feature request to have the ability to update custom fields when using the Update Issue action in Jira. I’ve added @ChadUnbehaun’s vote to this and we’ll be in touch by email once that’s possible.
 

So if I understand this, Zapier does not keep track of the metadata associate with Jira or DevOps issues such that Zapier can determine if a particular field has changed


In some cases, Zapier does keep track of changes. For example, with polling triggers Zapier stores an identifier for each item to determine whether the items it finds should be triggered on. You can find out more about this here: Data deduplication in Zaps

Hey friends! 👋🏽 I wanted to pop in and update that custom fields are now available in the “Create/Update Issues” actions! Woohoo! 🎉

 

Terms & Conditions