Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation - Create multiple issues based on variable checkbox values

I'm attempting to automate the creation of a set of linked issues based on values selected in a checkbox (which is only editable in a workflow transition). Automation rule is setup per following:



When value changes for Checkbox Field "CSM Project type"

Issue fields condition CSM Project Type contains any of "Value 1"

Then: Clone issue with Summary = ABC

Then: Clone issue with Summary = DEF

Issue fields condition CSM Project Type contains any of "Value 2"

Then: Clone issue with Summary = GHI

Issue fields condition CSM Project Type contains any of "Value 3"

Then: Clone issue with Summary = JKL


Branch rule - All Created Issues

> Edit Issues

    Copy other custom fields from 'master' ticket and set the request types


The rule runs fine and as expected when all values are set in the checkboxes.

However, when one is left out, it stops running the remaining issue fields conditions checks and doesn't run my branch rule. In the above example, if Value 2 isn't set, the Value 3 actions aren't ran.

I tried If/Else conditions at one point but it doesn't suit my needs - I would need to write an excessive amount of "New Action" components to cover every possible combination of the checkboxes.

Is there something obvious I'm missing that will allow all condition checks & asssociated actions to run, without creating conditions for every possible combination of the checkbox values?

Thanks in advance,



2 answers

Hi @Zac Robertson 

How many values/conditions do you need to check?  (i.e. the number of cases leading to cloning issues)

For a "simple" rule, I suspect that you would need nearly the same number of rule components, regardless of how you implement this: branch on current issue/JQL or if/else conditions.

And FYI: there is a 60 component limit for a rule, so check your math to learn if the rule is even possible.  For example looking at the rule you posted, you could have a maximum of 27 cases.

Another way to solve this would be to use advanced branching and iterate on the cases, stored in a smart value, and then edit your created issue fields, one at a time, within the branch.  The limit for that path would be 100 cases.  Please take a look at this article if you want to try that approach:

However you choose to solve this, this sounds like a potentially long running rule, and so could fail if it runs often enough to trigger an SLA limit for automation (e.g. processing time per hour)

Kind regards,

0 votes

Try branches 🙂

Suggest an answer

Log in or Sign up to answer
Site Admin

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