Account settings
Sort by:
Trending
Status:
Showing 631
1
VOTE
View more than 20 users at a time from account settings
Configure a drop-down selector to allow an administrator to view more than 20 users at a time, for example (20, 50, 100, 500, 1000). Currently, if you try to check a few users for a bulk update and then navigate to the next page of users, the chec...
0
Future consideration
1
VOTE
Add ability to view more than 20 users at a time from Account Settings
Adding the ability to view more than 20 users at once, preferably through a drop-down selector (20,50,100,500,1000) would make bulk edits of user permissions easier for administrators. Currently if you select a user and then navigate to the next p...
0
Future consideration
4
VOTE
permission-restricted release or feature status
We should be able to configure specific release statuses so that they're restricted, editable only by certain users or user groups.
We have a Program Management group which maintains an authoritative list of releases the product organization has c...
1
Unlikely to implement
2
VOTE
Inconsistent / Broken Terminology
Within Marketing, Business and Project Lines, the customize terminology setting is broken and creates an inconsistent user experience that confuses users. Within the 'Customize Terminology' setting (Settings > Product Line > Terminology), if...
0
Future consideration
1
VOTE
Allow deletion of types and other data while still in use
There are several places in Aha! where we disallow a user action because an object is in use. For example, users can't delete a custom type while records are using it. We already have an elegant solution in place for this when changing from one wo...
0
Future consideration
2
VOTE
Line and Workspace management - stop collapsing the Line / Workspace hierarchy each time you complete a Line
If we leverage UX / UI, when a user-persona leaves a data structure in a window, they should expect it to remain the way they left it when they return, or complete a task Currently, when I go to the Customized Workspaces --> then expand some or...
0
Future consideration
2
VOTE
Opening 2-factor authentication to other providers
aha!'s 2-factor authentication implies signing up with a designated 3rd party. We would like to include aha! with the other solutions in our IT portfolio, for which 2-factor authentication is supported by a different supplier than aha!'s partner.
1
Future consideration
4
VOTE
Ability to suppress Product Line level custom fields from products
We have some custom fields that we want only to appear at the Product Line level, specifically for Master Releases and PL Initiatives. We'd like a way for them not to appear in Product Initiatives or Releases. As it stands now we just need to inst...
0
Already exists
2
VOTE
Sync Record Fields - Idea / Feature / Epic
Our organization recently did an overhaul and added dozens of custom fields to ideas, features, and epics. The vast majority of our records were created before the overhaul, which means most of the fields are blank. We use the Idea Portal to updat...
0
Future consideration
4
VOTE
