All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5862
3
VOTE
The new search functionality returns too many results when searching for multiple keywords
Who would benefit? All users with a large number of ideas including others in my organization who have struggled with this. What impact would it make? After using aha for 6 years this is the single most harmful change to my personal productivity w...
1
Future consideration
3
VOTE
Add ability to set brand guidelines when using AI
Who would benefit? Users who are using AI What impact would it make? When users draft content using AI it should follow brand guidelines to help with efficiency. How should it work? Allow users to define standards for content that is created using...
0
Future consideration
2
VOTE
Allow for consistent formatting when using AI to draft release notes
What is the challenge? We have multiple products and multiple releases happening over time. Each time a product owner creates a release note the formatting usually is different. What is the impact? The product owner then has to manually update the...
0
Future consideration
9
VOTE
Feature fields inherit values from Release fields
When I move a Feature to a Release, I'd like to have some Feature fields inherit their values from Release fields. For instance, when I assign a Feature to a Release, I want the external release date of the Release put into the Feature's "Release ...
0
Future consideration
3
VOTE
Add "Workflow approval groups" in workspace settings to reporting
Who would benefit? people like myself that administer Aha! to my organization What impact would it make? easier to check the ingrity of these reviewers to ensure our most critical workflows are being managed properly How should it work? like other...
1
Future consideration
16
VOTE
Allow bulk moving of reports
Reports often get created at the root level when first starting use of Aha but over time multiple users require different report folders. Then you need to move reports into those new folders. There is no bulk move feature so it is a lot of effort ...
0
Future consideration
11
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
4
VOTE
Copy formatting in text editor
Who would benefit? Everyone using notes and rich text description fields What impact would it make? Save time and provide consistency within a document. How should it work? Add the concept of a "format paintbrush" in the text editor that allows me...
0
Future consideration
5
VOTE
Scope / granular permissions for API Access
Hi All, currently every user with Aha! access can create an api token or authorize Apps to use the Api. And the Scope is tied to the user itself and not configurable. When it comes to projects, utilizing the API, it is the Application Owner / Admi...
0
Future consideration
14
VOTE
Maintain Audit Log on changes to record layouts
Recently we had someone make a change to a record layout and we don't know who made the change and we are therefor unable to ask this person the reason for the change. If there was an Audit Log on who changed record layouts and when, we would be a...
0
Future consideration