Issue summary

When using Jira integration with Bitbucket Cloud or GitHub, if the workflow is configured to automatically trigger a transition and change the status (e.g., from "To Do" to "In Progress") when a branch is created, Jira will display the last user who committed on the source branch as the author of the status change in the issue history.

This occurs even if that user's account is suspended and they lack the permissions in Jira to make such a status change. Consequently, it is highly likely that the work item history within Jira will be inaccurate, as it may incorrectly attribute the status update to someone unrelated to the specific issue.

This is reproducible on Data Center: no

Steps to Reproduce

1. Integrate Jira Cloud with Bitbucket Cloud or GitHub
2. Configure a project and edit the workflow to trigger a transition when a Branch is created.
3. Add a post-function to assign the issue to the current user.
4. Open a Jira issue and select Create branch and create it.

Expected Results

Optimal results would be The issue is transitioned and assigned to the user who created the branch. 

But this is a known issue and as detailed in the following Documentation this should trigger as an "anonymous" user per Atlassian Documentation on the feature:

• Understand workflow triggers AND
• Troubleshoot workflow triggers

The correct user is only shown on the 'History' and 'Activity' tabs for work items in Jira, and in notification emails. In other notifications (e.g. 'Transitions' tab for work items) an anonymous user is shown.

Do nothing.

This is a known issue that will be fixed in a future release.

Actual Results

The issue is transitioned and assigned to the last user who made the last commit on that branch

NOTING: This does also include users that do not have access to Jira and are flagged as inactive triggering investigations into suspected security breaches due to access bypass concerns.  Issue history show a user action that could not have occurred

Suggested Fix

It would be advantageous if the integration between Bitbucket Cloud or GitHub and Jira reported the branch creator or the authenticated user at the time of the change, rather than attributing the status update to the author of the last commit on the source branch.

See Related Feature Request:

• https://jira.atlassian.com/browse/JRACLOUD-94660

Workaround

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