How to allow users to manage releases, and nothing else?

[Juanma]

As the title says we want to allow users to be able to manage releases, and I know we can make them project admins to gain such permission, but it comes with several others that we don't want them to have.

So, from what I saw a project admin grants access to modify:

1. Details ✘
2. People ✘
3. Issue layout ✘
4. Versions ✔ (or Releases as shown in the project view)
5. Components ✘

Is there a way to just let them manage releases?

I know there are plugins that would help, and for a price, but we would expect that something as simple and important as this would be available out-of-the box in Jira.

[Angélica Luz]

Hello Juanma,

Thank you for reaching out to Atlassian Community!

When using Jira Cloud, as you mentioned, the only way to allow a user to manage version is by giving Administrator permission.

There is a feature request opened since 2004 requestion to allow some administrators permissions to users without giving them full access. I understand it's an old feature, but they are still receiving feedback. The last update is from March last year about next-gen projects:

• Required: Project Group Administrator

We also have a feature specific for Versions:

• Separate Project permissions for Version Management

Please, click on vote and watch to receive updates about the feature and feel free to add your feedback as well on the links above.

Regards,
Angélica

[Juanma]

Thanks for your reply, Angélica.

Sadly, creating next-gen projects doesn't resolve the problem, and it's not only far-off from what people has been asking for all these years, it doesn't have anything to do with the issue at hand.

That Atlassian even proposes something like that as a solution displays a complete lack of understanding of the users' needs.

It's a very simple feature request that should have been part of Jira since day 1. No company will be able to scale properly if it doesn't have the means to manage such simple permissions.

Jira has a lot of potential, but its limitations come from a narrow product vision which resulted in poor implementations such as this. Next-gen project won't solve things.