Our workflow starts with product management creating a roadmap of features and master features in Aha. Engineering responds by changing the status to "understood", "committed", "will not fit", etc. Seeing the history on that provides a record of who committed to implementing a feature so that we can refer back to that history.
Right now, for engineering to be able to do that, they have to have paid licenses in Aha. This seems like a huge waste of money to give them a paid seat just so that they can change the status of features. To enable our workflow, we need to be able to give Reviewers the ability to change status as well as see history on features or master features.
|Release time frame|
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 make changes to the permission levels. 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. We hope you can understand.