Due to a merger/acquisition my organization has two Jira instances. There is an organization wide instance and a smaller instance. We all want to move towards using the org wide instance but still need to access the project data.
Problem: these two instances of Jira are at different versions and both have their own set of custom objects. (fields, workflows, screens, etc)
Migrating projects from one server to the other seems like it will be a serious bit of work. Federating the servers seems like a good way to keep the info from the old server available (for searches, dashboards, etc) without risk.
Am I looking at this the wrong way? What are the downsides to federating?
Well, there's no easy federated searching.
You're right about merging, it's a lot of work.
The simplest approach is to offer to configure the main Jira as needed for the users who currently work in the smaller Jira. Get them to start using the main Jira. Make the small Jira's issues, comments etc read-only. Leave the small Jira alone and work should naturally move to the main Jira. Your reports will be messed up for a few months but things settle down in time.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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