Request Participants immediately repopulated after automation rule removed them

[Michael Reznicek]

Hello,

we have a automation rule in place which immediately removes Request Participants after an issue is opened by email. This week it happened that the rule ran successfully and removed the participants but they were immediately repopulated.

Does anyone have an idea why and how this happened?

Greets,

Michael

[John Funk]

Hi Michael - Welcome to the Atlassian Community!

I assume you are obfuscating a user name that put the Request Participants values back in. That tends to happen if there is a Post Function on your workflow that might be happening - that's why you see the person's name instead of Automation for Jira. 

See if that might be the case, or even check with the user to make sure they didn't actually put them back in. 

[Michael Reznicek]

I checked with the user and they were not put back in on purpose. I also don't think its something with the workflow. This rule is in place since months and was executed hundreds of times and that is the first time that that happened.

[John Funk]

If you look at the list of Automation Rules executed for this issue, does it show any other ones executed at the same time as the one that cleared it? 

Did it do it one time with this issue and then not again? IOW, is it still happening? 

What's the timeframe between the time the Automation rule cleared it and the time that they were added back? Seconds? Minutes? Longer?

[Michael Reznicek]

Hello,

all updates, the deletion and the addition of the participants happened in the same minute. Only this one rule was executed and this issue happened on two different occassions.

[John Funk]

That doesn't seem to line up with the screenshot of the history above. It shows that Automation for Jira updated the Request Participants, and then someone else (not Automation for Jira) updated the Request Participants right after that. That sounds like either a post function on the workflow or the person came behind it and updated. Or you have some other non automation rule that is running that is doing that. 

[Jack Brickey]

Hi @Michael Reznicek , can you look into the History tab to see if there is a clue?

[Michael Reznicek]

Thank you for your quick response. The attached screenshot is from the history tab. It states that the same user who opened the ticket updated the request participants before and after the automation ran.

[Jack Brickey]

To be clear, does the "all" tab show this precise chronological events

1. request participants added at create
2.  request participants Removed by automation 
3. request participants Added by reporter

without any events between?

[Michael Reznicek]

yes, that was the order