Account settings
Sort by:
Recent
Filter by:
Status
Showing 610 of 8836
1
VOTE
Products should be easily transferable to other teams
This would be similar to Heroku's treatment of "apps." You can work and collaborate with others on an app -- say as a consultant -- then when it's time to deliver the product to a client or otherwise hand it off, you can easily transfer everything...
0
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
4
VOTE
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, ...
0
Future consideration
9
VOTE
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...
0
Future consideration
5
VOTE
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...
0
Unlikely to implement
20
VOTE
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...
5
Future consideration
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
Future consideration
9
VOTE
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...
4
Future consideration
1
VOTE
1
VOTE
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...
0
Already exists