Account settings
Sort by:
Trending
Status:
Likely to implement
Showing 645
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
3
VOTE
1
VOTE
Calculate progress based on completed status of child records
I would like the option for Aha to automatically calculate the progress of an Initiative based on the number of Epics or Features that are Released verse still open. The same would apply to Epics and the child features.
2
Future consideration
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
1
VOTE
Automation - add specific data range when choosing time frame
When creating an automation for a goal, it would be nice if I could add a specific date after choosing a time frame. So if I create a new goal, and choose a time frame of FY23 Q3, I'd like to set a custom field Goal Start Date as Oct 1 and a custo...
0
Future consideration
3
VOTE
Allow non-admin product owners to configure tags
Our teams are using tags heavily to add planning metadata to features. Over time, duplicate and mistyped tags are introduced which can cause confusion. At the moment, only those with admin access (one person within our organization) can clean up a...
0
Future consideration
3
VOTE
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
1
VOTE
Product line prefix for all ideas of all product workspaces under it
Let's consider an example to understand it better: I have a product line called: "Line1" having a prefix as "L1" I have 2 product workspaces under the same product line, i.e., Product A with prefix as "PA" Product B with prefix as "PB" I have an i...
0
Future consideration
4
VOTE
permission-restricted release or feature status
We should be able to configure specific release statuses so that they're restricted, editable only by certain users or user groups.
We have a Program Management group which maintains an authoritative list of releases the product organization has c...
1
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved