My ideas: Account settings
Sort by:
Trending
Filter by:
Status
Showing 506 of 8642
3
VOTE
Allow for integration via OAuth 2.0 Service Accounts
Ask: Support OAuth 2.0 Service Accounts for auth on the Aha! API
Background: We use SSO (Okta) for user authentication (Aha! doesn't know about passwords by design). We also have a set of scheduled tasks (scripts) that query the Aha! API, summari...
1
Already exists
1
VOTE
Add a filter to Account Settings - Custom Fields by Used in Layout
User, needs to filter by 'Used in Layout' in the Account Settings for Custom Fields, to easily view fields used in specific layouts and more easily edit specific fields per layout, or to see or not see fields that are not in a layout. This would i...
0
Future consideration
2
VOTE
Maintain item ID when Promoting/demoting
When changing a feature to master feature, to initiative and back (demoting), the item is recreated, resulting in a new id, and a new link. If a team is documenting the features/master features etc with links, this documentation will lose value wh...
0
Future consideration
1
VOTE
Make New user message easier to edit and away from security
We have a custom New USer message but when you go to edit it the entire message disappears so if you just want to remove a name you have to reenter the entire message. It is also closely tied to the security area and should be separate so that the...
0
Future consideration
2
VOTE
Allows us to use Display Name with OKTA
OKTA has a username & display name option, however, Aha! doesn't pull in the Display name to give you the option to visualize that or give you the option to edit the name. This is a frequent request from my users who do not go by a legal name....
1
Future consideration
1
VOTE
1
VOTE
Support One to many relationship fields on Customize record cards
Why is it useful? Ability to add One to many relationship fields on Cards really helps to view the field value at glance rather than to open a record to view field values.
Who would benefits from it? Anyone who uses board.
How should it work? It...
1
Will not implement
2
VOTE
One Field Directory for Records
It is very tedious as an admin to have to recreate fields numerous times that are used across all record types. Most systems that I have built out (SFDC, JIRA, etc.) have one entity database that is shared across all record types and it would be i...
0
Future consideration
1
VOTE
3
VOTE
