Changing Jira, Confluence and Bitbucket Access URL

[Yogesh Mude]

Hello All,

We have to different teams which are using two separate Jira instance to manages their work/project now we are planning to merge these two different instances to one and we want to have a common access/base URL.

Let say, we have two Jira, ie. Jira A and Jira B...for two teams. Jira A access URL is jiraA.xyz.com and Jira B access URL is jiraB.mno.com and after merging these to Jira A and Jira B instance, we want to have a common access URL called jira.abc.com..so both the team can access Jira with this new URL.

So my question is after merging what are the things we need to take care of...

1. As we have integration between Jira, confluence, and bitbucket.

2. Where are all we need to change the access URL? like application links, confluence user macro, rest API, GIT repo URL etc..

3. WHat are the precaution we need to take care of before merging.

If anybody has done this before so please share your thought on the same or any suggestion will be a great help for us.

Note: We are going to merge Jira, confluence, and Bitbucket one after another.

Thanks in advance.

Yogesh.

[Nikola Ilo]

@Yogesh Mudeyou might also want to check if regenerating the bitbucket data is enough for your requirements.

[Nikola Ilo]

Hi @Yogesh Mude

all Atlassian products use Application Links to access and reference data from each other.

First the products check the remote appid is used to identify the target instance, then product specific keys are used to identify the issue/page/...

An incomplete list of references:

• Jira -> Confluence: Saves as "RemoteIssueLink" in the remote_link table
• Confluence -> Jira: There are references in Macros in the bodycontent table
• Jira -> Bitbucket:  Depends on your config but usually in the AO_E8B6CC_* tables
• Bitbucket -> Jira: This is the exception that does not use appids, so should work unless issue keys change

As far as I know (please correct me if I'm wrong) neither Configuration Manager nor Project Configurator handle changed ids in other products (e.g. change Jira references in Confluence macros, change Confluence Page Id in Jira). You will need to write some custom scripts here to fix this.

We developed AtlasMerge to handle this and many other migration/consolidation challenges. Feel free to contact me if you are interested in Atlassian consolidation as a service.

[Yogesh Mude]

Hello @Nic Brough -Adaptavist- 

Any additional suggestions on the same. 

Thanks.

[Yogesh Mude]

Hello Pramodh,

Thanks for the response :)

Yeah, we can use the Project configurator or Configuration Manager app to move projects from secondary Jira to the primary.

But what about the development history (like bitbucket ) is integrated with secondary Jira it has diff project key and all ...after moving the data/project from secondary to primary will this carried out? or what would be the precautions we can take so that the data should not loose and same for confluence page and all.

After merging secondary Jira to primary, is that we need to update the confluence page link as well? 

[Pramodh M]

Hi @Yogesh Mude 

You have to have one primary instance that is the main one. Once you have decided which is the main instance, let's look at the steps you need to follow

Take the system backup of the secondary instance, and in addition to that inspect the apps you are using in the second instance.

Now all you have to do is import the secondary instance to primary instance project wise. Here what we to notice is copying attachments, copy the contents inside the attachments directory as it is into primary instance.

Make sure you don't have same project key for multiple projects while importing.

Install the apps in primary instance.

If there were application links configured in secondary instance, you have to redo it manually in the instance you are importing.

While this is all the main things, to make sure everything is fine, you can note down the facts in system info and cross check once the import is done.

Best to carry it out in test instance first and then on production.

Thanks,
Pramodh