Account settings
Sort by:
Trending
Filter by:
Status
Showing 390 of 7020
12
VOTE
7
VOTE
1
VOTE
Add possibility to have title read only
In case of integration (e.g. DevOps integration) there could be some records which should not be modified in Aha (or at least some fields) but only in the integration. All fields can be set to read only via the custom layouts, but title can never ...
0
Future consideration
16
VOTE
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...
0
Future consideration
1
VOTE
List report of all users w/in my product line and the workspaces under it
We recently went through a reorg and have users that are either no longer with the company, have changed roles/responsibilities, etc. that will need their access/permissions changed which will result in a cost savings for the paid subscriptions. I...
0
Future consideration
4
VOTE
9
VOTE
Introduce Customization Owners
As a large organisation with several independent product verticals, we need the ability to lock down account-level customizations (e.g. layouts, custom fields, workflows) by owner (+ collaborators) so that we can retain adequate controls without l...
0
Future consideration
3
VOTE
Follow custom terminology in Pivot reports to reflect customized terminology of where the report was originally built, not where the report is run
Pivot table headers use the terminology from the workspace they are being viewed. I want to see the terminology that is used from the workspace line where the pivot table was built. By not reflecting the customized terminology we are effectively i...
0
Future consideration
3
VOTE
Follow custom workspace line terminology when viewing Roll up to workspace goals
When a workspace line references its parent, the naming of that parent should match the parent level, not the workspace level. By not reflecting the customized terminology we are introducing layers of confusion for the team members who don’t spend...
1
Future consideration
43
VOTE
Automation: support setting a date field to a value relative to another date field
I wanted to create an automation to update the external release date to match the release date on a release when that changes. Arguably we should just do this automatically already... but I was hoping that Automation would solve the issue After se...
5
Future consideration