How to properly make repeating tasks with automations without hitting rule limit.

Question

I am trying to set up a rule that will make a new, identical ticket when I've completed a ticket. I am currently setting up the rules like the following steps:

* Trigger: When Issue is transition to Done
* Labels contains and of "every_4w"
* Then Create a new Issue where the due date is +4weeks from "now"

I have similar issues but am using different labels to determine the new due date.

The issue is that every time a task is moved to Done, all of the rules are triggered. This project is made up of repeating and non-repeating tasks. It looks like I can make a single rule with conditions, but this will still trigger on non-repeating tasks.

Is there a way to limit which tasks use automations so I don't use all 100 on the first 100 tickets I complete?

I had assumed that an automation would only count if completed. It was a surprise that incomplete rules count towards the 100.

Thanks!

Angélica Luz · Answer

Hi Krista,

Yes, the manual trigger will only count if someone clicks to run it.

Using another status is also an option, so the ticket can be transitioned to Done and if it’s something that needs to be cloned, then transition to Repeat, and the automation will run.

The limit of conditions on the automation is 65:

A single rule contains more than 65 conditions, branches, and actions.

What are service limits?

Krista M_u0t2jd · Answer

Ah, yes this is helpful. I didn’t realize there was a manual options. Will manual only run a single run then?

I was also thinking of maybe making a new status that is in the completed status category called “Repeat” or something like that. Then, changing the rules to only look at that status instead of Done.

Is there a limit to the number of conditions in a rule? I have a dozen labels that I would like to have determine the next ticket’s due date if it is repeated. (Ex. If I repeat a task with the “Every_wed” label, the due date auto-advances to the next wed). I thought having all of the labels as if-thens after the single trigger might be a way to cut down on the number of automations that run.

Angélica Luz · Answer

Hello @Krista M,

Welcome to the Atlassian Community!

Testing on my local site, I was able to replicate what you mentioned.

When creating a global or a project rule, the automation will always try to execute the rule due to the trigger. Since the trigger is "When a ticket is transitioned to Done", all tickets that are transitioned to this status will fall under that automation rule.

In this case, since you are using a Free site and there is a limit, my suggestion would be to use a manual trigger, so when the ticket needs to be Cloned, you or your teammates manually execute the rule.

Hope this helps!

Kind regards,
Angélica