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.

Greetings,

I am trying to have a Zap which is triggered, when a Jira Ticket is closed.

I already saw a lot of threads here, suggesting to add a filter condition right after the update to check for the status.

But here is my situation:
Sometimes we have scripts which go over tickets (as well closed ones) to add labels, or versions. In that case, those tickets are touched again and the zap would be executed again (because the ticket is updated and the status is done, even though it was done before already).

Is there a possibility to check if the status just changed to done?

Thanks in advance!

Not knowing what the exact payload of that Zap is, would simply adding another condition i.e. ‘label xyz’ does not exist to the filter be a solution for you?

Not knowing what the exact payload of that Zap is, would simply adding another condition i.e. ‘label xyz’ does not exist to the filter be a solution for you?

thanks for your reply!
That would be an idea, but pretty fragile to unknown stuff which is happening (I would just take care about that one specific label). We are quite a big company. If anyone “invents” some new bulk updates, we would fall in the same trap again.

I see…On Jira-side this could maybe be done via their ‘Automation’. In that case you would just compare status before the update and after, and filter those out that had status ‘Done’ before the update already.

This article might be helpful: https://community.atlassian.com/t5/Jira-questions/Can-you-trigger-an-automation-based-on-specific-field-value/qaq-p/2738282

You could and then connect that to Zapier via webhook. Like this only the trigger would need to be replaced, and the remaining Zap could stay the same.

Hope that helps :)

Hi ​@MarcoS24, just wanted to check in and ask if that would be a solution to your problem.
Best regards!

Terms & Conditions