Features
Sort by:
Trending
Status:
Future consideration
Showing 575
6
VOTE
Redirect users to accessible version of link if they do not have access to internal link
Users submit requests via an externally facing portal. Once that request is received, the team handling the request have one view of the request, while those who do not have that internal access can only see the publicly visible version of the req...
0
Future consideration
11
VOTE
Add "current user" as a selectable option in all user filters
As an Aha! user, when I filter based on User ("assigned to", "created by", etc.), I should be able to choose "Current User" as an option. This way, when I save and share a View, the results are dynamic and update based on the signed in User.
For e...
1
Future consideration
2
VOTE
Show last modified date on lists
Who would benefit? users in need of detail What impact would it make? provide additional method of validation or review How should it work? When adding columns to a List, whether features, epics, requirements, etc. it would be nice to have "Last m...
0
Future consideration
7
VOTE
Allow a feature to transition to different release phase when feature status changes
In order to make best use of multiple release phases I would like to be able to automate the moving of a feature from one phase to another when I update its status. For example a feature will be In design as a feature status and part of the Design...
0
Future consideration
1
VOTE
2
VOTE
Nest or group to-do items together
Who would benefit? PMs, Product Ops, docs team, What impact would it make? Easier to use and navigate to-do lists within discrete phases How should it work? I'd like to be able to nest or group to-do checklist items under a higher-level checklist ...
0
Future consideration
9
VOTE
Have Workflow view respect release ranking from Features board
Currently the ranking in the Features Workflow board is not respecting the ranking from the Features Board. We use the workflow board for collaborating with the engineering team for planning and monitoring work. If we rank work in one board it is ...
1
Future consideration
9
VOTE
Record Fields should create Relationships
Expected behavior when adding a Record field to a layout is that when records are selected, a relationship link is created. Use Case: We need to drive people to link specific records and leveraged Record Fields; i.e. one or more release, one or mo...
1
Future consideration
2
VOTE
Sort by any field in Prioritization Screen
Who would benefit? Product Managers and Owners What impact would it make? Prioritizing based on more than just custom fields allows us to quickly prioritize the work, rather than manually going through and entering in the priority. How should it w...
0
Future consideration
8
VOTE
Automation: Allow an option to clear multi-value fields
At present, for Users-type custom fields, the automation options are: Add, Remove and 'Same As'.There is no easy way to remove all users. A 'Clear Values' option would be a great addition to Users field type and to other tagged field types.
3
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved