RELATED IDEAS
permission-restricted release or feature status
We should be able to configure specific release statuses so that they're restricted, editable only by certain users or user groups.
We have a Program Management group which maintains an authoritative list of releases the product organization has committed to. We need to be able to differentiate between the releases that have been formally committed and those that haven't (which we can accomplish with custom release status, a tag, or a custom field), but more importantly we need to restrict which users can edit that attribute.
Maybe a simpler way to achieve this would be with permission-restricted custom fields, but even for custom fields we can't currently set up permissions restricted only to certain users or user groups.
-
ADMIN RESPONSEJun 2, 2016
Thank you for the request. In these types of scenarios, we suggest maintaining a process with the team to let them know that only certain people can edit/configure specific release statuses.
One area that may help would be to use the Transition buttons. Transition buttons allow you to show options which can be selected (based on the current status of the item). You could encourage your team to solely use the transition buttons when updating status (and only show buttons when these are items which can be changed by everyone).
While we understand that this is a workaround, we hope that it can at least help (when combined with your internal processes). At this time, we do not have plans to make updates in this area based on current priorities. We hope you can understand.
© 2024 Aha! Labs Inc.•All rights reserved
This feature would be helpful as we currently have to give clients access to workspace so they see all Releases listed even ones we do not want to share.