No option for customers to set primary Jira instance while they have multiple Jira instances linked to their single Bitbucket cloud

There is no option for customers to set primary Jira instance while they have multiple Jira instances linked to their single BitBucket cloud. 

In the above scenario, if they have same project names on both Jira instances, the Bitbucket cloud issues Jira key the URL of the Jira instance which was registered first with the Bitbucket cloud account.

Eg: Let's say customer is having two Jira instances https://one/jira and https://two/jira.

Customer will connect these two instances to their Bitbucket cloud account but in the order of 1) https://one/jira  and 2) https://two/jira.

If customer creates project with key "PROJ" in both the instances and issues the Jira key eg: "PROJ-1" to a Bitbucket commit, the Bitbucket will assign URL of Jira instance https://one/jira,, which was registered first.

If customer wants the Jira keys to be linked with second Jira instance https://two/jira. , then customer had to disconnect the first Jira instance https://one/jira.

It will be a good option to let customers group their Jira instances and mark one of them as primary. by doing this customers will be aware of the Jira URL linked to their issued keys.