About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

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

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

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.

Best answer

Only create issues in Jira for first alerts in New Relic?

  • 19 August 2021
  • 3 replies
  • 46 views
D

Hi,

 

I create a Zap between New Relic and Jira Cloud which woks fine. 

I’ll give an example - a high CPU alert in NR creates a new issue in Jira. When the condition changes (the CPU load goes down), there is another alert in NR and a new issue in Jira. Anybody knows how can I avoid the second issue to be created or, better, to update the existing issue in Jira?

 

Thanks,

 

Daniel

icon

Best answer by Troy Tessalone 20 August 2021, 16:23

View original
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @dhertanu 

Try these Jira steps in the Zap.

 

Action: Jira - Find Issue

Action: Jira - Update Issue

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
D

Hello @Troy Tessalone,

 

Thanks for your reply. I’m trying since yesterday to make this work and I’m not  there yet so I’m trying to clarify something first. 

I guess you are saying to have New Relic - Jira Find - Jira Update - Jira Create in the same Zap? 

Is this the way it should work?

 

Thanks,

 

Daniel

Troy Tessalone
Userlevel 7
Badge +14

Hi @dhertanu 

Try one of these setups…

 

Zap Steps

  1. Trigger: New Alert or Deployment
  2. Action: Jira - Find/Create Issue (only if the Find Issue action has a checkbox option to also Create Issue)
  3. Action: Jira - Update Issue

 

Zap Steps

  1. Trigger: New Alert or Deployment
  2. Action: Jira - Find Issue
  3. Action: Paths
  4. Action: Path A - Filter (Issue does NOT exist)
  5. Action: Path A - Jira - Create Issue
  6. Action: Path B - Filter (Issue exists)
  7. Action: Path B - Jira - Update Issue
⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
Terms & Conditions