NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thank you for taking the time to share your challenges around custom field management. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the next 12-18 months. We will be maintaining this ticket's status as "Gathering Interest" in order to continue learning from all of you about pain points and challenges relating to this suggestion, and will continue to re-visit this ticket in our ongoing product planning.
We recognise that privilege escalation can be a major challenge in using Jira, which is why we are taking steps to improve the flexibility of our permission scheme at all levels. That journey begins with our Extended Project Admin capabilities, which will be released by the end of this year, and which we hope will be just the first step in making Jira permissions more granular and powerful.
We understand that this is not the update you may have been hoping for, especially given the longstanding nature of this issue. Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Aditi Dalal
adalal@atlassian.com
Product Manager, Jira Cloud
It would be great if we could set the permission to manage the Custom Fields (Create new fields, add options to fields) on <your site name>.atlassian.net/secure/admin/ViewCustomFields.jspa without needing a JIRA Administrator global permission.
- is duplicated by
-
JRACLOUD-78038 Permissions on custom fields
- Closed
- is related to
-
JRASERVER-34335 Separate Custom Field management permission
- Gathering Interest
- relates to
-
JRACLOUD-62157 Allow a specific group of users to be able to edit only specific fields
- Closed
- mentioned in
-
Page Loading...