How to Manage Versions without Jira Good of the Universe Admin Permissions

[Deleted user]

it's April 2023, if I search the commuity knowledge base I find tens of trillions of questions all the same as mine that I'm about to write again: why can't a user of a Jira project manage versions on his own and does one have to be an administrator? Unanswered questions of 2020, of 2019, of 2021, ... can any of you tell me if and how possibly, while waiting for Atlassian to finish the development of emoji smilies for all its products and focus on the functions really needed by those who really work, you can manage the allocation of affected and fix versions on Jira projects? Does one have to buy yet another expensive plugin?
https://community.atlassian.com/t5/Jira-questions/How-do-I-assign-the-permission-to-create-Versions-to-a/qaq-p/677499

[Karin van Driel]

Hi,
Just to clarify, to manage versions, you just need the Administrator role in the project, you don't need to be a Jira Admin.

Project admins can make changes in the configuration of a project that only apply to that project, such as creating versions and components, managing project roles, changing screen layouts etc. They cannot make changes that affect other projects and if you're in a Company Managed project, they cannot make changes to any of the schemes (issue type, screen, permission etc.)

Does that help?

[Deleted user]

Thank you for your reply yes I know very well that you have to be Jira project admin mine was just a hyperbole or a little provocation towards Atlassian to ask why there is not yet a granular permission for versions like there is for example for sprint management or attachments 

So you know a way?

[Horst Kriegers]

I agree with this need. 
We may have to give rights for versions / components but no other rights such as managing project users. Which is currently our case.

Alternatively, a third-party application recommendation?