Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 9039 of 9039

Allow automations for custom tables based on another custom table

Who would benefit? Aha! users who have expanded their capabilities through multiple custom tables. Today, when custom tables reference each other, you need to update them on both sides. This drives no-value-add manual work and is ripe for inaccura...
Guest 8 months ago in Roadmaps 1 Future consideration

Requirements capacity planning

We have users stories mapped to requirements in Aha!. When viewing the capacity planning at a requirement level it uses the feature level start and end date, we want to see the start and end date of the requirement (Story). Also related to this in...
Ruth Gardiner over 1 year ago in Capacity planning 0 Future consideration

Progress bar for roll-up releases

This functionality is available for every other record type, user expectation is that it you would also be able to track progress across all Releases within the Master Release. This is a request from our Senior Leadership team as well to track por...
Guest over 4 years ago in Releases 3 Future consideration

Include Requirements when using AI Draft Release notes from a release

Who would benefit? PMs What impact would it make? Save time from creating a list report How should it work? Using AI Draft Release notes directly from a release doesn't allow you to pull in requirements of features that are contained within that r...
Terence Osmeña about 1 year ago in Notes 0 Future consideration

Remove releases from features roadmap if all features/epics have been filtered out

Who would benefit? Product managers & their shared webpages What impact would it make? Allow us to not have to manually adjust releases based on goals/initiatives or other information that's not represented in that release How should it work? ...
Steven Schafer 8 months ago in Roadmaps 0 Future consideration

Support approval gates in Aha! Develop

Quality is critical for my product. I want to ensure that all features go through QA testing before being marked as "done". The approval workflows implemented by Aha! Roadmaps solve my need well. I want Aha! Develop to respect those workflows as w...
Jeff Tucker over 2 years ago in Workflow boards 1 Future consideration

When adding features from the prioritization board, choose where they're placed

What is the challenge? When adding features from the privatization board, they are automatically added at the top of the priority queue. However, we have had PMs in our organization that this is annoying and might not want them added at the very t...
Guest 4 months ago in Features 1 Future consideration

Allow filtering by organization on the ideas prioritization view

What is the challenge? Unable to easily create a prioritization view for a specific organization. What is the impact? I'd need to manually add ideas to the prioritization view based on a separate report to segment the ideas for a specific organiza...
Kristina Gass 4 months ago in Ideas 0 Future consideration

Ability to send Aha Defects to Rally as Rally (CA Agile) Defects

We need the ability to send defects to Rally. Currently, we are only able to send features/ user stories which cannot be converted to defects once they are in Rally.
Guest about 7 years ago in Rally 2 Future consideration

Ability to configure automated status logic

For almost all our workflows, a parent record's status is dictated or a reflection of it's child record's status - similar to how the progress of a parent record is an aggregate of it's child records and that functionality. I would like the abilit...
Michael F about 4 years ago in Application 3 Future consideration