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...
Justin Woods
about 5 years ago
in Jira
0
Future consideration
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...
Hank Liu
over 1 year ago
in Epic
0
Future consideration
The Idea detail via includes my list of To Dos for that idea I am working on. When I add the Idea Detail to a notebook it does not publish the to do list. My idea is to allow for to dos to be added to a not book by feature, release or idea.
Joe Ross
about 9 years ago
in Presentations
2
Unlikely to implement
When using requirements for estimations as an input to roadmap planning, it would be helpful to be able to add a standard set of requirements to the feature, for example where each requirement might identify a different resource type for estimatio...
Guest
about 9 years ago
in Features
3
Already exists
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...
Dru Clegg
almost 7 years ago
in Releases / Reports
0
Future consideration
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 ...
Sam Banks
over 2 years ago
in Application
0
Future consideration
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...
Anh Truong
almost 4 years ago
in Jira
1
Future consideration
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 ...
James Love
over 2 years ago
in Releases
0
Future consideration
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...
Kyle Kinder
over 1 year ago
in Features
0
Future consideration
Support an integration with BetterWorks to sync goals, success metrics and initiatives
As a company adopting a next generation performance management system anchored in the concept of Objectives and Key Results I would like to synchronize Aha goals, success metrics and initiatives with BetterWorks (www.betterworks.com)
Note: both Be...
Guest
over 8 years ago
in Integrations
0
Unlikely to implement