Account settings
Sort by:
Trending
Status:
Showing 693
1
VOTE
Allow automation rules based on Feature name
What is the challenge? Automation rule triggers are limited, not enough customization. Feature name is a particular use case that would open up a lot of possibilities, especially for teams that use naming standards and conventions. What is the imp...
0
Future consideration
2
VOTE
Dynamically adjust whitespace on "Workspaces" page in Settings
Who would benefit? Customers with a lot of workspaces and workspace lines What impact would it make? This would make it easier to see more content on this page at once and more easily adjust the hierarchy and edit workspaces. How should it work? T...
0
Future consideration
8
VOTE
Rules based status changes on workflows
We need a feature that allows the Release status be automatically changed to a "red" or blocking status value based on a rule. An example for a rule would be:
If Release date is < than Today AND Release status NOT Equal to Shipped than set Rel...
0
Future consideration
8
VOTE
Alphabetize Products in Top Left Dropdown
It is difficult and awkward to quickly navigate to Products you are interested in because they are not sorted alphabetically. They appear to be sorted in the order they were created. Unless you remember the exact name and/or location of the Produc...
1
Future consideration
2
VOTE
Have workspace templates be default for new workspaces
Who would benefit? anyone who administers an aha account What impact would it make? streamlines work, reduces chance of manual error, reduces need to manually verify items How should it work? allow account admins to set what the default workspace ...
0
Future consideration
2
VOTE
Consider inherited values when copying workspace settings for workspace templates
Who would benefit? Any users creating a workspace template from an existing workspace. What impact would it make? Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings. For example, at the wo...
0
Future consideration
2
VOTE
Develop team owners should be able to manage team members
Who would benefit? Team owners that do not have the customization admin role What impact would it make? Currently Develop team owners do not have a place in the team settings to manage the users in their team, but this is a permission owners have ...
0
Future consideration
7
VOTE
Update product prefix on existing record IDs
We need to update several of our product names and prefixes, however, the capability in the GUI doesn't allow us to reset or update the prefix for any existing records. Going this route means we would have a product with features in it that show d...
0
Will not implement
11
VOTE
A Private View of Comments or Notes
It would be great if we could mark Comments and Notes as private or restricted based on the User's email domain (or something) so that teams who work with external clients (like my firm does) can still have "internal conversations" within Aha but ...
1
Already exists
4
VOTE
Limit Name field in all objects to 255 characters
When integrating to Rally, integrations fail due to Rally's 255 character limit in the matching field. There are no error messages or notifications. This was determined through some back end research. In order to prevent this in the future, we wan...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved