Account settings
Sort by:
Trending
Status:
Will not implement
Showing 655
3
VOTE
Ability to create custom fields with context
When we create custom field in AHA we want the ability to create context for each product so that we can see only values which are relevant to a specific product. For example Team A, Team B and Team C are related to Product 1, we do not want to se...
0
Already exists
2
VOTE
Share the list of value among different custom fields
We have some custom fields that are replicated for Epic, Feature and Requirement (e.g. Area Path for the integration with Azure DevOps). They have a long list of values we need to replicate and maintain three times instead of one. It would be perf...
0
Future consideration
4
VOTE
Ability to suppress Product Line level custom fields from products
We have some custom fields that we want only to appear at the Product Line level, specifically for Master Releases and PL Initiatives. We'd like a way for them not to appear in Product Initiatives or Releases. As it stands now we just need to inst...
0
Already exists
2
VOTE
Global setting to turn off attachments
Our company works with sensitive data and we would like to globally shut off the ability to add attachments. In order to meet security requirements, we have quarterly auditing of attachments in addition to coaching users to insert an SSO protected...
0
Future consideration
4
VOTE
4
VOTE
Search on users that are using SSO or password
Recently integrated SSO with Aha! (thank you Chris!). we're now going to transition users from traditional password to SSO. I think there are some small changes you can make to user administration to make this easier. Should be able to search on t...
0
Will not implement
2
VOTE
Assign Custom fields to a parent workspace
We have over 250+ custom fields being utilized by various workspaces. Because we cannot assign a custom field to a particular workspace all 250+ fields are visible in every filter in every workspace. If we could have the ability to define which wo...
4
Future consideration
2
VOTE
Inconsistent / Broken Terminology
Within Marketing, Business and Project Lines, the customize terminology setting is broken and creates an inconsistent user experience that confuses users. Within the 'Customize Terminology' setting (Settings > Product Line > Terminology), if...
0
Future consideration
1
VOTE
Ability to archive and/or export a customization
Once an organization has decided on specific configuration settings (deeming it "golden" as an example) they need to document those configuration values in case it is accidentally (or maliciously) changed. An ability to archive and/or export the c...
0
Future consideration
2
VOTE
Line and Workspace management - stop collapsing the Line / Workspace hierarchy each time you complete a Line
If we leverage UX / UI, when a user-persona leaves a data structure in a window, they should expect it to remain the way they left it when they return, or complete a task Currently, when I go to the Customized Workspaces --> then expand some or...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved