Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best practices Multiple instances

Hello Community ! 

We are currently planning on moving from server to cloud around september, 

But I would like an advice on some best practices. 

For now we have 1 jira (core/software/conf/service management) for all the company, and another instance because we have just aquired another company which already have jira cloud instance. 

1) For our main jira that we plan to migrate, is it better to have small separate instances, so the dev teams can have more autonomy on their projects (and just centralized the system admin), or let it in the same instance as it is ? 

2) Do you think it is better to integrate the other instance (the one already in the cloud) in our jira or to let it that way ? 

Thank you very much for your help !

1 comment

Hello @Camille 

Welcome to the community.

When you say the dev teams can have more autonomy on their projects, exactly what do you mean by that?

In general I would suggest having one cloud instance. That should reduce the administration overhead, and allow the team members to easily cross boundaries and share information between projects. But I would like to understand what you mean by "autonomy" so that I might provide a response that is more related to your needs.

Like Matthias Gaiser _K15t_ likes this

Hi @Trudy Claspill ,

Thank you for your response ! 

Well, for now I (as an Admin) am the only one who can make all the changes in jira system. For example if they need to change their workflow or want to create a new project ... 

So I was wondering if having little instances where they can be Admin of theirs, can be a solution ... 

But you are right, it would totally reduce the administration overhead..

In the Cloud offering there are two types of projects

- Company Managed (previously known as "classic")

- Team Managed (previously known as "next gen")

You can have both types of projects in one Cloud instance.

Company Managed projects are like what you have experienced with JIRA Server.

Team Managed projects were implemented to give teams more autonomy to manage the workflows and custom fields for themselves. But those customizations become unique to that one Team Managed project and cannot be shared, and they don't have all the same functionality that you are used to in the Company Managed projects.

You might want to do some research on Company Managed vs. Team Managed projects to see if that will suit your needs for giving more autonomy to the teams.

Like Matthias Gaiser _K15t_ likes this

I'm backing what @Trudy Claspill said, in general I'd also aim for one instance. That makes collaboration a lot easier.

The team-managed projects might be a solution for giving teams more control over their projects. Here are some links to get you started:

Hope that might help to get you into the topic.

Thank you very much , that was very helpful. 

I am going to read the articles you sent, to be more prepared. 

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira Service Management

Security Advisory for Jira Service Management

On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link.  We've seen a number of questions already asking for...

54 views 0 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you