[JRACLOUD-34015] Separate Project permissions for Version Management

UIS:
4,585
Support reference count:
78
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

Currently a JIRA user needs to be the Project Administrator to be able to manage Versions in a project.

It would be great if we could have a separate permission for Version management.

duplicates

JRACLOUD-92887 Add granular permissions relating to version control

is duplicated by

JRACLOUD-12891 New permissions item - version maintenance (v3)

JRACLOUD-77231 Create a separate permission for managing versions/releases

is related to

JRACLOUD-67414 As a JIRA administrator, I want a specific set of permissions to see/manage project releases

JRASERVER-34015 Separate Project permissions for Version Management

JRACLOUD-43683 Separate Project permissions for Component Management

relates to

JRACLOUD-3156 Required: Project Group Administrator

JRACLOUD-12891 New permissions item - version maintenance (v3)

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(1 is related to, 2 relates to, 28 mentioned in)

No work has yet been logged on this issue.