Currenlty there is an option to create an automated score card but it only becomes automated when you actively click on it in a layout and click automate. clicking 'automate' on several releases is manual and tedious. The whole reason for an autom...
Guest
over 1 year ago
in Account settings
0
Future consideration
We can require fields upon a records creation with the create record layout. But to complete a record, users just need to change the status to a status in the Shipped category. However, completing a record sometimes requires other fields to be upd...
Erik Johnson
about 4 years ago
in Account settings
0
Future consideration
I like that Aha! allows me to share my product data with my organization, but I need more granular controls over who can create, read, update, and delete data. It would be great if I could create custom roles and assign them to users. Additionally...
Nathaniel Collum
about 6 years ago
in Account settings
1
Unlikely to implement
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...
Guest
almost 7 years ago
in Account settings
1
Future consideration
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...
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 ...
Sandy Goertemiller
almost 7 years ago
in Account settings
1
Future consideration
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.
Alex Bartlow
about 4 years ago
in Account settings
0
Future consideration
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...
Workspaces allow users to update/change the name AND the prefix. Similar for a Team I would like to change the prefix of the team. right now the only work around is to delete the team and rebuild everything.