In this scenario, I have an automation rule that modifies a text field box based on what the customer fills out in the portal. In the portal I have 1-10 item fields (fields are dynamic, up to 10 different items can be picked if needed, or as little as 1) that can be selected (based on the amount needed by the customer).
I have devised the automation in two ways:
So my question is: Will the Current Issue branching rule cause a degradation in performance?
*1st Automation shown below*
What problem are you trying to solve? This is what I use to guide the automation rules I write...
Regarding your question about branching: according to documentation and community posts, branches which evaluate at design time to one-and-only one issue (e.g. current issue branch) get converted into in-line code and so are as fast as possible. Multi-issue branches get executed asynchronously and there is no guarantee when the spun off pieces will complete...and certainly not before the next steps after the branch. So indeterminate performance and certainly slower.
In my opinion since it a good practice to :
It always better to go for the short!
You'll have more chance to reuse the parts for other purpose, and you'll reduce the impact.
Talking purely about performance it should be almost the same but you can try both of the solution and see in the log how many time it take to run!
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