What is the challenge? When linking a feature to an epic you cant limit the epics you can view What is the impact? Limiting the amount of epics you can view will make it more self explanatory, for big companies with lots of workspaces it will clea...

We use Custom Tables in many workspaces to track dollar savings.Once a project reaches a certain status these committed savings should be locked. It would be a great enhancement to be able to do this with Aha!'s 'Lock based on Status' functionality.

Current burndown charts (release > details) are created at the release level. It would be great to be able to customise the burndown to view progress at a release phase level. We would love to be able to review progress at the release phase lev...

Users want to create submit only portals to capture product feedback and wanted to have a rating field (stars similar to what’s available on amazon, etc sites). Currently we cannot use scorecard and had to create a dropdown with numbers – not very...

Who would benefit? Any users creating a workspace template from an existing workspace. What impact would it make? Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings. For example, at the wo...

I would like to map the release reference number field for Epic between Aha! and Azure DevOps Integration. But I can not find it in the field mapping of Epic. I found the release reference number field for Feature, not Epic, at field mapping of Ah...

While we have the ability to use 'select all' on certain filters, it's not available for filters such as tags, status, etc. For example, I have 100 feature tags and now I want to select 95 of them. I have to manually select the 95 tags on the filt...

In November 2018, Aha! added text wrapping to roadmaps to avoid overrunning the release and phase box. While this is great for some instances, this improvement makes the roadmap really large, which becomes problematic when space is limited. I woul...

Who would benefit? Our dev management team What impact would it make? Would provide much better insights into why a release went off track. Currently the "Records Added" section lists Epics & Features added after dev started. In our case, it's...

It would be useful to be able to allocate to-dos to approval groups, where the task is assigned to multiple assignees, but only one approval is required. At present, a to-do can only be marked as complete when all assignees have completed it. An e...