All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5643
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
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
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
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
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
5
VOTE
Support Movement of Requirements to Different Features in Other Workspaces
We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to feature...
1
Future consideration
3
VOTE
Multiple Independant Releases within Master Releases
As an enterprise SaaS software provider, we need to manage releases in two key categories, major and minor, so that we can monitor the iterative delivery of our minor releases as a part of our major, less frequent, releases and provide clarity to ...
0
Future consideration
2
VOTE
Initiative - Include Related Records
It would be helpful if we had an option on initiatives and rollup initiatives to automatically include any records related to the records related to the initiative. For example, after associating a release to an initiative, we could click a button...
0
Future consideration
8
VOTE
Show "Last Update Date" in all screens
It is critical to show "Last Update date" in screens like
Vision, Goals, models, Personas, competition, positioning and all other screens.
Looking at our Product Portfolio, it is critical to understand how relevant the information is (was it updat...
1
Future consideration
2
VOTE
Set default for presentation export
Increasingly we're wanting to export standard presentations across our enterprise.Each time someone does this they have to go in and configure some setting around footers and enhanced security as shown in attachment... We'd like it if we could set...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved