Create Branch workflow trigger runs as wrong user

[murray.tait]

We've configured a workflow trigger to move issues from To-Do to In progress when a branch is created via GitLab. When branches are created by user A, the issue's activity log shows that user B has moved it to In Progress, and vice versa. Part of the workflow actions is to assign the issue to the current user (in case it isn't already), which is messing up the assignment of the issues.

Has anyone encountered anything similar before?

[Mercy]

This happens because branch creation triggers in Jira Cloud don’t run under the identity of the Git user who created the branch. The automation comes through the DVCS integration service account that Jira uses to process repository events, so the workflow transition appears as if it was performed by whichever account is linked to that integration. That’s why you’re seeing the issue move under the “wrong” user and why the “assign to current user” post function doesn’t behave as expected. Atlassian’s [workflow triggers documentation](