Is it better to split up big rules into smaler ones?

[Maximilian Daum]

The scenario is the following:

We are going to use JIRA Software and JIRA Service Desk. The requests from service desk will be link to issues in jira software projects. We want to use automation rules to transmit comments posted to a request to the linked issue and vice versa.

Now I'd like to know if there is a difference in performance or execution delay if we use very general rules (e.g. if an issue is commented on post the comment to the linked issue but only if  the linked issue is a service desk request).

Or if it would be better to split the rules into smaller ones (e.g. a rule like the one above but separate for every jira software project: if an issue is commented on and is from a specific project post the comment to the linked issue but only if the linked issue is a service desk request)

Thanks for your help

[Deleted user · Accepted solution]

Hey there Maximilian,

It sounds like if you have one big rule, you'd still have different branches in the same rule to match on different conditions.

In that case, the individual rules will generally complete end to end faster.

Having said that, we're working on improving end to end performance and scalability all the time, so which ever way you go, you should see an improvement over time. 

Cheers,

Mark C

[Alexey Matveev · Accepted solution]

 Hello,

You should do the load testing to be sure. But in my experience with the plugin the less rules the better. But of course every situation is unique.

[Maximilian Daum]

Thank you for your reply.