Restricting Ability to Create Versions in "release" page / Work arounds.

[Tin Nguyen]

As of currently Atlassian does not have a more granular feature set within the permissions scheme to allow more granular control of things such as versions. I want my release cycle to create the version through automation which is currently happening without an issue.

My dilemma is that the permission is just a default permissions of project administrator. We want to prevent users from creating Version's and allow the automation to do that for them.

I am not sure how I can approach this but maybe some kind of automation or listener that checks for versions that are not created by the automation user gets deleted....

Looking to hear what kind of options the community suggests.

[Vikrant Yadav]

Hi @Tin Nguyen  Welcome to Atlassian Community!

Only Users which are added in Administrator project role is only have permission to create new releases/version in a project. You can remove other users from this role so that limited user will have permission to create releses in a jira project.

How users are creating a new version , all users are added in Administrator user role or in Administer permission any logged in users is added ? 

Are you trying to create new version via Project Automation ? It should be automatic or manual trigger automation rule ?

[Tin Nguyen]

I don't want a single human user creating any versions but I want the people to still be able to administer the projects. the roles/people the boards, the components, etc....

Essentially not a single human user should be creating a version to release its all done via an automated pipeline that triggers various deployment jobs that will create the version, attach all tickets to that version for release based on deployment.

With this in mind it also helps keep our reporting in check versus it all being manual. The problem comes with the fact that I want product teams to administer the projects but not have permissions to create a version.  (not possible)

an alternative I thought was some kind of automation that deletes any version created in projects in (x,y,z) to be deleted unless created by the deployment automation user.

[Vikrant Yadav]

Unfortunately, it's not possible to restrict only Create Version permission. You need to restrict Administer project permission, then only Create Version can be blocked. 

You can create Manual Automation with Input Screen, to create version/components via Automation. 

[Tin Nguyen]

Hello Vikrant,

Thanks for providing additional insight.

The creation of Versions is not a concern as I can do that via API and do not want a local automation to do this as it is based on passing testing pipelines that creates versions and schedules releases based on those triggers.

But it looks like being able to have a fully automated release without humans creating their own releases to keep reporting up to date everything is going to be impossible at this time.

---

the TL/DR answer:  This is impossible to do at this time.