Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 9110

Ability to have a common structure for competitor cards under different products so the layout doesn't change when moving a competitor

When moving a competitor from under one product to another the structure of the competitor page changes and certain fields hide in the new space where it is being moved. This then requires manually editing and moving around fields in the card, whi...
Guest about 4 years ago in Strategy 0 Future consideration

Create a calendar report sorted by schedule start date

Would love to create a calendar report sorted by schedule start date? Or even better one that keeps the schedule on the calendar until the end date?
Sherise D about 4 years ago in Calendar 0 Future consideration

Allow data import into Aha! from other requirement tools to preserve parent-child relationships to other requirements or feature ideas

Many tools when exporting either requirement or feature idea data will export the upstream and downstream tag IDs to their own columns. If Aha! can leverage that data and preserve the relationship / dependency detail when importing requirements it...
Guest over 8 years ago in Features 0 Unlikely to implement

Support the context of a sub-goal at the Company, Product Line or Product Level

Normally when setting a corporate strategy, the Corporate goals have sub-goals that are a little more down to earth and digestible. These sub-goals give all areas of the business, IT, product development anchors to have a common understanding and ...
Guest over 8 years ago in Strategy 0 Already exists

Sub-classify requirements within a feature

When creating requirements I like to divide them into the functional areas of the feature.
Ian Hassard over 8 years ago in Features 0 Unlikely to implement

Add clickable ID for epics on the Gantt > Epics view

On the Gantt view, the features have the ID on the left which is clickable to open the feature record. On the Epic view of the Gantt, the epic ID is not displayed on the left. It would be helpful to see the ID and click it to open the detail view ...
Craig Pflumm over 4 years ago in  0 Future consideration

Have reports force the user to change their workspace

We have leveraged the ability to change the taxonomy per workspace to be very relevant to the context of that workspace. When I create a report that is intended to show details for a specific workspace, it makes the most sense when the user views ...
Alex Horan over 4 years ago in Reports 0 Future consideration

Rally Integration: Allow Rally "Programs" integration to Aha's "Goals"

Our Rally implementation uses a Lean Agile decomposition model - Programs, Business Increments (BIs), Minimum Business Increments (MBIs), and Features. BIs map nicely to Aha Initiatives, MBIs map to Epics, and Features map to Features. We use Prog...
Stephen Wingert over 4 years ago in Rally 0 Future consideration

Capture and add attributes (Labels) to users names

We want to be able to measure over time how engaged specific user groups are when using Aha! and then use that to information to show utilisation. So for example I want to show a report that shows week by week how many Programme Managers who have ...
Andrew Brooks over 4 years ago in User management 0 Future consideration

Be able to link feature to initiatives only starting from a specific status

When we are working on the roadmap we draft some initiatives for the next releases. Before we have the budget confirmation initiatives are not confirmed, so it would be perfect if they could not be seen and linked to the feature. In the same way, ...
Guest over 4 years ago in Features 0 Future consideration