All ideas

What is the challenge? Editing existing comments in ADO do not sync back correctly in Aha! What is the impact? Comments can become out of date and not contain the correct information. Describe your idea Sync edits to existing comments

What is the challenge? Our team has a process where we gather customer votes through a submit-only portal throughout the year, then at the end of the year we open up these questions for voting w/ a vote limit to our customers' designated voters. C...

It would be really useful to be able to filter at the Epic level on the strategic roadmap. The current filters (i.e. release settings > show parking lot) only apply to the initiatives. For example, we have cases where items are in the parking l...

As a product team member, I have a series of documents that need to be captured on every epic (such as a BRD, a kickoff session agenda, and a retrospective agenda). I'd like to define a "template" experience such that when new epics are created, t...

Hi Aha! Team, as an organization we use Aha! together with Azure DevOps (both integrated) in order to track the progress and delivery of initiatives. As we work in an Agile environment, our roadmaps are usually built on a Sprint basis (e.g. Initia...

The Capacity report for teams provides the ability to see the available capacity per team per time period by hovering each cell/ It would be helpful to be able to include the available capacity per team in a list/pivot report. This would provide t...

What is the challenge? Currently, integration actions from automation rules can only be created for workspace-level automations. These automations can only be copied but cannot be applied to a workspace template. Currently, workspace templates are...

I think todos have a lot of potential to represent non-feature work across Aha. I like the idea of not "polluting" aha with workarounds where features are used to represent work, nor requirements used to represent non-feature related work. There i...

What is the challenge? For large scale implementations it requires a blend of general Aha! documentation and internally created documentation to provide users with a complete picture. In app we are limited to only Aha! resources What is the impact...

Who would benefit? All teams who create parent-child relationships What impact would it make? It would help teams who are using record link reporting to validate data relationships How should it work? In the attached example, a feature belongs to ...