Jira (Selfhosted): How to deal with different departments (clients) with multiple Jira-Projects each

Thomas Grotzeck [Administrator]

Hi there,

is there any recommendation / best practice for the following use-case:

- Jira should be installed as self-hosted version in a company

- several departments should use Jira for their work but each dept. is isolated from the rest

- each department can create as many Jira-projects as required. It's important, that a newly created Jira-Project can be seen by the creating dept only.

- each Dept. can configure their own Jira-Project as they want. They cannot destroy / impact any configuration of another department.

- Finally, all projects of a department can be deleted without impacting any other department.

 

Questions:

A. Is such a (multi-client) setup possible without having a super-admin involved?

B. Can the departments separated in a way, that even basic configs (WF, Issues etc) are valid within the department only?

 

Just in case I didn't make clear what we want to do. We want to mimik the behaviour of Jira Remote hosted service:

Dept. A creates a Jira Environment, Dept B and C do the same: 

So we have:

https://Dept-A.atlassian.net/
https://Dept-B.atlassian.net/
https://Dept-C.atlassian.net/

Each department can now create and configure whatever they want without impacting the other.

Is such a setup possible with a self-hosted version without running destinct server for each department?

Hope it's clear what we want to achive and thanks a lot for any input.

Regards
Thomas

 

Nic Brough -Adaptavist-

Partly.

It is possible to have separate departments have totally separate projects, with no cross-department visibility (let alone being able to do other stuff).  You can do that in any JIRA installation

But, there's more detail in your points:

>Jira should be installed as self-hosted version in a company

Yes, that's fine.

> several departments should use Jira for their work but each dept. is isolated from the rest

Yes.  You'll want to change the defaults after installation, but that's fine.

> each department can create as many Jira-projects as required. It's important, that a newly created Jira-Project can be seen by the creating dept only.

Also fine, as long as you change the defaults

> each Dept. can configure their own Jira-Project as they want. They cannot destroy / impact any configuration of another department.

This is a little more complex, but yes, you can set up JIRA such that projects are totally independent of each other, and all use separate configurations.  Again, get the defaults right, and you're fine

> Finally, all projects of a department can be deleted without impacting any other department.

Yes

 

Questions:

>A. Is such a (multi-client) setup possible without having a super-admin involved?

No.  Your System and JIRA Administrators will all see, and be able to configure, all departments.  Your project admins will be fine, limited to their projects within their department, but not your system and JIRA admins.

>B. Can the departments separated in a way, that even basic configs (WF, Issues etc) are valid within the department only?

No, you will have to train your admins to know which configs go with which department, or project if you go to that level.

Finally, you say
>We want to mimik the behaviour of Jira Remote hosted service:

Those urls do not make up a JIRA remote hosted service.  Those are three independent remote services.

To mimic that behaviour, you are going to need three separate JIRA installations.  But that solves your "super admin" question, as the installations are totally separate.