Question to how Jira works optimistic locking / race condition.

[Artur]

Hello Atlassian Team! :)

Here is my case: I build a complex rule that should include mentioned users in a comment to a customfield I called "experts_needanswer". The mentions gets added by a variable "mentionedUsers" and through a branch.

The rule is working as intended and causes no errors, but there is a situation, when this rule triggers (on issue commented) and there are more than 2 mentions, then the issue may not work properly. That means not every mentioned accountId will be added to the field, even though the rule acknowledged that the amount of mentioned users. For example 5 users mentioned, only 2 were added.

I tried to analyse this issue with Rovo. Rovo called this issue "Race Condition" and say that this error may happen, because Jira tries to add all the mentioned users at the same time (parallel), that's why some mentions got ignored, because due to the process of the first mentions. I hope I described it well enough to you to understand the issue.

Currently I suggested my team a workaround and they should pay attention, when they write a comment and when mentioned users that wasn't added by the rule, should be added manually.

Is there a way to solve this issue automatically or is it a known limitation?

Thank you in advance

Best regards,

Artur Schäfer

[Mikael Sandberg]

Rovo is correct, it is a known limitation and unfortunately there is no way around it. You could add a delay and a re-fetch in the automation, but it is not a guarantee that it will solve the issue.