All ideas
Sort by:
Trending
Status:
Showing 8942
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
1
VOTE
Allow Custom Worksheets to filter out archived records
What is the challenge? Filtering out Archived data from current data What is the impact? Impacts custom worksheets and reporting Describe your idea make the "Initiative Archived" value reportable so that it can be filtered in custom worksheets Cur...
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
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
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
29
VOTE
Inherit Field Values from Feature to Requirement
We have a field that exists on both our Features and Requirements, and that custom field is being used in our JIRA integration. When creating a new requirement, it would be great to have the field auto-populate from what is specified in that field...
6
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
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
1
VOTE
Control path and slug of knowledge base document's URL
What is the challenge? Replatforming an existing knowledge base to Aha! requires editing all intra-knowledge base hyperlinks since part of the published Aha! document's URL is systematically assigned and not controlled by the document author. What...
7
Already exists