multiple environments in Jira Enterprice

[Eric Roetenberg]

Help Question:

We recently got Jira Enterprice Cloud within our organization we were always on Premium. Now Enterprice offers the ability to work with multiple environments we would like to do this. We have 105 Agile Safe projects that we want to move to another environment. Who has a roadmap for this and can tell me more about how to go about it. And is this also arrange with separate license and or AddOn's that we have to use for this. Will the URL to the project also change.

As you hear a lot of questions

Who can help us on our way. 

Grtz.  Eric

[Ollie Guan]

Hi @Eric Roetenberg ,

As @Walter Buggenhout  mentioned, splitting and migration are lossy. You need to give up some convenience or change some previous usage habits, but it will also bring some good aspects, such as permission management and streamlined plug-in authorization.

To some extent, you can also automate functions for different sites under the enterprise plan. In any case, I suggest you first determine why you want to split the existing site, what problems the split can solve, and what new problems it will bring, rather than splitting for the sake of splitting.

[Eric Roetenberg]

Hi ,
We want to move to split to better manage AddOn
We have projects that need an ADdOn but only 10 users work with this while we pay the addOn for 1800

[Ollie Guan]

This is indeed a compelling reason and it will bring you cost savings.

[Ollie Guan]

BTW,

What are the benefits of multiple instances?

Do multiple instances affect app costs in Enterprise plans?

[Walter Buggenhout]

Hi @Eric Roetenberg,

Jira Cloud has a data copy feature available that allows you to copy projects from one instance to another. Settings as well as data are copied over in the process. As one important piece of advice: before you jump in head first and start moving things around, read through the documentation thoroughly so you understand e.g. what data is copied and what isn't.

If you move data to another environment (also known as another site), that new site will indeed have a different URL, even though the data copy will retain the project name and key from the original site.

Apps (AddOns) are to be purchased per site. If some teams need a certain app and other teams don't, you can set up separate sites for these teams and only purchase the apps where you need them.

A final recommendation: make a good assessment of where teams need to work together and where it is ok to separate them. As splitting sites can be interesting to save costs on app licenses (e.g), splitting work across different sites can also introduce factual silos that - in turn - create new synchronisation challenges.

Hope this helps!

[Eric Roetenberg]

Thanks for your quick response, so do I need to create a new instance first. can I also do this from my Admin tool. or do you do this through the Atlassian website(new Jira cloud product) and is this then also automatic Jira Enterprice

[Trudy Claspill]

Hello @Eric Roetenberg 

Chiming in...

In an Enterprise subscription you create a new site from https://admin.atlassian.com

If you have access to more than one Atlassian Cloud Organization, make sure you select your company's Organization.

Go to the Products tab and select Add Product.

You can add a product to an existing site in the Organization or indicate that a new site should be created for that product.

Each Product can exist only once within a given site. If you already have Jira under the URL https://abc.atlassian.net then you can't add a second copy/instance of Jira to that same site URL. You have to add a new site/URL for that new copy of Jira.