DevOps Triggers in Automation for Jira Server/DC

Issue Summary

When a pull request is created in Bitbucket, there is an automation that transitions a Jira issue to the next status.

Automation for Jira is not able to capture the user that created the pull request in Bitbucket to assign as Assignee in the Jira issue, since the status is changed by the automation between Jira and BitBucket.

Steps to Reproduce

1. Create a DVCS Integration between Jira and BitBucket
2. Create a Pull Request in Bitbucket
3. Jira issue is transitioned to the next status by existing automation between Bitbucket and Jira.

Expected Results

Automation for Jira could capture the action to manipulate the user information.

Actual Results

The trigger can only be capture when the status is changed, however, it is not possible to get the User Information, as the status was changed by the automation between Jira and Bitbucket.

Workaround

There is no current workaround.