Skip to Main Content
ADD A NEW IDEA

All ideas

Showing 8992

Aha online support should show data configuration to produce report

What is the challenge? When trying to reproduce the reports shown in Aha's online support documentation I sometimes struggle with how to configure the data fields. This is a particular challenge with pivot tables, but happens with all reports. How...
Julia Pence 8 months ago in Training 0 Future consideration

Prevent users from inadvertently moving Features' workspace

Who would benefit? Our company's 750+ workspaces What impact would it make? If not resolved, this can cause damage, manual work to re-create Aha! <> Jira integrations, and work becoming out of sync between the two. How should it work? We oft...
Donald Hebert 10 months ago in Epic 0 Future consideration

Epic Roadmaps by Roll-up release

Who would benefit? Any customer who has a quarterly marketing release that impacts multiple products What impact would it make? this would allow us to have a single consolidated view across our products with a single reporting view so the entire b...
Rob S 10 months ago in Roadmaps 0 Future consideration

Allow ideas portal users to set time zone

Currently ideas portal times are in GMT - would be nice to have these be localized so emails that come through from ideas & updates to ideas display event times in the local times for the user.
Danny Archer over 9 years ago in Ideas portal 10 Unlikely to implement

Use field comparisons to trigger automation rules

For example, when the Detailed estimate field changes to a value that is higher than the Initial estimate field, assign a to-do for someone to review.
Guest 3 months ago in Capacity planning 0 Future consideration

On a public ideas portal: require a user account before posting, voting and commenting.

Our public ideas portal is today open for all people to post. I’ve been recommended by our internal security expert to require people to create an account before allowing them to post, vote and comment. When I set the ideas portal to be privat...
Guest over 6 years ago in User management 2 Unlikely to implement

Keep features in sync when they cross areas in Azure DevOps

This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
Deb Gay over 5 years ago in Azure DevOps Services and Server 0 Future consideration

The ability to configure which fields are included in the feature to pdf export

Who would benefit? Customers who are required to share feature documentation with enterprise or large government clients What impact would it make? Ease of hiding internal information or displaying only customer relevant information How should it ...
Megan Sullivan about 1 year ago in Account settings 0 Future consideration

"related" features/activities have details

In my Aha boards, I have epics/projects that have "related" features/activities. One thing I have found is that it can be difficult to see details for the lower level features/activities without going into the ticket itself. Under activities in th...
Guest almost 3 years ago in Epic 3 Future consideration

Update Feature ID when moved to another product

When you create or copy a feature, its ID is automatically created based on the product code. The ID is a combination of the product code and an auto number (and that is perfectly fine). But when you change the release reference to a release of an...
Guest over 9 years ago in Features 10 Future consideration