Who would benefit? Aha administrators, anyone responsible for maintaining integrations/records between systems What impact would it make? Reduce potential issues with integration records not always synching as expected, resulting in inaccurate or ...

Currently exist only pre-defined colors for Releases, Features and Initiatives in the Starter roadmap if you switch to Color bar by type. I would like to choose my own color e.g for all Initiatives

We have a field that exists on both our Features and Requirements, and that custom field is being used in our JIRA integration. When creating a new requirement, it would be great to have the field auto-populate from what is specified in that field...

In the Aha! we have Features that reference a parent Epic in another workspace. In Rally we have portfolio items that are children of a Capability in another project. This cross workspace/project relationship is supported in Aha! and Rally, but th...

What is the challenge? Customers who want a tailored KB experience for users want options to further customize this. What is the impact? This would allow customers more flexibility to customize their KBs to their own brand and the experience they ...

What is the challenge? Reviewers cannot rearrange record ranks in the prioritization view. Only owners/contributors can. If I only have reviewer permissions to all the workspaces I have access to, I can still create a prioritization view but I can...

What is the challenge? We've defined a set of objectives (goals) and a set of initiatives under each goal. But the UI allows epic and feature creators to select objectives and initiatives that are independent of one another. What is the impact? Th...

Currently we can rename the title of the Salesforce widget. We can also customize all the text within the Ideas portal in Aha. For us, we want to use this connection but we don't want to call them ideas, but rather e.g. Requirements. This is possi...

It would be great if, instead of just showing the underlying value, the scorecard metrics could use abstract labels... for example, for an 'effort' metric we might use t-shirt sizes such as "Small", "Medium", "Large" and "X-Large" behind the scene...

What is the challenge? Representing the same data in different object levels (initiative, MF). Today this is achievable only via automation What is the impact? When there are many automations, it would become complex tomaintain, as this is in the ...