All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6024
66
VOTE
Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature
The specific use case that this commonly occurs for is the following mapping:
Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well.
Current behavior: The int...
13
Future consideration
50
VOTE
Make admin access multi-level by organization/product line
We have multiple organizations/Business Units/Groups with their own product line in the hierarchy. We would like to be able to make them admin of just that area so that they can make the customizations they need without negatively impacting produc...
7
Future consideration
16
VOTE
Change revision history descriptors for text field updates
It seems that some fields when updated via integration show a descriptor as XYZ changed integration link for Capability..123". This can be found in some values fields. Other fields like description simply state " XYZ updated the capability 123". T...
1
Future consideration
22
VOTE
Allow drill down into 'Related' records on Presentations and Webpage share
We attach a lot of ideas and/or features to epics, initiatives, and goals. That level of granularity is not needed in the presentation itself or the initial webpage view, in which we display only high level planning objects (initiatives, epics, go...
5
Future consideration
5
VOTE
Prevent users from creating blank initiatives from roadmaps
Who would benefit? Users that use roadmaps and initiatives with required fields. What impact would it make? Prevent blank initiatives from being created even though initiatives have required fields. How should it work? Option A) Users should be pr...
1
Future consideration
40
VOTE
Allow Full Customization of Email Template
As I lead design + product at my company, I'd love to be able to have full control over the contents of the email templates that are sent via Aha. Currently the content is injected into what seems to be a pre-existing template and the large logo i...
7
Future consideration
11
VOTE
Clear Multiple or All Ranked Records on Prioritization Report
Clear Multiple Ranked Records on Prioritization Report Requirement: Multiselect ranked records to remove from ranked area. Use Case: Multiple ranked records are shipped or moved to other workspaces or parking lot, and therefore should be removed f...
0
Future consideration
2
VOTE
8
VOTE
Add "documentation templates" to automatically create documents upon record creation
As a product team member, I have a series of documents that need to be captured on every epic (such as a BRD, a kickoff session agenda, and a retrospective agenda). I'd like to define a "template" experience such that when new epics are created, t...
1
Future consideration
8
VOTE
Convert whiteboard note to a requirement
When we kick off work on a new feature opportunity, we typically have a workshop session to discuss all the possible considerations and requirements of the new feature. We usually run this in Miro. I wanted to utilize the new Aha whiteboard functi...
1
Future consideration