RELATED IDEAS
New user role 'Approver' to change status without permission to change feature details
We would like the option to assign permissions to our Engineering leads, so that they have the ability to review features and approve the feature description by changing the status from “Ready to develop” to “In development”. They should not be provided with the right to edit/change the feature description.
-
ADMIN RESPONSEDec 1, 2017
Thank you for your idea. As you already know, we currently have 4 tiers of users permissions within Aha! (product owners, contributors, reviewers and viewers). We have spent much time gathering feedback from the community in constructing these permission levels. We do not have plans to add new permission levels but one workaround for this use case would be to leverage to-dos. Once a feature is ready for review, you could assign a to-do to the Engineering lead(s). Once the to-do has been completed, the product owner would be notified and could update the feature status.
At this time, we do not have plans to make changes to the user permissions model based on community feedback and our current goals and initiatives.
1
MERGED
User class with permission to update feature status
It would be nice to either have a new user class or to allow reviewers to update feature status in addition to completing to dos and commenting. The features section has enough functionality that a team could use it without another development too...
0
Unlikely to implement