Can you update more than just the status field in a Jira issue?

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