All ideas

Currently, we can save a Gantt view with releases that are expanded or collapsed and that's how it will appear when added to a presentation. It would be helpful to have the option to allow the viewer of the presentation to expand/collapse the rele...

Who would benefit? Groups of approvers What impact would it make? It would keep the to-dos focused on what has not been completed How should it work? If >1 user is assigned an approval because of an automation rule, and any user completes the r...

Who would benefit? Product Managers What impact would it make? Aggregates poll responses into a single representative value Provides a simple way to share poll results internally Allows setting targets/goals when gathering feedback on new launches...

Analytics and Reporting are part of Develop Advanced, and users in those accounts are able to save list reports. However, some teams use list reports as part of their backlog and sprint management process. They don't need sophisticated analytics, ...

Who would benefit? Eveyyone that uses To-Do's heavily. What impact would it make? Easily be able to see just what is left to be completed. How should it work? Similar to the Status filter on the related tab views. Have the ability to filter by the...

Who would benefit? Integration users What impact would it make? How should it work? When you delete a feature which is linked to a dev system you get a warning (attached). When you delete an epic, you do not get a consitent warning. This suggestio...

Our development team manages PBIs within sprints. Currently you can map a custom sprint field for features in Aha! to DevOps, but not requirements. Ideally, we would be able to sync sprints for requirements/PBIs, as that would be more useful than ...

Today the Aha JIRA integration will leverage the user account setup in the integration settings as the actor for all integration sends between the systems. This creates a lot of confusion for who actually made changes in one system or the other. F...

I can currently add comments on text in the description field of records such as features, epics, goals and initiatives. It would be helpful to have this available for ideas as well.

Who would benefit? People who support the implementation of Aha! across an enterprise, and anyone trying to find multiple presentations What impact would it make? It would save time, clicks and make it much easier to manage the proliferation of re...