If you already know the benefits of separating one instance of Jira, it’s time to present the process of this configuration. Eight steps are all it takes to enjoy greater security and relatively lower costs through this separation. Learn more about the challenges that await during configuration and the expenses the process may involve.
How to divide a Jira instance?
The entire process depends heavily on the advancement level of your configuration. We start with the preparation of a new server; the environment. Then we can install a new Jira application, remembering a few rules:
- the new application must have the same version number (or higher) than the version already existing on the server;
- you need to create a new home directory for the created application;
- two instances cannot be combined with the same external database.
The next steps will be creating backup data on the original Jira and transferring, restoring them to the new instance. Such duplicate data should be configured to match the needs of users of the second instance.
Key challenges of the division process
- Maintaining another server
This involves costs associated with the preparation of a new server, a virtual machine, or the acquisition of new hosting. Of course, with a relatively small instance of Jira, one would be tempted to use an existing server. However, remember that two instances hosted on one machine, even if separated, will consume more system resources. In this situation, it’s completely unreasonable to expect performance improvement after breaking one instance of Jira into two.
- Management of two configurations
One Jira instance requires at least one administrator – a person who takes care of making changes in workflows, screens, creating new projects, etc. The division brings a challenge because you’ll probably need to assign a new person to the new Jira installation. It can still be the same administrator. However, to decide about it, you need to answer a few questions:
- How much will both configurations have in common?
- Will the configurations be completely disjoint, will the processes will be different?
- Will you have to redesign the current documentation?
Collecting this information will help you to decide if a new role or employee will be necessary.
The price of sharing the Jira application
The expenses involved in the process are an important issue. During the process, we must expect costs such as:
- the cost of preparing a new server;
- the cost of hosting;
- costs associated with maintaining two Jira instances;
- the cost of the implementation team and administrators.
Is separating Jira instances worth it?
Challenges and costs of application splitting are not very encouraging. However, one should remember about all the benefits of division presented in our other articles.
If you’re interested in this topic and have a few more questions, we’ll be happy to answer them. We have extensive experience in dividing applications, as well as combining them.
Solution Architect for Atlassian Jira platform with a holistic approach. He combines strong technical skills with a business-oriented perspective providing a bridge between technical and non-technical stakeholders. Currently, focusing on application integration. Together with a team of experts, he helps companies to design, implement and tune Atlassian products.