Account settings
Sort by:
Status:
Unlikely to implement
Showing 77
49
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
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
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
20
VOTE
23
VOTE
Custom Fields Permissions
When creating custom fields for ideas or features we need ability to select which user group has rights to edit it. We created a field named owners, with multiple select options from which a product owner can select several names of people that ow...
6
Unlikely to implement
1
VOTE
Record level permission restrictions
What is the challenge? Some features or initiatives are sensitive, so we would like to be able to set record level permission restrictions What is the impact? Anyone who might come across work that isn't being widely publicised in the org Describe...
0
Unlikely to implement
2
VOTE
Ability to set a specific date in automation rules
Who would benefit? everyone What impact would it make? high priority for our key product team In the area in setting an Automation Rule you can set dates for things like 1 day or 1 week from today. Our team wants to enter a specific date to be set.
2
Unlikely to implement
16
VOTE
Granular Permissions for Components
It would be beneficial to Product Line Managers and Product Managers if individual custom components could be hidden from some individuals. This is useful when adding sensitive financial data or other secure information. If the Product is shared f...
7
Unlikely to implement