The profile page needs a large overhaul. Right now it is not a functional space. I would like to see it become a hub for the user to go, see what actions they have taken and easily review their interactions within the community. It should inclu...

What is the challenge? When a shared web page is generated an automatic header is generated. This header is not editable and most often not aligned with Aha customer brand + not allows for navigational elements, contact information etc. What is th...

Today under an Epic/Master Feature I can see related Features, but the layout only shows 2 fields: Feature and Status. To understand (for example) who that Feature is assigned to we have to click and open each feature. The option to "View in repor...

Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...

What is the challenge? It is possible to update a user's current paid seat group via a CSV import by adding a column for that field and inputting their new group info, but there is no way to fully remove a user from a paid seat group via this meth...

What is the challenge? Admin responses will always have the date when it the response was added to the system and will ever be from that person who added it What is the impact? losing history when migrating ideas Describe your idea just make the a...

It should be possible to import releases on a product line level. Any level of workspace hierarchy which supports the creation of any records should also support the bulk import of these records via csv.

Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...

As an admin of Aha, I would like to see history and data on workspaces, fields, tags and custom fields so I can clean up the system on a regular basis. Knowing when a field was created, by whom , where it's used would be great. I , I know some of ...

I have a mandatory custom field in Aha! Feature’s form and I would like the field to be non-editable once the release is approved through fixed workflow statuses, so that people could not make any changes there and any exception changes should go ...