Account settings
Sort by:
Recent
Status:
Showing 507
1
VOTE
An option to remove prefixes found before initiative names when they have been linked within a feature
This would be useful, as an option so those who prefer the prefix can still access it. At the moment the prefix is clouding our users view, an slowing down different internasl processes
0
Future consideration
4
VOTE
Organizational roles for users
In addition to user roles for permissions within Aha, it would be great if each user could also have a role within the organization of the workspace lists/workspaces. For example, our initiatives each of a senior leader. If we add a custom user fi...
0
Future consideration
2
VOTE
Update Demand/Capacity Terminology to eliminate confusion
Currently, throughout Aha! and in the documentation the term Capacity is used loosely to imply both Capacity or Demand. This is creating confusion amongst our users and we request that Aha! clarifies the terminology to distinguish between demand a...
0
Future consideration
1
VOTE
Allow selection of "Release" in the CSV Import file
Currently the "Import from CSV" functionality requires you to select a release before you select a file to upload. This creates a lot of overhead when importing a lot of Features of Epics that align with multiple Releases. Having the option to inc...
0
Already exists
11
VOTE
1
VOTE
Change notifications language
On the notifications page, it clearly refers to only browser-based and email alerts. However, disabling them turns off in-app alerts. That is a very different thing from browser alerts and caused me to lose a month of notifications in Aha. Should ...
0
Future consideration
2
VOTE
Allow Read Only records to become disabled once data is inputted
We like the idea of read only fields to capture initial data but prevent further edits. Currently if a custom field is marked as read only data can't be inputted which seems to defeat the object of creating a field. It is fine on a bulk import, bu...
2
Already exists
1
VOTE
1
VOTE
1
VOTE
Custom Fields Export should include Custom Layout Column to know where the field is used.
When exporting Custom Fields from the Account Customizations, the Custom Layout field is not included in the extracted CSV file. It would be beneficial to have this information to understand how many layouts the custom fields may be used on.
0
Future consideration