All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6177
8
VOTE
External facing product names
As a product manager I'd like to be able to define both an internal and an external product name.
The case might be that our team and internal employees refer to a product as "X". Externally, our customers know the product as "Y" in marketing and...
1
Future consideration
3
VOTE
3
VOTE
Allow mapping Release as a field on Requirements in Azure DevOps integration
Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
0
Future consideration
2
VOTE
Automation to Create Duplicate Record in Another Workspace
We have multiple teams who work in multiple workspaces where one body of work being created may trigger another body of work to be created. Currently we need to copy the record and then move the copy to the other workspace. Ideally we would be abl...
0
Future consideration
1
VOTE
Improve handling of progress calculation for Develop team work
Features should have a single continuous flow that progresses from Design through Dev and QA, where statuses pick up where the last team left off. I.e., the final status of the record for the Dev team would be “Ready for QA” and map back to a simi...
0
Future consideration
1
VOTE
Enable Aha! community bulletin board for Aha! community
It will be helpful to reach out to (focused reach) all Aha! clients and inquire who solved the problems I am encountering. For example, instead of searching ideas and hoping Aha! solves a problem / blocker - others in the Aha! community may have a...
0
Future consideration
2
VOTE
Visualization of Epics Roadmap Timeline
When using the Aha Epics Roadmap option, the releases do not visually align with the chronological timeline. This creates some dissonance when understanding when things occur. When there is space to do so on the roadmap, it would be helpful to hav...
0
Future consideration
6
VOTE
Add scorecard support on custom field update API
Whenever you modify a custom, scorecard-type field to point it to a different scorecard, all previously entered values in this field across Aha are lost. This makes sense, as the structure of the new scorecard may be completely different from the ...
0
Future consideration
5
VOTE
Pretty / Attractive/ Professional Looking Roadmaps
Content wise, the roadmaps that we can make in aha meets our needs pretty well. We can organize the work by goals, and themes, and by quarters. We can present status and any additional details we want to include. But, what we hear from our executi...
7
Future consideration
5
VOTE
Add Estimate when configuring Feature Cards at the Product Line level
We have 20+ products, when viewing feature cards across multiple products I would like the Estimate to be visible for each - however in order to do this I now have to manually go into each product and customize the feature card since this is not a...
0
Future consideration