Using JIRA Software in more than one company / teams

Initial situation: We want that more than two different teams use JIRA Software.

Each teams are managed by different project / team managers who need to be able to create and manage the projects. But we don’t want neither the project managers or the team members see the projects of the other teams. 

Which possibilities are there to cover these requirements?

 

3 answers

1 accepted

0 vote

Only adminstrators can create projects, but separating your users is completely possible.

The most important thing to do is look at the Permission schemes.  This says "people matching a rule can BROWSE the project".  All you need to do is for one set of projects, make sure one team has BROWSE and they do not have it for the other set of projects.  And similarly for the other team.

The usual problem here is the default that JIRA ships with - the default permission rule is "People in the role of Users can BROWSE the project".  There's nothing wrong with that rule, the problem is that the default also puts the group "jira-users" into that role in every project.  That group is also "people who can log in", so it's everyone.

You will need to undo that - replacing the use of jira-users with your two teams separately.


It sounds like you're saying that you'd like JIRA users on Team 1 to have administrative rights to create and manage projects, but cannot view or administrate projects owned by Team 2. As far as i know, JIRA cannot do this under a single instance. Administrators generally have full access to the system.

Thank you for the answers. 

In order to separate the users, we would also proceed like Nic has described it.

But, we have the problem that the administrators of Team A should not see the projects from Team B. The reason is that we want to use JIRA/Confluence in our enterprise group and the teams are from different companies.

Thus I think we either use individual independent instances in each company/team or we say that we are not restricting the administrators (project managers).

I think an another option is the enterprise-version of atlassian. But I don’t know whether we can restrict the administrators based on teams/companies.. 

Moreover the enterprise version is too expensive and big for us, because we need only 100 User-License for JIRA Software & Confluence.

You can't separate the administrators. What you should do is have Team A with project admins Team B with project admins A dedicated and trusted internal team who have admin rights and can hence see both There is no "enterprise" version of JIRA - whatever you're looking at, it's the same JIRA software (ok, Data Centre is slightly different, but it works the same as far as the JIRA admins are concerned) If you really need that level of separation, then two independent JIRA servers is the answer.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,345 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot