Issue Summary

When an issue is transitioned to Closed from the portal and a comment is added, this triggers an automation that re-opens the issue when commented. Now it leads to a race condition where Jira is closing an issue while automation is re-opening it and it messes up the Issue History despite the right events being performed by Jira

Steps to Reproduce

1. Add a customer transition to Resolved status as shown in Show a workflow transition in the portal
2. Create an automation that would re-open a ticket(move to IN Progress) when a comment is added in Resolved status.
3. Now on the portal, transition the issue quickly add a comment, and observe the changes
4. Changes made by the automation appear as made by the reporter who resolved the ticket which is incorrect

NOTE: This isn't always reproducible

Expected Results

The initiator must be clearly updated in the issue history

Actual Results

The initiator on these events appears messed up in the Issue History

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available