All ideas

This new functionality is great. (6 Note Templates for Better Team Collaboration) Just missing a way to save a note created as a template to reuse it ! (or at least being able to customize the template)

Our engineers do their dev work at the Requirement level in Aha!. Capacity Reporting would only benefit us if we could track time/points associated with Requirements (not Features) to accurately do resource planning of our engineers.

When a user logs into Aha!, the first page they see is the page "How Aha! works". Our users are reporting that this is confusing, as they want to navigate to a page within the product itself (i.e. Feature Board or Releases Overview"). Users arrivi...

As comments are made on a feature, sometimes there are questions that come up that are unrelated to the other comments that have been entered. It would be much easier if I could just reply to the comment and the thread is kept/read in that fashion...

Add an "Import from Rally" utility for importing existing features, user stories, etc. and supporting metadata into Aha! as Features and Requirements and creating corresponding links between the data objects in support of the bi-directional integr...

I would like to be able to bulk move or copy personas from product lines/products to other product lines/products. A few scenarios where this is helpful:- I need the same personas across multiple products- I might be on the wrong product in the na...

It would be nice to default the progress calculation for Goals, Initiatives and Epics at a Workspace level so that product managers don't have to do it at a record level for every goal, initiative and epic. It is tedious and leads to data error as...

We build features across several releases or we break them into smaller marketable components of the larger feature. We really need a way to tag a feature to multiple release vehicles.

What is the challenge? The API documentation lacks some accuracy and is incomplete What is the impact? Even if Aha!`s support is always helping out, when i have strange API questions, a complete openapi / swagger document would be helpful Describe...

So that users don't vote for everything, limit the total number of votes they have (which could perhaps be a number that is editable by the Aha! admin). Allowing more than one vote on an item for weighting would be helpful as well.