Skip to Main Content
ADD A NEW IDEA

Account settings

Showing 506

New user role 'Approver' to change status without permission to change feature details

We would like the option to assign permissions to our Engineering leads, so that they have the ability to review features and approve the feature description by changing the status from “Ready to develop” to “In development”. They should not be pr...
Guest over 6 years ago in Account settings 0 Unlikely to implement

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

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

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 over 6 years ago in Account settings 0 Unlikely to implement

Broadcasts - Need functionality to allow a Broadcast to expire after x views

Right now #Broadcasts is a great tool, but the implementation is very wieldy for the Aha admin as they (currently) only have the ability to turn them on or off. I would like the ability to have them automatically expire for the individual user aft...
Joe Carpenter over 6 years ago in Account settings 0 Future consideration

Provide sorting capability for custom fields (tags and Choice lists)

We have a large client list and when a feature has been requested by a client, we associate the client to the feature. With a long list of clients, being able to sort the Alphabetically (ascending/descending) would make choosing the Clients far ea...
Jerrold Emery over 6 years ago in Account settings 1 Already exists

Home page customization doesn't match terminology

Bug report: When editing the default home page selection for a user, we are not seeing our customized terminology in place, which is causing some confusion with our end users. Thank you
Guest over 6 years ago in Account settings 0 Unlikely to implement