Hey @Anton Genkin, Thanks for the update.

So what would happen in other places where things have already jumbled up on the previous commits? Currently we are experiencing this issue where we have upgraded to Jira 8.5 while Bitbucket is on v5.12.2. We are running into a lot of commits linking to incorrect projects on instances that had/have no correspondence to it previously. 

Thanks,
Madhu

Hi everyone, in Jira Software 8.5 and Bitbucket 6.6 we updated Project links, which might help you resolve a problem when several issues have the same project key and point to a single Bitbucket.

Now by clicking on issue key in Bitbucket you will see all relevant issues in Issue dialog. Previously you could see only issue from Jira which was the primary Application link for Bitbucket. Moreover, if you set Project links, the first issue in the dialog will be the one from the selected Jira instance.

Check out Configuring Project Links across Applications to learn more about connecting your projects -
https://confluence.atlassian.com/applinks/configuring-project-links-across-applications-976158802.html

Cheers!

Anton Genkin
Bitbucket Server Product Manager
agenkin@atlassian.com

Our situation is a bit different. We have only one JIRA instance linked to Bitbucket Server. However, the commit messages in our Bitbucket Server sometimes refer to issues in third-party JIRA instances; e.g. if the commit works around a bug in a third-party product, or if it implements a feature that a client of ours is tracking in its JIRA instance to which a few people in our company have access. So far, the project keys have been unique, but I don't know how long that will last. It is not easy to find out which third-party projects have been referenced in this manner, so I fear we won't be reliably able to avoid their project keys when we create projects in our JIRA instance.

I'd like Bitbucket Server to change so that, if a commit message or pull request description contains the absolute URI of a JIRA issue, e.g. "https://jira.atlassian.com/browse/BSERV-4814", then Bitbucket Server should treat that just as a URI and ignore the issue key. That would prevent commits relating to the third-party issue from incorrectly showing up in our JIRA instance, if an issue with the same key is later created there. Perhaps this can already be implemented using integration.jira.key.pattern, but that has its own problems (BSERV-10930, BSERV-10561, BSERV-2470).

However, if some companies are now deliberately putting the URLs of their own JIRA issues in commit messages, then they would not like a new version of Bitbucket Server no longer detecting the issue keys in those URLs. To cover that case, I suppose
Bitbucket Server could let the administrator configure a list of base URLs for each linked JIRA instance; if a URL in a commit message starts with one of those base URLs and contains what looks like an issue key, Bitbucket Server would treat it as a link to an issue in the corresponding JIRA instance. This should allow multiple base URLs per JIRA instance so that Bitbucket Server could keep recognizing old URLs after JIRA instances are renamed or consolidated.

Do you have different Jira projects with the same project keys pointing to a single BbS repo?

We don't.

What Bitbucket Server / Data Center version are you running?

Bitbucket Server 5.15.1.

Do you use Bitbucket Repo Shortcuts in the sidebar?

We have shortcuts to Bitbucket Server repositories in the sidebars of JIRA projects, but generally not in the other direction.
Some JIRA projects have also been linked to Bitbucket Server projects in the application link configuration (https://jira.example/plugins/servlet/applinks/listEntityLinks/com.atlassian.applinks.api.application.jira.JiraProjectEntityType/PROJECTKEY), although I'm not sure that actually affects anything.

As a product manager I'd like tell that our team is actively working on solution for this issue. We hope to ship it in mid-term. Meantime, If you could answer several questions that would help us to validate solution that we have in mind:

• Do you have different Jira projects with the same project keys pointing to a single BbS repo?
• What Bitbucket Server / Data Center version are you running?
• Do you use Bitbucket Repo Shortcuts in the sidebar?

This is an important issue also for Publicis. We would like to link multiple JIRA instance to a central Bitbucket repository and the experience is broken.

This is important to Cisco too.  We are having issues with the application links working correctly from Bitbucket.  On the PR screen when it is linked to a JIRA item, if the project key is on multiple instances then the user must have access to all JIRA instances for it to figure out how to load/display the JIRA info.  

If you are going to make unique project keys a requirement, then that kind of check needs to exist before hand (before the application link is allowed and then before projects can be created if application links are already established).  I think it would be easier to deal with having the information be part of the reference and the security checks only look at the specific JIRA instance.  

a1jira.com , b1jira and c1jira.com are 3 instances share same project key.
The Source tab on those JIRA shows the commit details (which should not be for non-relevant JIRAs), the actual commit details on Stash shows c1jira (which was set as primary) and we expect only c1jira showing commit details.

The issue here is user not part of c1jira, but part of b1jira. How can it be fixed on Stash commit to show right details of JIRA?

regards
Viswa

We need a fix for this, https://support.atlassian.com/servicedesk/customer/portal/24/SSP-12513 is waiting. We have 6 jira instances, although we do the due diligence and prevent duplicate keys across different instances, this is down to individual admins. Fixing this will be key to run a seamless, Central Stash instance for all projects across these 6 jira instances.

byterider, swisscom.scm, unfortunately I don't have an update on plans for this currently.

To help us prioritise and design the right solution, could you describe the issue you're encountering? Is it that issue links are going to the wrong instance?

Same here... all the links to our JIRA tickets are broken.