Issue Summary

On moving a Jira issue key from one project to another project in Jira, Bitbucket associates the pull request and branch information to 2 Jira issue keys (Old issue key and new issue key). This causes duplicate pull requests and branch information to appear in Jira development panel.

This is reproducible on Data Center: yes
Issue is reproducible on Jira Cloud as well.

Steps to Reproduce

1. Create a repository (repo1) in Bitbucket
2. Create 2 projects in Jira (HOT, COOL)
3. Create an issue in HOT, i.e HOT-1
4. Create a new branch in Bitbucket (branch1)
5. Push a change to branch1
6. specifying issue key HOT-1 in the commit message and Create a pull request specifying issue key HOT-1 in the pull request title
7. You will see the commit and pull request details appearing in Jira development panel for issue HOT-1
8. Move the issue key HOT-1 from one project to another project in Jira, in this case, HOT to COOL project
9. The issue key HOT-1 is changed to COOL-1 in project COOL
10. Push another commit to the branch branch1 specifying the latest issue key which is COOL-1 and create a pull request specifying issue key COOL-1 in the pull request title
11. You will now see 2 pull requests (#1 duplicate records) and 2 branches in Jira development panel.

Expected Results

Only one pull request per PR ID/branch per branch is expected to appear in Jira development panel

Actual Results

Two pull request records per PR ID/ 2 branch records per branch appear in Jira development panel.

Workaround

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