Please consider fixing this, it just doesn't make sense the way it is. It's weird that a release master needs admin permissions to set the status of a release.

Will there be an update on including this in the roadmap for 2023?  For minor releases or hot fixes, the speed with which a release needs to be created is critical.  Our Jira admins may be occupied due to the higher level nature of their work and may not be available to create the minor releases. 

It would also be nice to have the ability to flag a release as major/minor other than by the semantic naming convention.  The next step would be to then provide the ability to restrict by role for creation based on major or minor, so that we could have minor created by developers and major by project admins.  The Approvers option was added but does not resolve this issue.

+1 still waiting for this.

We want to track our releases in Jira but don't want the devs doing the release to require project admin access to create release versions.
We currently have to ask our 3 project admins to create a release version then we can add the tickets being released to that version.

Especially for minor releases, such as releasing a single microservice from Github, we ask for release version to be created and it is not done because of whatever reason (holiday, sickness, busy,...). It is too easy to forget to follow up. Then that release is not tracked in Jira. 

How much longer do we anticipate waiting? Is the development of this feature underway, or is it currently under discussion to determine whether it will be addressed or not?

 Please provide an update on this issue. A lot of customers (who pays) are interested in.

This functionality is critical…. We want to automate the creation of releases, but only want to grant those permissions to automation accounts. We can’t launch that automation while users with rights to add issues to versions still have rights to modify release properties set by automation. This is a huge blocker for us. It is critical certain properties be immutable.

The approver doesn't help me as I need someone to be able to rename the release and release it.  Anyone could add tickets to the release without being an approver

@Tracy Moffat - If you're on a bundled release track, it should be coming out in the next release (we are, and I'm seeing it in the list of features to be included in our September release.)

Hey Tracy Moffat,

Yea, in our Jira Cloud, when editing a release, we are now able to set "Approver(s)".

Once these approvers are assigned, they gain the ability to make edits to the release and add related work. They can also update the release's "Approval status," with the default being "Pending." They have the option to choose between "Approved" or "Rejected."