If automation triggers on an issue update, is it better to have a separate rule for each field?

[Cash Coyne]

In automation, if you're triggering on an issue update, is it better to have a separate rule for each field that you're interested in that got an update, or should you have one rule and if statements based on the field(s) that were updated?

[John Funk · Accepted solution]

Hi Cash,

If the fields are related and the actions you are performing the rule are the same more or less, the put them together in one rule. If they are totally independent actions then I would make multiple rules.

[Bill Sheboy]

Hi @Cash Coyne 

Yes, and...to John's answer:

Please consider what problem is a rule trying to solve.  When possible, having one rule to solve each problem may help to have "one version of the truth", rather than creating a maintenance problem of rules getting out of sync.

Another consideration is the recent change to the packaging model and rule limits.  That may be less impactful for your teams, as you appear to be on a Premium license.  When usage is a concern, using many more, smaller rules with additional conditions or a larger, complicated rule need to be compared for impact on monthly rule limits and fit to solving the problem.

Kind regards,
Bill