Skip to Main Content
Status Will not implement
Categories Application
Created by Guest
Created on Apr 21, 2017

Allow the people doing the work (designers and developers) to update feature status.


My team and I just started using AHA! integrated with Pivotal and I couldn’t agree with you more on this limitation. The people working on the features need to be able to update the status and it’s definitely not worth $1200 a year. It especially makes no sense considering that the integration with Pivotal Tracker grants the developers this permission, why can it not be granted within the app itself for designers and others who work on features with the developers.

    Apr 30, 2017

    Thank you for the idea. Each of the different roles within Aha! have specific permissions and capabilities. As you know, contributors and product owners are the users who have the ability to edit features status. Reviewers are able collaborate on features through comments and To-dos.

    We don't plan to expand the capabilities of that role as the current permissions framework was based on substantial research and customer feedback. We hope you can understand.

  • Attach files
  • Kelly Kampen
    Jul 21, 2017

    I too would love this feature. 

    Having an Engineering role would pretty much eliminate the need for 3rd party tracking system. Everything is already in Aha. But because of the price per use we are forced to use PT or Jira for Engineers. 

    I think Aha may be missing out on a profit center.  The Engineering role could simply be a less expensive role that allows for status change & comments.