What is the challenge? Currently we have cases where RnD would open a theme (we categorize it) , and that is for mostly themes with technical nature. as such PM will not initiate them, but we still want the PM to be aware of them in planning and p...

Who would benefit? Teams using roll-up releases extensively. What impact would it make? Easily keeping everyone informed of launch details. How should it work? When the user updates the name of the roll-up release, it should be updated in any mapp...

Who would benefit? Users who receive product requests via GitHub or similar What impact would it make? It would allow to add both Product- and Engineering-related items from importer extensions How should it work? When dragging an item from the im...

Who would benefit? All whiteboard users: designers, facilitators, cross-functional teams, workshop participants, Guest users... What impact would it make? Improve navigation between different parts of a whiteboard, for example as part of pre-struc...

Who would benefit? Aha users What impact would it make? It will be possible to automate the process of filling up the needed field on initiative level based on automatic change of value of delivery risks flag field on feature (epic) level How shou...

Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.

What is the challenge? Brand guidelines for presentations at my company is Aptos, which is not available in Aha Presentations What is the impact? Using available fonts, Aha presentations does not fit within in our brand guidelines, and appears "di...

The options to calculate the completion of an epic in Aha is only based on user stories, but there are other items in JIRA that determine how complete an epic is. It would be helpful to have the progress bar completion automatically reflect whatev...

Delivery risks are calculated against the due date of epics and features. Requirements don't have due dates, so this risk check is not present. I see two use cases here: If I have custom date field on a requirement, it would be great to be able to...

The list of archived timeframes can get pretty long and since not active, really doesn't need to appear so hiding them would be better