Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Trigger an action when issue count is reached?

I'm using JIRA to track product returns to try to improve visibility of common problems. I'd like to set up some sort of trigger / action to alert someone or raise an issue type when, for example, 3 issues with the same label are raised within a 30 day period.


Does anyone have any experience of this sort of thing? There must be something to help spot patterns to avoid relying on humans? 





2 answers

If you use the Jira Server or DC version - I  would recommend using the Alert Catcher add-on for such case ( You can create rules and conditions for aggregating the issues and assignee them to the team lead.

More details about how to use the plugin for problem management (as a mass incident) you could find by the link below:

Thanks for your reply, Dmitry. I use Jira Cloud. Would this not work with Jira Cloud?

Not yet, but the cloud version is on the roadmap :).

Like Lewis Foster likes this
Andy Heinzer Atlassian Team Jul 13, 2021

Hi @Dmitry Kozyarevich -Softlist- 

Thanks for contributing to our community.  In the future though we would ask that you please review our Community guidelines for Marketplace vendors.  I can see that you have already added your organization name to your name, but we want to make sure that when you recommend your own product as a solution that you also disclose your affiliation.



Like # people like this
0 votes
Daniel Ebers Community Leader Jul 17, 2021

Hi @Lewis Foster

I also could think of an Automation rule (Automation comes with your Jira Cloud plan at no additional cost!) to get informed about critical circumstances in customer support related to inquiries of your customers:


In this example the CRM team would receive a mail when there are more then two requests opened with support team that are labeled as complaint.

You could tweak it according to your needs and I can see that it could get complex when there are many, many use cases. Probably it would be a good idea to speak with the team which (let's say three or four) use cases are pressing the most.
For them you could craft some automation rules.


Please also refer to the documentation which you can find here:


Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you