User with 'Manage Versions' permission cannot be selected as Release Driver (Project Admin required)

[오예찬]

Summary Users with the newly introduced Manage Versions permission cannot be selected as a "Driver" in the Release Hub. The user list currently seems to filter users based on the legacy Administer Projects permission only.

Steps to Reproduce

1. Create a user (e.g., User A).

2. Grant User A only the Manage Versions permission in a project (ensure they do NOT have Administer Projects permission).

3. Navigate to the Project Releases page (Release Hub).

4. Create or Edit a Version.

5. Attempt to search for User A in the "Driver" field.

Expected Behavior User A should be searchable and selectable as a Driver because they have the explicit permission to manage versions.

Actual Behavior User A is not found in the search list. The field only displays users who have the Administer Projects permission.

Questions  I believe that logically, the Manage Versions permission should allow a user to be assigned as a Driver. They are asking for clarification on the following:

1. Is this behavior (requiring Project Admin) a strict policy/intended design even after the release of the new permission?

2. Is there a roadmap or scheduled update to fix this logic? Please confirm if this is a known bug or a gap in the current feature implementation.

[Trudy Claspill]

Hello @오예찬 

Welcome to the Atlassian community.

I have seen other community members document the same behaviour that you are seeing.

I have not found anything in the public backlog about this issue.

https://jira.atlassian.com/secure/MyJiraHome.jspa

I recommend that you ask your Jira Administrators to open a support request about this behaviour and ask Atlassian Support directly if this is already a known and documented issue or if it is intended behaviour that will not be changed.

It would be helpful to the community if your report back here what you learn from Atlassian.

[Trudy Claspill]

@오예찬 

I have upgraded my own environment to a Jira Standard trial plan to try to recreate this.

I was able to recreate the issue and have submitted a support case myself to get more information from Atlassian.

[오예찬]

@Trudy Claspill 

Thank you for taking the time to replicate the issue and submit a support case. Please share the response from Atlassian once you receive it.🙏

[Trudy Claspill]

Here is the response from Atlassian technical support:

------

I’ve checked with the developers, and we’ve found that this is, at the moment, an expected behavior documented in our documentation. See the document below:

• https://support.atlassian.com/jira-software-cloud/docs/create-a-version-in-a-classic-project/

Create a version

1. From your space navigation, select Releases.

2. Select Create version.

When you create a version, you can enter the:

• Name: choose a name that’s easily identifiable for your teammates so they can recognise the version.

• Start date: the date work on the version will start.

• Release date: the planned release date for the version.

• Description: more information about what you plan to release in the version.

• Driver: someone in your team with administrator permissions who’s responsible for coordinating the release from start to finish (by default, it’s the person who creates the version).

However, while discussing with the dev team, we’ve recognized the importance of improving the way the ‘Releases/Versions' creation and driver process is being done. This is why we’ve created the feature request below:

•  JRACLOUD-97201: Unable to add Non-admins with 'Manage versions' access as 'Drivers' when creating a new release in Jira Cloud