All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5639
1
VOTE
Ability to Integrate Ideas with Jira Service Desk
What is the challenge? I am using a Jira Service Desk to capture new product and project requests and would like to use the Aha! Ideas for review and prioritization before sending to a specific Aha! Product Workspace. What is the impact? Today I h...
0
Future consideration
1
VOTE
Use AI to build segments for organizations
What is the challenge? Understanding ideas based on organization segments. What is the impact? Using AI to build segments could potentially surface connections between organization attributes. Allowing for better understanding of different market ...
0
Future consideration
1
VOTE
Ability to list users who are using API Keys
What is the challenge? Users have generated API Keys to update Aha and the Account Admins would like to know which users are using API Keys. What is the impact? How can we know who is updating using an API and understanding where the API is used t...
0
Future consideration
4
VOTE
7
VOTE
Add field for target release date vs actual release date
It would be helpful if, by default, Aha! could provide a field on releases to track the originally targeted release date. It would also be helpful to then show how many days the release was late by (compared to the actual release date) on the rele...
0
Future consideration
3
VOTE
Dependent questions on Polls
Depedendent questions would be the ability to have future questions that are triggered by the previous. Effectively, poll takers would never see all the quesions but rather the relevant ones based on their responses. This would allow a poll taker ...
0
Future consideration
2
VOTE
Ability to Make Record Name Read Only
We want to make all Epic fields read only for Epics with 'Done' status, as it makes sense that done Epics should not be changed / edited anymore unless reopened. We applied a custom layout for 'Done' status in a workflow; however, it seems that 'N...
0
Future consideration
7
VOTE
Allow child integrations to inherit the "run-as" user from an integration template
The following idea is for the JIRA integration, but could describe integrations to other development tools using a similar web hook mechanism.
The integration template functionality allows settings from a master template to be adopted by child int...
0
Future consideration
3
VOTE
Automations: Combined Add + Same As operation for compatible fields
Automations currently support modifying multi-item fields with the "Same as" operator, and the "Add" operator. The "Same as" operator is useful for greatly reducing the number of automations required when mapping field values, but the downside is ...
0
Future consideration
9
VOTE
Allow group for pivot on repeat release phase names
Right now record values that are consistent are only grouped together if they have a relationship or a common selected value. For those that have the same value manually entered with no relationship, they are included as separate records in a pivo...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved