Issue Summary

When using workflow triggers, if the username does not match with Jira cloud then the workflow transitions are shown as performed by Anonymous users. Especially when Bitbucket can perform an auto-decline.

• Single Jira user with a matching email address — Transition the issue as the Jira user.

• No Jira users with a matching email address — Transition the issue as an anonymous user. When we can’t match a user to the trigger, we move the issue with an anonymous user. This doesn’t mean there are anonymous users with access to your Jira site.

• Multiple users with a matching email address in Jira — Try to find a matching username in that group of users. If there is a Jira user with a matching username, transition the issue as the Jira user. If there is no matching username, transition the issue as an anonymous user.

Suggestion

To have a dedicated system account performing the transition so that users can identify easily.

Actual Results

The issue history for the transition states that it was performed by an anonymous user.

Workaround

The Workaround is to use Automation instead of Workflow Triggers. The same events that are in workflow triggers are available as Automation triggers (as well as deployment events, nbot available as workflow triggers) and will transnition the issue as the user "Automation for Jira". This is preferable and more powerful that workfow triggers. Automation triggers however do not work for FishEye and BBDC events unless (for BBDC) you configure the OAuth integration with Jira Cloud as per the guide here: https://confluence.atlassian.com/bitbucketserver/link-bitbucket-with-jira-776640408.html Also note that for non-premium users, Automation is a paid for add-on.