PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
What is the challenge? The auto-resizing functionality used by Aha! dashboards makes report panels, text boxes, and images appear at different sizes on different people's computers. What is the impact? This provides an uneven visual experience. Da...
Guest
12 months ago
in Reports
0
Future consideration
Add message to linked record drill-in on custom roadmap
What is the challenge? Currently the drill-in on a custom roadmap shows the related records for the primary record, not necessarily for the record being viewed in the bars What is the impact? This is mis-leading as the drill-in appears next to all...
Peter Whisenant
12 months ago
in Roadmaps
0
Future consideration
What is the challenge? In large organizations that do not have teams well coordinated, there are instances where multiple teams are working in silos creating similar features or components. It would be awesome if Aha! could help to surface similar...
Madeleine Black
12 months ago
in Features
0
Future consideration
Allow Drill-in for Feature columns on Prioritization view
Who would benefit? Users sharing Prioritization views via shared webpage What impact would it make? Increase ease of use for drill-in functionality by enabling the function on the default columns How should it work? The default Feature Name column...
Stephanie Lechner
almost 2 years ago
in Features
0
Future consideration
Allow Aha! user name to populate DevOps board user
When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in Dev...
Remove Requirements from custom Feature Card layout
We would like to remove "requirement" from our custom feature layout as this adds "too many layers" to the work. We want to utilize "to do" only within our workspace.
Carolee Snarr
almost 5 years ago
in Features
2
Future consideration
Tags should propagate bidirectionally into Pivotal Tracker
Much like status, it would be nice if tags on features would propagate instantly to stories in PT bidirectionally. We have historically used PT labels to organize aspects of our sprint. It would be nice to setup initial tags in Aha and have those ...
Jason Novek
about 10 years ago
in Pivotal Tracker
2
Will not implement
Stay in a whiteboard when moving a record in the side drawer
When working with Aha! goals and initiatives in a whiteboard, if a user moves the record to a new workspace from the side-drawer, the user is navigated to a full-screen page of the record. This takes the user out of the whiteboard experience - it ...
Steve Dagless
12 months ago
in
0
Future consideration
Allow External Users to Drill Down and Comment on Whiteboard Objects
What is the challenge? We would like to use Aha! as a tool to engage with our users at a Conference. We like the Ideas portal, but even better would be an interactive roadmap. The roadmap shared as a web page is not comment enabled. We imported a ...
Andrew G
12 months ago
in Whiteboards
0
Future consideration
On custom roadmaps show requirements in a feature's record links
When building a custom roadmap, you can click the icon above the roadmap bar to see related record links but Requirements are not shown when viewing a feature’s linked records. Other related records are shown but the Requirements are not.
Justin Waldorf
12 months ago
in Reports / Roadmaps
0
Future consideration