Features

I am using the new Template capability to provide guidance for populating Initiatives / Capabilities (Features) via a standard format. Unfortunately, to use this feature I am required to include the Description field in the Create Layout. This res...

Features can have relationships with other features recorded and this is really helpful for building out the overall feature architecture when they're "visualized". It would be great to have functionality to display an overall features visualizati...

To create a feature I must link it to an Epic before I can save it, but then I can go back and unlink the Epic. If I can go back and unlink the Epic, then why not allow the user to create a feature without linking it to a specific Epic from the be...

As we plan our releases, we order features in those releases by their Aha! score. The "Rerank features by" option makes it simple enough to ensure records are in the correct order during planning. As a release plan evolves though, it becomes chall...

Picture this. You're paying Aha $1800 per year for Enterprise+ because that's the tier you need. 100 people work at your company, and they have been using Zoho Projects @ $60 per year per person. You are not not not going to convince this company ...

Currently I can map features statuses to colors. But if I have more that 10 features in a release is hard to tell how many are in each state. It would be nice to have a summary that shows number of features that are currently in a ToDo, In Progres...

Make the field recognize numbers, but allow the customization of a number range. For example, 1-10. I tried to accomplish this with a predefined list, but it doesn't recognize the number as a value and therefor doesn't sort correctly.

You can now promote an Idea to a Feature. But Ideas and Features often have many-to-one relationships. Right now you can relate a Feature to Goals and Initiatives but not to an Idea. If Aha! is to be used for LSU/Agile/SCRUM management, you must b...

Requirements can be imported as part of the feature import from CSV routine. The requirement comment field is not included in the possible fields. Aha! users need to be able to keep track of the comments that are being imported and so at the momen...

For the Project views, it would be useful to be able to input a duration for an Activity and for a Requirement that will the automatically calculate the due date. This also makes it easier when dependency dates move. Perhaps this functionality can...