Currently when creating a feature, I have to create the feature and then manually send the integration to ADO. I want to have a variable on the Create Record Layout screen to be able to choose this option when creating the feature. This way I can ...

As a PM of a new organization, I need the Product Line/Workspace Overview pages to show the full Description section so that our new Teams can easily find information between Work spaces. Suggested "quick" fix, is to allow the user (or admin) chan...

We use Benefit Maps to help plan out work and recieve Business approval. The content of the map is all on Aha such as Company goals, initiatives, and often features. The latter two typically come through the our Ideas portal. It would be beneficia...

Most users spend their time in features boards and therefore are unlikely to see broadcast messages which limits their usefulness. We recently had to notify users of a change and had to send an email to ensure they were aware of what was changing

In the new workspace overview tab, there are filters to show all, in progress, not started. It would be useful to also be able to filter out archived timeframes so not all goals and initiatives are showing so the context for "all" is set to the cu...

We're regular users of Feature Upvote where we can set a password for our Feedback board, and users must input it to access our boards. They can then post/comment by just inputting their email and username. This works well for us because we're lim...

Our UX team has created a set of approved personas for the entire company to use in all of their product lines. Our UX group would now like to have the ability to look at a specific persona and find out what are all the open initiatives, goals, ma...

When creating presentations, it can be hard to find the presentations that have been created. They are accessible via the dropdown menu under "Roadmaps" (which doesn't make sense) then "Overview" (which takes the user to a pretty unnecessary inter...

In the below screenshots, email address is a required field on the first screen, but not on the second. Email address shouldn't ever be required when creating a virtual user.

We had a very large number of Jira Integrations created before we had central administration of our Aha application. I need to apply a Jira template to these integrations so that the URL and password can be managed from a central person, but if I ...