What is the challenge? Currently, where a Jira Board is set on an integration it cannot be edited or removed. What is the impact? Customers who are not mapping the Jira Sprint field do not need to select a Jira Board. However, once the Boa...

Currently mapping the Aha! "Release name" field to a Jira Label (type: string) field is not supported. While the team is able to map the field to a text field in Jira, it has limitations for querying and plotting chart. This idea is to support map...

The duplicate idea detection appears to rely heavily on shared keywords, which leads to unrelated ideas being suggested as duplicates. For example, in our language support workspace, any idea that includes the word “language” is surfaced as a pote...

What is the challenge? Currently if we have a pivot chart on our dashboard, you cannot click into the Summary Totals within cells and see the records which relate What is the impact? This adds lots of clicks, because if you want to drill in and se...

What is the challenge? I would like to integrate data from other systems when I am working with the AI Assistant, like my Figma designs. What is the impact? Describe your idea Add support to the AI Assistant for third party MCP serve...

What is the challenge? When changing the feature type to one that does not have a template, it no longer removes the last template from the description box. This used to work, but has been broken for months. What is the impact? The box has...

This applies to all records with required default fields, not just Features: I would like to be able to customize fields that are default/'out of the box' fields on records. Specifically, I would like to be able to rename and add descriptions (hov...

We have "Same as" functionality for certain field types now available for automations. It would be helpful to see the same ability extended for number fields, so related/promoted records can be populated with these when they are created or updated.

Aha! Develop has excellent support for SAFe in its program increment, sprint planning and program board functionality. Teams who are doing PI planning in Aha! Roadmaps with their engineering teams in other development tools are not able to benefit...

What is the challenge? The user interface feels disjointed and separate. If we can combine to one in a side column or on top that allows you to instantly see everything together, this would be absolutely amazing and leadership would have higher ...