Different Administrator permission for different projects?

[Billy Knox]

JIRA in our scenario is used by more than one division of the same company. Each division has their own group of JIRA Administrators with their own set of projects and workflows.

Is it possible to prevent other division administrators from having access to our own set of projects, etc?

I know the Dashboard can be setup so that only projects related to the user, etc is shown, but when logged in as an Administrator one is able to find and potentially modify all projects and workflows on the same server.

[Daniel Wester · Accepted solution]

Depending on what you're wanting the JIRA administrators to do, you could use two of our add ons:

Project Creator for JIRA: https://marketplace.atlassian.com/plugins/com.wittified.jira.project-creator can let you set up a group on non-jira admins to create projects (and as of 2.3 - you can have regular users request projects) from a set of standard templates that the JIRA admins create.

Once the projects are set up you can use Delegated Administration for JIRA https://marketplace.atlassian.com/plugins/com.wittified.jira.delegated-admin to allow the project admins to switch their workflows, issue type, screen, field, permissions and notifications schemes. For permissions and notifications they can maintain their own version as well. (We'll be doing some additions in this area in the next couple of months).

[Nic Brough -Adaptavist-]

No.  A JIRA admin is a JIRA admin.  The whole of JIRA is built on sharing globally available objects, so the ability to administrate those must be global as well.