Allow feature and master feature content to be set to "read-only" based on status

Aha should be able to allow us to set "Allow editing" and "Read-only" for feature and master feature content so that at a particular stage in development we can stop adding content to a feature/master feature. We would like to do this manually and based on status. 
For example we could set 'Committed', 'Complete' and 'Released' to Read Only which would lock the description field and other parts that we don't want edited. This would be an option to set for each status type. 

Once a feature/master feature has been changed to read-only it could be manually switched back to allow editing by the owner.

  • Perri-Anne Sims
  • Nov 21 2018
  • Unlikely to implement
Release time frame
  • Dec 8, 2018

    Admin Response

    Thank you for your idea. We would recommend handling this using internal processes. If changes are made to a feature you can use feature history to identify the changes and make updates as necessary.

    Given the ability to find this information in history and other priorities, we are unlikely to implement this idea at this time. We hope you can understand.

  • Attach files
  • Julia Doyle commented
    December 10, 2018 14:55

    I have several concerns in reply to admin response:

    1. Only paid Aha users get to see history. This means that the majority of our users have no way to see if a feature has been changed after it has been committed. 
    2. There is no indication/flag that a feature has been changed. Your suggestion implies that our process should be that every time someone looks at a feature, they should check the history to see if it has been changed recently. This is a huge hassle. 
    3. We have almost 2,700 features in Aha and 550 users and we are getting more of each all of the time. Certainly internal processes are useful and important, but human error is inevitable when there are so many people and pieces of information at play. 

    Please give us a better way to manage information and keep it from changing once it is at a certain state. The suggestion of keeping track of the history of every feature and master feature is not feasible for us. This is a huge issue and makes people not trust the information in the feature because there is no way to ensure it hasn't been changed.