Summary

When multiple Jira instances are applinked to a Bitbucket instance, a user may see unexpected commits when viewing an issue. This can occur under two conditions:

• The same project name and issue key are in use across multiple instances (expected).
• A project originally had the same name across multiple instances but has been renamed to a unique value (not expected).

Steps to Reproduce

1. Create two Jira instances.
2. Create new projects with the same name/key across both instances (e.g., FOO).
3. Rename (name and key) the project on one instance (e.g., BAR).
4. Create a test issue in each project (e.g., FOO-1, BAR-1).
5. Link both Jira instances to a Bitbucket instance.
6. Create a repo in BB for each project.
7. Commit a file in Bitbucket and reference the issue key for each project in the respective commit message (e.g. commit -m "FOO-1 test commit" and commit -m "BAR-1 test commit")

Expected Results

Only commits relevant to this particular issue should be observed when viewing issues in their respective Jira instances.

Actual Results

When navigating to issue BAR-1 you'll see commits for both  FOO-1 and BAR-1.
When navigating to issue FOO-1 you'll only see a commit for FOO-1.

Workaround

Creating a backup, deleting and re-importing project BAR from backup will resolve the problem. You will only see commits for **BAR-1.