Add "Request participants" to issue, instead of changing existing ones - two automation rules

Filip Prokop September 8, 2023

Hello,

I'm propably overthinking it much, and the answer is really simple, but i just cant get it right.

I created two automation rules:

  1. If the issue is created by X, change "Request participants" field to user Name1
  2. If the issue type is "Onboarding", change "Request participants" field to user Name2

The rules both work fine, except when user X creates issue type "Onboarding".

In that case, both rules are executed, and they override each other.

Capture.PNG

Problem is, they don't always get executed in the same order (looks like it's random), so I cant just add "Copy from issue" to "Request participants" field, in the rule, that runs as second one.

Easiest fix would be, if the "Request participants" field added new user, instead of replacing existing.

2 answers

1 accepted

1 vote
Answer accepted
Filip Prokop September 8, 2023

Ah, I just realized after posting the question.

I'll just add "Copy from issue" to both automation rules, therefore it doesn't matter which rule gets executed first, as they both will work as "add", instead of replacing the field.

1 vote
Arkadiusz Inglot
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 8, 2023

Hello

1. What is more important in this case? Onboarding or Reporter (user X) to set the values in your problematic case?

2. Create one rule and make proper if statements. Ths below is an example and you should set IFs which suits you properly, as both triggers which you described (1, 2) do not exclude eachother.jira-auto.jpg

Filip Prokop September 10, 2023

Well, they are both equally important and need to be executed toghether if needed.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events