Account settings
Sort by:
Trending
Status:
Unlikely to implement
Showing 102
1
VOTE
Integration of company's proprietary AI engine with Aha!
What is the challenge? User can only use default AI engine. Due to company's cybersecurity polices, we cannot enable AI related features. What is the impact? By integrating company own AI engine, the system will benefit from enhanced data security...
0
Unlikely to implement
59
VOTE
44
VOTE
As an Admin, I would like the ability to easily see and filter which custom fields are being used by which products and product lines
As a very large account user, we have A LOT of custom fields and we are finding it very hard to manage. Our biggest pain point is that some of our Admins will update a custom field, that they believe is only being used by them in their product, an...
6
Unlikely to implement
50
VOTE
Tag Separation by Product
I have a number of different products all of which require their own tags. Each product is sufficiently different that a tag in product one would not make sense in product two. Currently I can see all of the tags for product two in product one and...
18
Unlikely to implement
33
VOTE
39
VOTE
Allow setting of default values in scorecards
When configuring scorecards, it would be useful to be able to set a default value for a metric within the given range. For example if a metric range runs from -10 to 10 (some metric may have a positive or negative impact on our product), it appear...
3
Unlikely to implement
20
VOTE
Allow Requirement Dates to drive that roll up to a Feature to drive that Feature's start & due date.
We integrate with Jira Engineering work at the Requirement level and must see dates associated with Jira Stories as Requirements in Aha! Since addressing the Requirements / Jira User Stories make our Features a reality, we request that a setting b...
4
Unlikely to implement
25
VOTE
Self Registration Capability for User Acess
We are a large organization with many users. We would like to share Aha! with interested individuals and that number could be hundreds or thousands. In order to alleviate that, the recommendation is to allow a self registration process that would ...
8
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
Unlikely to implement
22
VOTE
Allow scorecards to be inherited from the product line
We have a lot of sub-products in our company, but we'd like to use the same general scorecard, linked to our general product goals, for all of them. It seems that currently scorecards need to be configured for each and every product, which isn't e...
1
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved