All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5653
3
VOTE
Ability to edit first and last name of a user
What is the challenge? Ask? . If a transgendered employee who hasn’t had a legal name change yet were faced with this challenge, it would be an afront to the values that our company holds dear. Certainly something we have to address at the point o...
0
Future consideration
3
VOTE
Use the release "Date range" in automations
What is the challenge? Trying to configure a release automation to set the "Feature start date" and "Feature due date" to be the same as the "Release start date" and "Release due date" What is the impact? Using custom/alternate fields where this i...
0
Future consideration
4
VOTE
8
VOTE
Hide parking lot from certain user roles
Who would benefit? everyone What impact would it make? limits information leakage and information misuse to parts of the organization who don't need to see in progress epic development before it's put in an official release How should it work? wit...
0
Future consideration
20
VOTE
Capacity planning - sync functionality available for initial and detailed estimates
Taking an initiative level as an example, for initial estimates you can view the capacity planning based on allocation across teams, you can further allocate to individual/s within that team if you know who will be working on the initiative. Once ...
0
Future consideration
51
VOTE
Support "NULL" checks for calculated columns
When you are using calculated columns, and want to check if a 'value type' field such as a date is null, there isn't a clean way of comparing the value to null. For example: If a date is blank, return "Not set", else return the date formatted as a...
3
Future consideration
10
VOTE
Allow Release Date (internal) and Release End date (date range) to sync
Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...
1
Future consideration
76
VOTE
Unique field layout based on feature type
As we continue to expand our use of Aha, one issue that has come up is that within a given product, there are different types of work/requirements that require different types of information. We're adding more and more custom fields, and it's star...
8
Future consideration
1
VOTE
Custom roadmap: continuous rolling 12 month view
What is the challenge? Given that we have standard views for stakeholders and teams, we have to go in every month and quarter to adjust the dates on each roadmap What is the impact? It is time consuming and another thing to make sure we audit each...
0
Future consideration
1
VOTE
To give a capability to add blank as a value for custom fields via CSV upload.
What is the challenge? Currently when doing a bulk update for a custom field if the data is already present and we need to update the field via with blanks. As of now this has to be done manually. What is the impact? It takes a huge time to do a m...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved