Issue Summary

The Pull request has one Jira issue association and the state is correct on Jira side but on the Bitbucket side, we see unrelated issues in the PR Jira issues tab.

Steps to Reproduce

1. Create a pull request associated with multiple issues.
2. Update the pull request to be associated with one issue.

Expected Results

In Bitbucket, The Jira issue tab shows the correct issue association.

Actual Results

In Bitbucket, we see the issues that were associated with the PR at creation due to the fact that the internal service on Bitbucket side doesn't listen to Pull requests update events.

Workaround

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