Account settings
Sort by:
Trending
Status:
Shipped
Showing 606
5
VOTE
Ability to select only one user from the "User Field" custom field
Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users.
It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises ...
0
Future consideration
3
VOTE
Allow for creation of Custom Fields that are a relationship to "Teams"
Aha allows for the creation of Custom Fields as "record relationships" with many objects, but doesn't include relationship to Teams. As we start using Demand/Capacity, creating relationships with Teams would be very valuable to allow for flexibili...
0
Future consideration
3
VOTE
Aha! Workspace Configuration Report - update the default settings
1: Please add a 'workspace name' filter to the View Report (Workspace Configuration Report) as there there are no default filters. 2: Update the default ‘Edit Data’ fields by adding the 1) Workflows for all record types 2) Add only custom layouts ...
1
Future consideration
6
VOTE
Advanced product permissions for users
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...
1
Unlikely to implement
4
VOTE
moving paid seats from one group to another
We have multiple paid seat groups that represent each of our different business units which allows us to delegate the administration of paid seat licenses. Each seat group has maxed out their allocations and we have no unused licenses. The issue i...
2
Future consideration
7
VOTE
Product line only permissions
As an Aha! admin of product lines, I would like to provide access to the head of strategy to contribute to strategy, but not to also CRUD on releases, epics, etc, so that the person can edit only areas relevant to their role.
Idea: create fine g...
0
Future consideration
6
VOTE
Remember the User's Login/Email Address
Provide some way for Users to have their Email Address stored on the login page (i.e. a "Remember Email" check box on the login screen so that users don't have to enter it every time they login. Not all of our Users want to store their password in...
0
Future consideration
4
VOTE
User tracking at business unit/department level
I'd like to understand more about who and with what frequency our users are actively using AHA! to drive adoption. We've been able to download the total users with the date they were activated and the last activity date. However, we can't categori...
1
Future consideration
2
VOTE
Show layouts used in workflows in "Used in" column
In Settings > Account > Custom Layouts, there is a "used in" column that displays which workspace(s) use the custom layout. However layouts can be overwritten by a layout used at the workflow status level. Therefore, some custom layouts will...
0
Future consideration
1
VOTE
Restrict license allocation to paid seat groups, not accounts
It's ridiculous to have "paid seat groups" and allocate those licenses to other psg's within the account. Licenses limits should be observed strictly within each psg. I've lost seats for my group without my consent simply because they've over-allo...
0
Future consideration