I have to merge a smaller Jira Software Server instance into a bigger one.
I read a lot of blog posts about it and the process is now clear for me.
However there are projects in the smaller instance, which use the same project key as project in the bigger instance?
To add to the complexity both instances are linked with Confluence servers, which need to be merged too.
In which system is better to change the project key - the source (before merging) or the target (again before merging)?
Let's imagine that the project key is ABC and we have issue ABC-1 in both instances.
If I change the key in the source instance to DEF, then the issue ABC-1 will be accessible by two issue keys - DEF-1 and ABC-1.
OK, but now if I move project DEF to the other instance and search for issue ABC-1, which issue will be returned - DEF-1 or ABC-1 from the target instance?
I am trying to anticipate all problems with incoming links that will arise after the merge
If you change the issue key still you face some issue when you try to merge the two instance. You may try to explore other options.
As you have smaller Jira instance you can export all the ticket in excel format. Then create a project with key DEF in your bigger instance and upload all the tickets in DEF project. Please use csv format to import this.
Follow the below process than.
Create an empty project with key DEF in bigger instance. Make sure all the configuration is same like ABC project of Smaller instance.
If you have a existing empty project in biger instance, you will get a ' 'Overwrite Project Details' option during Project restore, please uncheck it. So your new project will display with DEF key only. It will not accessible by ABC key anymore.
There is a very simple solution to your "project keys problem".
Before starting the merge you must do the following.
1. Rename the project on the small JIRA system
2. Export the Project, use the XML backup
3. Delete the already renamed and exported project.
4. Import back the project via the XML importer.
This way you will loose the records in DB for the old key in the DB.
Do not forget to try this on a test instance :)
To see what kind of problem you can expect you can take a look at the presentation that I've made on the European Summit 2017 here ->
or at the community
@Jack Graves [AC] first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this follow...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs