In a distributed team, not always the Product Owner (Product Manager) is in charge of all the aspects of a release or a feature. A typical example would be dates, where a Service Manager owns the date changes. In this situation, and when we do not want the Product Owner to lose control of the release information in Aha! there is no simple way to request a date change to be approved by Product Manager.
What we propose is that any fields (dates, status, descriptions, etc.) in release, feature and strategy is eligible to be requested for a change. The Service Manager (viewer/reviewer role) will ask for a change request, Product Owner approves or diminishes it, and if accepted, field is updated.
|Release time frame|
We have spent much time working with the community in finalizing the roles and permissions within Aha! At this time, we do not foresee changes in the user permissions based on community feedback. The primary suggestion in allowing your service managers to generate change requests would be to promote their user type to a contributor, to enable them greater controls within the application