nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way to only allow a user to modify versions or permissions, but not roles, nor to see any other admin-level information?

Rob Horan

The current "Administer Project" permission is WAY too inclusive.

Accepted answers

Rahul Aich [Nagra]

Unfortunately not, once a user is granted with administer project permissions, he will be able to perform all admin functions of a projects.

There is no way we can isolate one from the other. Its either none or all capabilities that a user gains.

Rahul

All comments

Rahul Aich [Nagra]

Unfortunately not, once a user is granted with administer project permissions, he will be able to perform all admin functions of a projects.

There is no way we can isolate one from the other. Its either none or all capabilities that a user gains.

Rahul

Jobin Kuruvilla [Adaptavist]

The roles edited by a project admin is applicable only for that project. They can't add/delete a role and the changes they make won't impact another project.

There is no way to limit it at the moment.

Nic Brough -Adaptavist-

Rahul and Jobin answered this, but I'd like to add that Atlassian have said that they'd like to break up admin into more layers, and this sort of thing is one part of what they're looking at. As in https://jira.atlassian.com/browse/JRA-3156 (vote and watch...)

Rob Horan

This is really unfortunate. Rather than having to add everything myself I was hoping to grant the ability to manage components and versions to others, but also keep them out of other areas.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

permission