Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I have a team that has a recurring set of work to do every month. That work is set up as an Epic, with a bunch of tasks and subtasks. More than 200 issues in all. I have other, similarly set up rules that create 10-15 issues.
Since there's a limit on the number of components allowed in a single rule, I have broken this up into several rules. These rules are all currently triggered by the creation of the epic.
The epic is created on a schedule, so these rules need to have the box checked to allow other rules to trigger them. I end up seeing the warning about the concern around an endless loop in the rules (though it's not an endless loop... just a lot of issues!)
I'm wondering how to fix this. If I can't have one rule that creates all of the issues, the next best thing would be if I could end each of the rules with an action that says "start this next rule with the same issue (the epic) as its trigger issue".
Is there some other way to do this?
Thanks! Automation for Jira has been incredible to use. (This reminds me to go leave a review!)
p.s. Clicking my way through creating 200+ issues was maddening... I ended up exporting the rules in JSON and then writing a script to generate the JSON to import the rules I needed. Worked great! I realize this is unsupported and likely to change between versions, but I can't imagine doing this any other way.
Hi Kevin,
thanks for the message and the kind words about Automation for Jira!
To be honest, this is probably not the ideal use case for Automation.
The limits are set to protect performance and our UI doesn't really handle so many components that well. In this case, you might be best either writing a script that hits Jira's API directly or using the Scriptrunner Integration.
Sorry I couldn't offer more help on this one in this case.
Let me know if you have any other questions.
Cheers,
John
Hi John,
FWIW, Automation for Jira has really been working quite well for us, even with this "create 200 issues" thing :)
Anyhow, thanks for clarifying that this is not within the general cases you're looking to support. I do understand it's an outlier.
Thanks
Kevin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No problem Kevin and thanks for the feedback. Just give a shout if you need anything else. Enjoy your weekend!
John
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.