I like and use Aha! scorecard to prioritize features in my product and release backlogs. However, quite often I need to explain other stakeholders (and record for myself) why I'd go with one or another score. It would be great to have one common o...

In order to test potential improvements to our workspace custom layouts, we have to create a separate test workspace and then clone and update the custom layouts. If we want to do any changes to the custom fields (such as new values), we also have...

We often have several initiatives (we refer to them as roadmap themes) in our Aha workspaces. Unfortunately, the labels for those initiatives often overlap on the 2x2 because of how things are scored. I have attached a screenshot of an example.

We have features in Aha mapped to epics in JIRA, and then requirements mapped to user stories. I'd like the user stories in JIRA that I send over to automatically include links to their sister stories under the same epic, so that developers can ea...

On the new integration report, please add columns to show which settings do not use the template. This is especially useful for the credentials so that we know which ones we need to update individually.

A product may have multiple initiatives and then you realize that they are very similar, but different, and you want to create an intra-product hierarchy. Same product -- multiple, related initiatives.

It would be great if you could make To Dos more functional. attach an existing to do to a new idea create an idea from a To Do change a To Do into an idea

As a User I want to ability to remove the Aha branding and login link as it looks odd when a Saved View is embedded in another website.

Who would benefit? What impact would it make? How should it work?

Similarly to how custom fields can have optional descriptions. The same would be good for tags, so that additional information (essentially explaining the tag in more detail) can be conveyed to other users. This would reduce the need to either cre...