Commits are confused becaus Jira projects with the same name from two instances point to Bitbucket

[Andrea Hakim]

We recently migrated from one Jira instance to another.  The issues in the new instance are showing commits from the old project - even after we rekeyed the project.

Here's the setup:

Jira instance 1, project BI - links to bitbucket

Jira instance 2, project BI - now also links to Bitbucket

If I create an issue in Jira2, BI-430 for example, the commit that was from JIRA2, BI-430 is showing.

We've tried to rename the BI project in Jira2, but it still references the oldkey in Bitbucket.

How do we remedy this?

[Luca Schioppa]

Hi @Andrea Hakim - were you ever able to solve this issue? running into exact same problem. 

[Richard Cross]

Yeah, we were hit by this too, and only discovered this limitation at a point where instance 2 had been in use for a long time. 

There's no warning at the point you create the second link; just the ability on the Bitbucket side to designate one Jira instance as "Primary", but that simply means Bitbucket will try to resolve from that instance first.

On the Jira side, I think it's just looking through the commit messages... which are part of the immutable (in a practical sense) git repo history.

Fundamentally, the scenario of multiple Jira instances pointing at a single Bitbucket instance is not supported.

Short of removing one of the Jira instances from Bitbucket... I'm not sure what can be done.

I have raised a ticket with Atlassian for solutions... if they come back with anything helpful, I'll update here.