Issue Summary

When a commit for a fork is received, the commit message is indexed but a remote event to update Jira's dev panel is not triggered in Bitbucket. (Edit: The Fork is in a standard project, not personal. Personal Forks do not trigger these events under normal circumstances)

Steps to Reproduce

1. Create a fork with fork syncing enabled or disabled
2. Push a unique commit to just the fork with a Jira issue key
3. Check the Jira issue and see no commits in the dev panel

Expected Results

Jira dev panel should be updated with the new commit hash from the forked repository

Actual Results

Jira dev panel shows no commits

Workaround

1. Pushing a commit to the upstream repo with the same Jira issue key will trigger a new remote event that will also contain the commit data for the fork, updating the dev panel with commit information for both commits.
2. Create a Pull-Request from the fork to the upstream. This will trigger the remote event and update the dev panel