Behavior or Automation for "simple" sync from select list edit to another field?

[Todd Alden]

W/o getting into the details of why we need to do this (has to do with field types and a specific plugin)...

Every time a selection list field is edited, we want to write the value (string) to another field.  So a simple, when edited, write the new value also to another field.  At least 2 ways to do this seem via a Behavior (using ScriptRunner) or using a rule in "Automation for Jira" (newly included for "free" with Jira DC).

We were planning on using Automation, but is one better than the other?  Performance?  Chance or an editing getting "missed" (not sync'd)?

In case it matters, we are using Jira DC, 8.20.6

TIA,

Todd

[Florian Bonniec]

Hi,

I would go with automation for Jira too. Just because by doing that you are sure that it will be triggered.

With behavior if you update the issue from a script or Rest API it will not be triggered but the automation will.

Also you have the audit log with automation in case there is any issue and it's a no code solution. So easier to support.

[Todd Alden]

I was thinking the same.  Thanks for the confirmation on those "pros" for using Automation.