Often settings like layouts, terminology, and navigation for parent lines may be purposefully different than workspaces. It would be helpful to drive standards for lines by allowing templates to be applied at those hierarchy levels. A few examples...
Jeanette Resnikoff
over 1 year ago
in Account settings
0
Future consideration
Allow ability to limit valid values in Feature fields to only display relevant values for the workspace.
When defining features in a workspace, you should only need access to utilize valid values from selected workspaces. Each workspace owner defines and reports on their valid values very differently. When all valid values from every workspace are di...
Karla Johnson
almost 2 years ago
in Account settings
0
Future consideration
Make admin access multi-level by organization/product line
We have multiple organizations/Business Units/Groups with their own product line in the hierarchy. We would like to be able to make them admin of just that area so that they can make the customizations they need without negatively impacting produc...
Marina Reyna
over 5 years ago
in Account settings
7
Future consideration
I would like to be able to copy a custom field, for example from Features to Requirements. I have several custom fields for Feature, then when I want to create a requirement from Aha! it complains those custom fields are not available,
Guest
over 6 years ago
in Account settings
8
Future consideration
When editing Tags list on "Config Tags" page, having the ability to bulk edit Tags (Delete specifically) would be very handy as the tags list could become very lengthy and removing multiple tags (with a criteria e.g. Tag starting with RFP#) takes ...
Who would benefit? AHA! and BU What impact would it make? No user could get an elevated role without a licence How should it work? When Admin assign roles that require a licence, they need to select a licence pool. When the admin changes a user ro...
Guest
about 1 month ago
in Account settings
0
Future consideration
It's cumbersome to need a unique custom field for the same data across different item types. It would be more efficient to be able to use a single custom field in multiple item types.
Max Cascone
over 5 years ago
in Account settings
7
Future consideration
The ability to configure which fields are included in the feature to pdf export
Who would benefit? Customers who are required to share feature documentation with enterprise or large government clients What impact would it make? Ease of hiding internal information or displaying only customer relevant information How should it ...
Megan Sullivan
about 2 months ago
in Account settings
0
Future consideration
When a user logs into Aha!, the first page they see is the page "How Aha! works". Our users are reporting that this is confusing, as they want to navigate to a page within the product itself (i.e. Feature Board or Releases Overview"). Users arrivi...
Matt Howard
over 5 years ago
in Account settings
8
Future consideration