Account settings
Sort by:
Trending
Status:
Showing 640
4
VOTE
Extend product tree to support different configurations of a product line
I manage a product line where each product has different configurations. Currently I get around it by making different releases, but it really doesn't solve the problem because the different configurations have different requirements. So, being ab...
1
Unlikely to implement
4
VOTE
4
VOTE
In workflows, add the ability to limit setting a certain status to certain users.
In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless.
If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets v...
2
Unlikely to implement
3
VOTE
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...
0
Already exists
3
VOTE
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...
0
Will not implement
1
VOTE
Add possibility to have title read only
In case of integration (e.g. DevOps integration) there could be some records which should not be modified in Aha (or at least some fields) but only in the integration. All fields can be set to read only via the custom layouts, but title can never ...
0
Future consideration
1
VOTE
List report of all users w/in my product line and the workspaces under it
We recently went through a reorg and have users that are either no longer with the company, have changed roles/responsibilities, etc. that will need their access/permissions changed which will result in a cost savings for the paid subscriptions. I...
0
Future consideration
3
VOTE
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...
1
Already exists
3
VOTE
Alternate hierarchy to manage work through different lens
We look at the same Initiatives through two lenses: (1) the product lens, which Aha! solves really well; and (2) the program lens, which Aha! does not solve for.
The idea is to have an Alternate Hierarchy in Aha!, such that the same initiative c...
0
Unlikely to implement
3
VOTE
© 2024 Aha! Labs Inc.•All rights reserved