About the management scope of different JIRA administrator

In our JIRA platform,we managed some different business projects, so there are many JIRA administrators, and the JIRA administrators could see the projects that not belongs to them. From security perspective, it is not good management.

For example:

Current situation:

administratorsA managed projectA

administratorsB managed projectB

but administratorsA could check both projectA and projectB

Expected situation:

administratorsA could only check projectA but not projectB
administratorsB could not check projectA and only check projectB

Is it possible configure on the JIRA?
Or maybe other better solution?

Thanks in advance!

2 answers

0 votes
Maarten Cautreels Community Champion Jun 03, 2017

Hi HongChao,

What do you understand with the term Administrator? There's a few different administrator roles within JIRA:

  • System Administrator: can administer everything, addons, system settings, all projects, etc
  • JIRA Administrator: can do many administrative tasks except the ones listed on Managing global permissions. But still has access to all projects
  • Project Administrator: can administer only the configuration of the projects he's the project administrator for.

So from reading your post I guess your looking for the Project Administrator role instead of the JIRA or System Administrator role. To learn more about project roles check Managing Project Roles on Confluence.

Hope this helps.



Sorry for the bad expression.

In fact, we need the role between JIRA Administrator and Project Administrator, that could  do many administrative tasks but only  access to the projects belongs to one business group.

In other words, we want to customized system privilege, for exampe, even only somebody could use see/use some buttons.

Is it possible through configuration to achive the target?

Or must revise source code?

Could you please give us some advice?

No, you'd need to hack apartall the permission code and rewrite it.

Atlassian are moving towards giving project administrators more delegated power, but it's going to take a log time.

To  achive the goal that customized system privilege through revising based source code or add-on , is it reasonable?

I wouldn't try it, it's a massive rewrite, and Atlassian are going down that road already.

thanks, I think so.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 29, 2019 in Jira Software

Transforming Jira Software projects for general project management purposes

...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....

182 views 0 6
Read article

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