All ideas
Sort by:
Trending
Status:
Unlikely to implement
Showing 9044
4
VOTE
Allow (clickable) hyperlinks in webpage reports and roadmaps
Who would benefit? All Sales and client facing teams using our roadmaps What impact would it make? Sales and client-facing teams often complain they can't easily download or get to resources linked to shipped (or soon-to-be-shipped) roadmap initia...
0
Future consideration
41
VOTE
15
VOTE
Support approval gates in Aha! Develop
Quality is critical for my product. I want to ensure that all features go through QA testing before being marked as "done". The approval workflows implemented by Aha! Roadmaps solve my need well. I want Aha! Develop to respect those workflows as w...
1
Future consideration
3
VOTE
Process for handling account merges in SFDC
What is the challenge? In Salesforce if I merge an account into another account any ideas that were linked on the source account are transferred over to the target account. On the Aha! side, the link in the proxy vote to the account still points b...
0
Future consideration
6
VOTE
Include Requirements when using AI Draft Release notes from a release
Who would benefit? PMs What impact would it make? Save time from creating a list report How should it work? Using AI Draft Release notes directly from a release doesn't allow you to pull in requirements of features that are contained within that r...
0
Future consideration
4
VOTE
Allow automations for custom tables based on another custom table
Who would benefit? Aha! users who have expanded their capabilities through multiple custom tables. Today, when custom tables reference each other, you need to update them on both sides. This drives no-value-add manual work and is ripe for inaccura...
1
Future consideration
24
VOTE
Ability to configure automated status logic
For almost all our workflows, a parent record's status is dictated or a reflection of it's child record's status - similar to how the progress of a parent record is an aggregate of it's child records and that functionality. I would like the abilit...
3
Future consideration
4
VOTE
Remove releases from features roadmap if all features/epics have been filtered out
Who would benefit? Product managers & their shared webpages What impact would it make? Allow us to not have to manually adjust releases based on goals/initiatives or other information that's not represented in that release How should it work? ...
0
Future consideration
30
VOTE
Ability to show 2 types of records in one column (master feature and feature records) but in different cells/rows in a Pivot report when the records are not linked.
In our configuration, we have either Epics(Features) or Master features linked to a Goal. In a pivot report, we want to show all Epics and Master Features linked to the Goal in one column.
For the report, the primary record is the Goal and Epics...
8
Future consideration
12
VOTE
Provide alternative way to match users when email address is not exposed in Jira
Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
1
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved