Application
Sort by:
Trending
Status:
Unlikely to implement
Showing 7705
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
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
7
VOTE
Allow external team members to Approve work via To-dos
What is the challenge? We need to get some sort of Approval or Sign-off from our customers (not Aha! users under our account) on the requirement or feature that we have created for them. What is the impact? We need our external customers to agree ...
0
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
Override Workspace Template Automations
What is the challenge? We have standard automations needed across a majority of the account with a few exceptions. We would like to disable those that we do not want to be used in certain workspaces. What is the impact? 99% of the time we want wor...
0
Future consideration
3
VOTE
link whiteboard object (x,y) position with field values
What is the challenge? When using a cost-benefit whiteboard to prioritize features it would be very helpful if the position i move a feature to was persisted to the feature card. What is the impact? This would make whiteboards part of actual work ...
3
Future consideration
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
57
VOTE
Expand/Collapse Release View to include Requirements
It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.
7
Future consideration
93
VOTE
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
© 2025 Aha! Labs Inc.•All rights reserved