Application Links and ServerID

[Bartłomiej F. Tajchman]

Hello, I have a self-hosted Jira linked to self-hosted Bamboo. It works well. I need to split Jira to two instances: self-hosted and cloud. I migrated Jira to cloud and it works well - some projects is in self-hosted Jira and others in cloud one. I have a problem with application link, I'm unable to create link "Jira Cloud" <-> "Bamboo", it says: "The ServerID reported is already being used for an Application Link. This may be because you have multiple applications with the same ServerID". It seems like new Jira Cloud and old Jira self-hosted have the same Server ID. What should I do to create a proper application link "Jira Cloud" <-> "Bamboo" next to working "Jira self-hosted" <-> "Bamboo"?

[Dario B · Accepted solution]

Hi @Bartłomiej F_ Tajchman ,

I can see that you opened a support ticket for this issue and that you actually already solved it by yourself. 

I am pasting  the solution in here in case any other user will be facing the same issue:

Problem solved, we changed Server ID in our Jira Server site and application links started to work. Thanks for answer!

Have a nice day!

Dario

[Deleted user]

Hello there,

I'm having the exact same problem as bart27 described.

However, I would like to leave the server ID in our Jira server instance unchanged.
Is there a way of tackling the problem on the cloud site, by, e.g., changing the serverID of "Jira Cloud" to solve the problem?

Thanks!

[Dario B]

@[deleted] , I am not sure this can actually be done. However, the best way to get an answer on this would be to open a support request using the following link: https://support.atlassian.com/contact

Cheers,
Dario

[Deleted user]

@Dario BThanks! I'll see what support says and update my question later.

[Dario B]

Thanks @[deleted] , looking forward to know whether or not this is actually possible in Cloud.

[Deleted user]

Ok, so here's what Atlassian support said:

Being honest with you, I believe that our approach should be aimed to the server version of Jira instead of the cloud one. I'll elaborate more why.

Our cloud structure is basically created in a way that we from support don't have access to change anything in the instance and in the DB, and to change the serverID, we'd need to change a few things at the DB level.

My suggestion is that we remove all the application links from Jira Server then change the Jira's server ID and finally create the application link.

Here are the steps I'd suggest.

1. Remove the application links from Jira Server, Cloud
2. In Jira server run the instruction of the Changing Server ID for Test Installations;
3. Try and re-create the app links.

Since the issue is currently not critical for our work, we have not tested this procedure.