Account settings

Who would benefit? Everyone What impact would it make? Ability to see all related workspaces enables speed. How should it work? I should be able to find/see all related workspaces under a product when I search for the product. Under the connected ...

Hello, I have created custom fields with type Predefined choice list.I want to allocate a color to each item of the list just the same way you can do it for tags. Is it possible?If yes, would like to understand how to do this?If no, is it plan in ...

Currently, there is no way to download all of our Aha! data in bulk. we an only download all the data for each record type is via the List report under Roadmaps. We can create a list of all records of a specific type (including personas and compet...

We like the idea of read only fields to capture initial data but prevent further edits. Currently if a custom field is marked as read only data can't be inputted which seems to defeat the object of creating a field. It is fine on a bulk import, bu...

I think an additional column is needed on the export to indicate if the user has been disabled or not. I’m seeing my user export list grow, but the CSV doesn’t readily show you if a user has been deactivated (their original permissions stay reside...

We have some custom fields that we want only to appear at the Product Line level, specifically for Master Releases and PL Initiatives. We'd like a way for them not to appear in Product Initiatives or Releases. As it stands now we just need to inst...

In addition to being able to attach files, it would be helpful to be able to attach links. Many times, relevant information is a web page instead of a file. Today, we can only embed links in text fields, such as Description and Comments. I put thi...

When we create custom field in AHA we want the ability to create context for each product so that we can see only values which are relevant to a specific product. For example Team A, Team B and Team C are related to Product 1, we do not want to se...

We have a fiscal year which starts in March, but it's leading rather than lagging. Therefore, FY17 starts March 1, 2016. However, reports reflect March 1, 2016 as FY16

Currently if you hit enter as the tag suggestions are displayed, it will enter a new unfinished word. This leads to messiness and tag cleanup.