Skip to Main Content
ADD A NEW IDEA

Account settings

Showing 609

Provide product managers with secondary way to manage reviewer and viewer access by product

Today, administrators have to manage all aspects of access control for users to access product records for the business units in order to maintain the unit's structure/implementation of Aha! This is not scalable for the 5 admins in our unit. Produ...
Cindi Baris over 6 years ago in Account settings 0 Already exists

Improvements to Master-detail relationship custom field

Custom tables have provided us great benefits. However, entering and editing data in these tables can be painful. Updates to the master-detail relationship field can make this better. 1: Allow the user to collapse the field and hide the records, ...
Ken Hinton over 6 years ago in Account settings 0 Future consideration

Adding values for custom fields at product level, not just account level

We have a number of Product Managers. It will be good if they are able to add values to certain custom fields so that an integration between JIRA and Aha doesn't break. For example, components. If an engineer adds a component in JIRA, it will be g...
Project Parker over 6 years ago in Account settings 0 Future consideration

Restrict Viewers to specific Aha section views

Currently we use web reports linked from Confluence to restrict the visibility of registered viewers on certain product roadmaps. However, the report view isn't really as good as the default Aha view which is much easier to navigate. But giving Vi...
Guest over 6 years ago in Account settings 0 Unlikely to implement

Add more granular admin permission for configuring product lines

In order to maintain consistency across the product hierarchy, it is important to keep control over the naming and organization of product lines and products. In many cases some users should have administrator access to make customizations for the...
Austin Merritt over 6 years ago in Account settings 5 Future consideration

Clarify the use of the term "allocate seat", as it's not clear a seat can be unpaid. :-)

Hi, I had a human-error issue where I had two users in my user list that I couldn't figure out how to give them view access. I clicked the viewer access button, but nothing would happen. It turns out it was because I wasn't clicking "allocate seat...
Guest over 6 years ago in Account settings 0 Future consideration

Custom Fields: Automatically linking the values of one field to be published in the linked field

I have created a custom field in features which links to persona’s. I am able to add the relevant persona’s for the product. The drop down shows the correct products to choose from. Similarly, I have created a custom field in persona’s linked to f...
Project Parker over 6 years ago in Account settings 4 Future consideration

Don't allow duplicate accounts with the same email address

The system currently allows multiple accounts with the same email address. We are using SSO, so I'm not sure if this is unique to SSO integrations. Multiple accounts with the same email address should not be allowed.
Avigail Ehrenhaus almost 7 years ago in Account settings 0 Unlikely to implement

Location To Manage Product Roles & Hiearchy

Would be nice if there was a editable template place to capture roles & responsibilities related to the product. Somewhere in the overview or strategy section would be ideal. For example, IT is responsible for these actions related to this pro...
Connor Shay almost 7 years ago in Account settings 0 Already exists

Custom field: maintaining standard pick list across Aha! functions

Problem: When defining a custom field with a pick list that you want to be exactly the same across all Aha! functions (ides, feature, releases, product and so on), you have to create, duplicate and maintain the custom field list over and over. I a...
Guest almost 7 years ago in Account settings 1 Already exists