Provide tools for Change Control

Once development on a release is underway, things happen.  Change Control should encompass approvals and permissions to edit dates and schedule, and rollback. Here are some requirements:

1. A product owner (or an "uber product owner", e.g. the VP of Products) "Starts" the release - by pressing a button e.g. "Start Release"

2. Once the release is started Features and Dates cannot be edited without a proposal (from anyone) and an approval (by a product owner, uber product owner, or consensus of several product owners).

3. The change is versioned and can be rolled back.

4. The change can be displayed with edit markup that looks like track changes or suggestion mode in a word processor.

  • Guest
  • Apr 18 2015
  • Unlikely to implement
Release time frame
  • Jan 8, 2016

    Admin Response


    Within Aha!, there are 4 types of user roles and permissions (product owners, contributors, reviewers and viewers). We've gathered much feedback from the community in coming to this place for the user types.

    We are unlikely to make additional updates in the area of permissions, particularly in regard to specific additional controls that users have and do not have. These areas are workflows which we feel should be commissioned outside of Aha!, where the team member is aware of the areas in which they are "allowed" to revise vs. not.

    We hope you can understand.