Account settings
Sort by:
Trending
Filter by:
Status
Showing 404 of 7158
1
VOTE
Support custom properties on users
Ideally we'd like to store properties about a user within the user object it self.For example we have members in our corporate directory who aren't actual employees, potentially we'd like to key of a property that indicates that to allow us to tai...
0
Future consideration
2
VOTE
Make the terminology around "Organization" customisable
Across most of Aha! you are able to re-name key items, such as Objectives, Epics, Ideas etc... this is great as it helps you align to the terminology used inside your company. It is not currently possible to do this for Organizations. I believe it...
0
Future consideration
5
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
5
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
44
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
4
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
20
VOTE
Automation rules send to integration
Rather than have to manually push ideas to the integration with Azure, Jira or other systems, it would be helpful and reduce manual administration if the automation rules could include the capability to send on a condition such as a status change....
0
Future consideration
3
VOTE
Ability to apply a workspace template to multiple workspaces in bulk
Workspace templates are a great way to encapsulate workspace configurations into a template, so that we can quickly spin up new types of workspaces. However after creating a new template, we have a need to apply that template to a large number of ...
1
Likely to implement
41
VOTE
Indicate required fields when editing a record
We need the ability to make standard and custom fields mandatory for existing records.
When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical in...
11
Future consideration