Rerun Mass Automations on Tickets

[Ethan Beadling]

Hi Guys, I was looking for a way to combat Jira issues when it comes to automations. We have a high flow project with alot of tickets coming in with alot of automations running on these tickets. When Jira servers experience automation errors, 400+ emails get skips on these automations. The issue with this is that we have over 200+ rules to sort things out. 

Is there a way for us to rerun these rules since half of those rules that are necessary to this process run on when the ticket is created?

[Aaron Geister _Trundl_]

@Ethan Beadling 

Welcome Ethan to the community and hope this finds you well. So one of the ways I have combated this in the past was to create a scheduled automation that I can run adhoc or created a manual automation that I can run adhoc.

I would think if your running automation based on creation there maybe another way to think about what else could trigger these.

If the only thought is "IDK" I would use a schedule automation that runs at the cadence you want or even set it to be like a year or two. If you set it out to be years you can turn it off and on based on adhoc needs and then in the automation at the top right corner you should see RUN. You can use this to run the issue whenever you need.

This should help to adhoc correct your automation issues.

I hope this helps you with your issue, and welcome again to the community.

[Aaron Geister _Trundl_]

I would like to add that you can copy your current automation's and then just change the trigger to schedule.

Also you can change the name or at least what I do to ADhoc at the beginning of the name.
I also usually will put my Adhoc automation in a group.

[Ethan Beadling]

Hi Aaron! Thank you for your response!

Can you clarify what ADHOC is to me please? The issue I'm running into is that I have about 100 separate rules that run on ticket creation alone and the reason why we cant consolidate these rules is due to company processes and how we are managing these. With the mass amount of emails that are coming in though daily, I worry about hitting the rate limits for automation when we run scheduled tasks. 

[Marc - Devoteam]

Hi @Ethan Beadling 

I fully agree with @Aaron Geister _Trundl_ solution.

But I think it would be useful to look at you automation stats and see which rules get triggered a lot, is there scope correct?

And also check long running rules, is the configuration fine or can it be improved and the scope off-course.

Loads of JQL searching can really have a major effect on performance.

If you didn't already have looked at these options already.

[Ethan Beadling]

The rules get triggered just fine on these tickets as its just checking the subject line and assigning a component accordingly. However when Jira encounters automation issues, these rules don't get reran on the tickets and they get skipped unfortunately.