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.

Currently, we have a flow that sends a Slack channel message when a Jira issue on our Project is moved to Review status.  Super simple flow, not using an API or anything, just the built in Jira Software Cloud app.  However, this flow also triggers any time after that initial trigger if the ticket is updated, specifically when a comment is added.  

Is there a way to set this flow to only trigger one time, and then filter out any subsequent updates.  Our team only needs to be notified once when the ticket is put into Review status, and does not need to be notified when comments are added. 

Yes you can definitely add a filter on this using Filter By Zapier step before sending Slack message,

The issue seems to be that you have setup Trigger that when a Project project is updated the status is Review, then send a message, so when a comment is added to it this trigger fires as well since the status is Review and it is updated with a comment.

You might add another filter in it, such that if comment does not exist. For this field you will have to look through the Data out of the Trigger field.

Hi there ​@kathryn1 👋

How did you get on with Mohammad_Shahzaib_Nawaz’s suggestion of adding a filter? Did it work as hoped?

Want to make sure you’re all set so let us know if you need any further help at all! 

Hey Sam, 

Mohammed’s suggestion was great.  Unfortunately we cannot use comments not existing as the filter to filter as the ticket already has comments on it in this stage, but I will look into what other fields we can use.  Maybe a label would work. 
However, it would be nice to have a setting for the Zap that states to only trigger once per Jira issue.  

Thanks for getting back to me ​@kathryn1! Glad you liked their suggestion—thanks ​@Mohammad_Shahzaib_Nawaz! 🙌

Ooh, yes a label could be a good way of getting around that. 🤔 Keep us posted on how you get on with it!  

However, it would be nice to have a setting for the Zap that states to only trigger once per Jira issue.  

I’d suggest reaching out to our Support team to flag need for an option to be added to set it to ignore new comments. They’ll be able to put in a new feature request for that on your behalf.

And if the label approach doesn’t pan out, perhaps you could use something like Zapier Tables to store a record of the ticket? For that you’d use a Find Record action, (which has the ability to create a new record if an existing one isn’t found) and the filter could be set to continue only if that Find Record action created a new record. Suggesting Tables here as it wouldn’t count towards your task usage.

If you give that a try and run into any issues or have any follow up questions at all do let me know—I’d be happy to assist further! 🙂

Terms & Conditions