When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...

Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...

What is the challenge? When customers raise reporting questions and share screenshots, it's difficult to know when they have renamed standard fields or where they're using custom fields What is the impact? More back and forths troubleshoot...

What is the challenge? When I review the AI assistant chat history, I currently see all prior conversations together in one long list — regardless of where in the application I started the chat. This makes it harder to quickly locate past intera...

We have a central point of contact for users to get in touch with us. It is via JIRA Service Desk. To keep it central, but efficient, it will be good if a submission into JIRA Service desk can take a particular issue type and automatically submit ...

What is the challenge? Currently we'll have to change the links on the home page and create or manually redirect new links for our product/support teams to share release notes documents. This is especially problematic for teams that release freque...

What is the challenge? If an ADO user has done things like add new projects, or add new area paths to their projects, the only way to see these in the selection dropdowns for the integration wizard is to go back and re-submit the previous step. ...

What is the challenge? It can be difficult to zoom in and out and see the larger context when working on on a whiteboard. What is the impact? You may want to focus on a specific object (feature, story etc.) but also see the wider context o...

Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...

Similar to Capacity line in the feature board , we would like a target, commit, and stretch line with user defined % of capacity. Ex, 80% = commit, 100% = Target, 120% = Stretch with 3 lines. This way I could have a quick visual of my capacity in ...