Skip to Main Content
ADD A NEW IDEA

Application

Showing 78

Allow features to span across releases for better data model alignment between Aha and JIRA

Please allow features to span across releases for better data model alignment between Aha and JIRA. Both Aha and JIRA have 3 levels in data model. Aha focusing on Why-What has Goals-Initiative-Features and JIRA focusing on What-How has Epic-Story-...
Guest about 7 years ago in Features 1 Will not implement

Mobile application emulators for testing

If it's possible, could the Product Specialist team have access to mobile emulators for the android and iOS applications? As a member of the Product Specialist team, when running through the zone/tariff pre and post go live processes, this is alwa...
Guest about 7 years ago in User management 2 Will not implement

Allow the people doing the work (designers and developers) to update feature status.

THIS! https://medium.com/@mkhoury/aha-a-few-quirks-in-my-favorite-product-management-software-8eb515fd9e78 My team and I just started using AHA! integrated with Pivotal and I couldn’t agree with you more on this limitation. The people working on ...
Guest about 7 years ago in Application 1 Will not implement

Filter related views lists as I type

It'd be nice to filter as I type. When there's a lot of saved views and I'm looking for something, I'm not always exactly sure the name. This would help the discover process.
John Bohn about 7 years ago in Reports 0 Will not implement

ability to search for tasks

Client or accountant can do a quick search to find the status on a task based on name or date
Guest over 7 years ago in Features 1 Will not implement

Top-level navigation order for Ideas

The location of Ideas in the top-level navigation seems out of place and I'm always a little thrown off by it. You've got Ideas between Releases and Features. To me, it makes more sense to put Ideas after Features. This would create a better hiera...
Tom Beck over 7 years ago in Application 3 Will not implement

In UI move Releases to be after Features

Since product development moves chronologically from Ideas to Features to Releases, move Releases to be after Features in the UI so the order is logical.
Guest over 7 years ago in Releases 1 Will not implement

Toggle Detail and Detail Drawer

After expanding the view of an item from the detail drawer to the full view, there should be a corresponding CTA (call to action) to collapse the detail view back down to the drawer view. I understand that I can click the back button to achieve th...
Tom Beck over 7 years ago in Ideas 0 Will not implement

Don't Group By Filters when the field isn't in the Report

When you add filters to a report like "Goals" and a feature is associated with more than 1 goal it duplicates the lines in the report. However, when the field that you are filtering on is NOT in the data set it shouldn't be grouping by this field ...
Guest almost 8 years ago in Reports 1 Will not implement

Pop up messages.Priority messages on both GoTrex and Webagent

It would be good to be able to place a 'Post it note' or priority message on both systems when a client has made an important request (eg, please do not discuss my claim/sensitive information with my employer/broker/family) It would be really usef...
Guest almost 8 years ago in Voting 0 Will not implement