Account settings
Sort by:
Trending
Status:
Showing 690
9
VOTE
Terminology customizations should persist throughout all screens when cascaded from Account level
We have updated some terminology for all of our products to use “Feature” (instead of default Master Feature), “Epic” (instead of default Feature) and “Story” (instead of default Requirement).
Unfortunately, this update in terminology isn’t consis...
0
Already exists
7
VOTE
Ability to 'expand all' lines within Account > Workspaces
While it is possible to selectively expand lines as needed within Account > Workspaces, it would be helpful to have the ability to expand all lines with a single action. It can be easy to accidentally miss expanding a line and keep the workspac...
1
Future consideration
4
VOTE
Support custom properties on users
Ideally we'd like to store properties about a user within the user object it self.For example we have members in our corporate directory who aren't actual employees, potentially we'd like to key of a property that indicates that to allow us to tai...
1
Future consideration
9
VOTE
2
VOTE
Allow bulk edit of a workspace custom fields that aren't on a workspace's layout from a list report
Who would benefit? Admins, workspace owners What impact would it make? It would make changes to values of custom fields so much faster. How should it work? It should work exactly like the current bulk edit option does, but the list of fields that ...
0
Future consideration
4
VOTE
Make the terminology around "Organization" customisable
Across most of Aha! you are able to re-name key items, such as Objectives, Epics, Ideas etc... this is great as it helps you align to the terminology used inside your company. It is not currently possible to do this for Organizations. I believe it...
0
Future consideration
6
VOTE
Collapse audit history records on linked objects when a custom table is edited
When editing a custom table, linked records will have history records added which describe a new custom field being added. This creates noise in the history and makes the history of the object hard to track.
0
Future consideration
7
VOTE
CSV import template: Please provide all default fields in the CSV template
When I go to do an import, I review the ‘What Fields Can I Import?’ function, and more often than not I download the Example CSV file. The issue is that the Example CSV file does NOT contain all the fields that are available to import. This is a b...
0
Future consideration
1
VOTE
Improve user experience of Idea Category type custom field
We promote Ideas to Epics and automatically populate the Idea Categories field into an Epic field, which calls from the idea categories of our product line. When we try to modify or add categories using the Epic field, we are encountering some iss...
0
Future consideration
1
VOTE
Integration of company's proprietary AI engine with Aha!
What is the challenge? User can only use default AI engine. Due to company's cybersecurity polices, we cannot enable AI related features. What is the impact? By integrating company own AI engine, the system will benefit from enhanced data security...
0
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved