How to set automation to change field values

Question

Hi,
Can you give me some advise, how to set the field value change using automation?

I have a field of type Radion Button called "Signature" and it has 2 values - Active and Passive. This field will only be for issue type "Signature" where there will be only 2 tickets. I need an automation that will make, that if I have a value of "Active" on one of the tickets, the other ticket will automatically have a value of "Passive".

When I change the value on one of them, I need it to change on the other issue the other way around (from Passive to Active, or from Active to Passive).

Is it necessary to have these tickets linked?

Florian Bonniec · Accepted Answer

Hi @Andrea Kolářová

It will be easier if linked. Otherwise you can run a JQL branch. Make sure to uncheck "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule." as update of the field edit the same field.

Regards

Tomislav Tobijas · Accepted Answer

Hi @Andrea Kolářová ,

I wouldn't say it's necessary to have them linked, although I'm wondering what's the use case here. 👀

Anyway, you could construct something like the following rule:

where I've just used branch to find that other 'fixed' issue for which radio button field should be changed. By just adding IF/ELSE (e.g. if Signature = Active > set Signature in other issue to "Passive" and vice versa), this should work.

Now, it all also depends if you're going to configure this on project level, or do you need to configure it on a global level, without the need to specific issue keys for other/linked Signature issue.

Hope this helps.

Cheers,
Tobi

Bill Sheboy · Accepted Answer

Hi @Andrea Kolářová -- Welcome to the Atlassian Community!

What problem are you trying to solve with this field and the two issues?  That is, "why do this?"  Knowing that may help the community to offer better suggestions.

Until we know that...

While you could use issue linking or JQL searches in automation rules to find the issues and "flip" the field values, that may be a brittle solution.  There are a variety of reasons when rules may not run as expected (or when needed).  And so relying upon rules to keep the values "inverted" may not be 100% errorproof.  Knowing the "problem to solve" will help reveal other possible approaches.

Kind regards,
Bill

Andrea Kolářová · Accepted Answer

Thank you all, I finally found a way how to setup this automation.