All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5639
9
VOTE
Provide a profanity filter for Ideas
On our previous Ideas platform we were able to create a list of inappropriate words that submitters could not include in their Ideas. This helped us keep profanity off of our site without having to wait for someone to read and deal with inappropri...
2
Future consideration
3
VOTE
Allow user-specified card layout to appear on Prioritization page
On the Features > Board page, you can set a card layout. This adjusts the fields shown on each of the cards. Users can either use the default card layout specified for their workspace, or edit the layout to only affect their own user. On the Fe...
0
Future consideration
7
VOTE
Add configuration to link a Feature's Release to that of the Epic it is created in.
As a user creating (or integrating) a Feature under an Epic, I want to configure if the Feature will inherit the Epic Release, so that I can automate my Release scope when I create (or integrate from JIRA) a new Feature in an Epic. This will help ...
1
Future consideration
10
VOTE
Add Delimiter to Public comments field or add 'commenter' and 'comment date field'
I'd like to know who is commenting on ideas to measure engagement of my team with customers. The way the data is present today aggregates the comments to one field and keeps me from being able to extract the user name and date of engagement from t...
1
Future consideration
11
VOTE
SFDC Case Integration - Allow Case Owner to Submit Idea on Behalf of Case Contact
Our technical support engineers work with customers to resolve post sales technical issues. Interaction with customers is tracked in the Salesforce case object. If the issue requires a feature request in the product to resolve, we would prefer tha...
4
Future consideration
11
VOTE
2
VOTE
Separate document access settings for notes and whiteboards
Who would benefit? Aha! admins and PMs What impact would it make? This would help to ensure the relevant types of documents can be open for collaboration How should it work? Currently, document access settings for the workspace allow for edit/view...
0
Future consideration
5
VOTE
Customize navigation terminology separate from object terminology
We love the ability to customize object terminology in AHA. However, the navigation menu language follows this customization too closely, and we would love the ability to customize the navigation terminology separate and in parallel to the object ...
1
Future consideration
2
VOTE
Display related Aha ideas and JIRA integration on features roadmap
Who would benefit? Internal stakeholders What impact would it make? Would free up time for Product Managers from providing the details offline on yet another wiki, confluence page etc. How should it work? On the features roadmap, it would be usefu...
0
Future consideration
8
VOTE
Show headings from Pivot reports in presentations even if there is no underlying data to show
We produce a number of reports to key stakeholders which has information entirley pulled and automated from Aha. This is great for a number of reasons, but largley because it re-enforces the value that Aha is bringing us. Another upside is that th...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved