Add more specificity/granularity around automation logic.
Who would benefit? Both Aha! administrators and the product team members they support through administration of the tool. What impact would it make? It would allow Aha! administrators to automate actions and notifications that advancement can be m...
Christina D
8 months ago
in Account settings
0
Future consideration
Add a field to USERS to identify Consultants or outside resources.
What is the challenge? Trying to identify consultants or outside resources hired/brought in to work on projects and be able to pull reports for capacity, associated cost or HR. How would you solve it? Add a field to be checked with a dropdown to a...
Tammy Culp
4 months ago
in Account settings
0
Future consideration
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...
Kristina Gass
9 months ago
in Account settings
0
Future consideration
Who would benefit? Enterprise+ Aha users What impact would it make? Improved usability of equations How should it work? When creating equations in worksheet custom fields it should be possible to hide rows from being visible, for instance when cre...
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 ...
Jason Gillmore
9 months ago
in Account settings
0
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
about 2 years ago
in Account settings
1
Future consideration
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
about 2 years ago
in Account settings
1
Future consideration
Customize / Create New Record Link Relationship Types
In Aha! we can only create record link with the 6 default relationship types, while in Jira the new relationship types can be added and are customizable. https://www.aha.io/support/roadmaps/strategic-roadmaps/collaboration/create-record-links We n...
Hank Liu
over 1 year ago
in Account settings
0
Future consideration
I live in Germany, like to use my apps in US English, want the ISO 8601 date formatting (2017-05-31) and want a space as the thousands separator. It really sucks that there is only a "locale" setting which assumes I want to use a certain formattin...
Guest
about 7 years ago
in Account settings
4
Future consideration