All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5566
3
VOTE
Add 'identity provider type' attribute to 'Update user' API endpoint
Who would benefit? Customers who manage user provisioning and updates through SSO and automated API processes What impact would it make? Customers can manage their user's authentication method en masse through the API - especially helpful with lar...
0
Future consideration
5
VOTE
10
VOTE
Use an Automation rule to update 'related' ideas
It would be great if we could use an Automation rule at the feature level to update the status of related ideas. Currently, it is possible to update ideas which were promoted to the feature, however, ideas simply "related" are not updated. I would...
1
Future consideration
2
VOTE
Status pills should use the defined color
What is the challenge? Although colors have been defined for a status, the color changes and shows as lighter when in views where the element appears as a pill. What is the impact? Only a cosmetic impact, and doesn't affect other use of Aha! Impac...
2
Future consideration
8
VOTE
Ability to restrict workspace owners to adding Viewer and Reviewer users only
It would be extremely beneficial to limit the control of adding paid seat user to administrators whilst still allowing workspace owners to add viewers and reviewers to their workspace. Where adding users is required to be restricted to administrat...
0
Future consideration
5
VOTE
Project level automation with Jira
Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
0
Future consideration
10
VOTE
Should be able to insert rows at any position in the custom table (like its on G - spreadsheet)
When i click to add row in a custom table the rows get added on the top. This could be desirable when you want to add comments so that the latest appears on the top but highly undesirable when you want to serialize items (1-n) with 1 appearing dow...
1
Future consideration
15
VOTE
Derive the Master Feature Release(s) based on Child Features
It'd be great if I had an option to have the system derive the release(s) that a Master Feature belongs to based on the release(s) that the Features that tie up to the Master Feature are slotted in. This would include the ability for the master fe...
4
Future consideration
3
VOTE
Automate feature creation on epics
Who would benefit? User teams that do a lot of repetitive work with contextual differences What impact would it make? It would help keep backlog items consistent and reduce the time needed for repetitive work created with necessary data relationsh...
0
Future consideration
5
VOTE
Limit available teams on the capacity report to the active workspace(s)
Currently, when using the capacity report, teams from other workspaces are listed as filter criteria. It would make the teams dropdown quite a bit cleaner if only teams in the selected workspaces were selectable.
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved