I have a project where requests are logged for different areas of work. Based on the area of the project, I have automations that generate sets of tasks linked to that request.
Currently, I have a number of automations that trigger on issue creation and check an issue field to determine what tasks to create. This has led to dozens of automations running when an issue is created. All but one will run in fractions of a second, but that's still time that adds up.
Because these tasks are being linked together in different ways based on which ones need to be done first, and we need for different sets of tasks per area, I cannot consolidate everything into single automation or use "Create sub-tasks".
Is there a more efficient way to accomplish this?
An approach seems related to what you are trying to improve. For example,
Unfortunately, rules are limited to 64 components (I believe) so no ginormous rule to cover all cases with if/else... and there is no action yet to call-out to another rule, as a sub-routine, to divide and conquer.
One alternative would be to use scheduled triggers, JQL, and an indicator field to say "processed". Such as:
You could schedule these as often as you believe you would need the tasks available. And clone the rule for each area of work type. The rules should only fire once per issue creation due to the JQL and the processed indicator.
My goal is to reduce total processing time. With many automations firing when an issue is created, it feels like there's a lot of wasted time.
I'm going to give a scheduled method a try. That way, one will only run once a day rather than every time an issue is created.
Thanks for the idea!
Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...