Account settings
Sort by:
Trending
Status:
Unlikely to implement
Showing 647
10
VOTE
Add History Tracking on Configuration Screens
This would allow a person to review if something changed on the configuration and what was changed.
The benefit is is something changed and a person is not aware, they do not add it back. Or if something was modified, we can find out why and reso...
1
Future consideration
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
1
VOTE
Ability to list users who are using API Keys
What is the challenge? Users have generated API Keys to update Aha and the Account Admins would like to know which users are using API Keys. What is the impact? How can we know who is updating using an API and understanding where the API is used t...
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
10
VOTE
Ability to add a clickable link for custom fields
When I add a custom field it would be helpful to be able to do one of the following:
add help text / description (this is how it works today)
add a link to help text (this is the request) - what we need users to enter is complicated and the "how ...
1
Future consideration
4
VOTE
Control which fields a Develop user can update in a record in a Roadmaps workspace
Currently when an Aha! Roadmaps record is assigned to a Develop team that gives anyone with contributor permissions in the Develop team access to edit any field on the record (even those in the Roadmaps layout). I'd like a way to control this more...
1
Future consideration
4
VOTE
7
VOTE
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
Future consideration
1
VOTE
© 2024 Aha! Labs Inc.•All rights reserved