Skip to Main Content


Account settings

Showing 404 of 7169

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...
Ian Cooper 3 months ago in Account settings 1 Future consideration

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...
Dan Jeffery about 1 month ago in Account settings 0 Future consideration

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...
Nigel Lawrence 21 days ago in Account settings 0 Future consideration

Profile card for all users

Hello, we would like to see the details of each user, such as his Org ID, manager name, location,, which is useful for capacity planning.
Guest 3 months ago in Account settings 4 Future consideration

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...
Joe Buehlmeyer 6 months ago in Account settings 0 Future consideration

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...
Todd Meyer over 2 years ago in Account settings 5 Future consideration

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...
Ian Cooper 3 months ago in Account settings 0 Future consideration

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....
Ronnie Merkel over 1 year ago in Account settings / Integrations 0 Future consideration

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 ...
Mark Eaves 3 months ago in Account settings 1 Likely to implement

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...
Nathaniel Collum about 3 years ago in Account settings 11 Future consideration