Currently, when looking for a specific component via relationship or when using "#" in a note/comment etc and you know the id, you always have to put in the whole id including the workspace prefix. If you only use the numeric id, you don't see any...

What is the challenge? having to manually replace current year in KB What is the impact? wasting time and effort multiple times for something a computer should do Describe your idea Using a variable to insert the current year in the footer (or els...

As a planning exercise, I may generate a multitude of scenarios using teams capacity planning. However, I do not want everyone to be able to view and toggle to those scenarios I've created and see the total estimates for all of those scenarios. I ...

Currently the user story map creates records in the left-most parking lot release - the way we use our parking lot releases makes this not ideal and will require a process change. Instead, it would be nice if this was either user configurable to s...

Who would benefit? Ideas Advanced users What impact would it make? Analyze ideas and other work by additional segment data How should it work? Like Organizations, it would be helpful to add metadata about segments such as TAM, Segment owner etc. S...

Who would benefit? Users creating advanced worksheet equations What impact would it make? It will allow to perform calculations based on the number and types of linked records How should it work? Custom worksheet are very powerful, but it is not p...

What is the challenge? can;t search records by the assigned to field using AI What is the impact? can;t search records by the assigned to field using AI Describe your idea can;t search records by the assigned to field using AI

USE CASE: As an Aha! Administrator, I need to be able to respond in a *snap* to leadership decisions that require re-configuration across hundreds of workspaces. Our organization already has 200+ workspaces. This week, a critical leadership decisi...

The first_name and last_name claims required by Aha! are not OIDC conformant, leading to duplicate information in previously conformant JWT tokens. This increases the size of tokens. This can also make it harder to use a common token for Aha! and ...

As a company adopting a next generation performance management system anchored in the concept of Objectives and Key Results I would like to synchronize Aha goals, success metrics and initiatives with BetterWorks (www.betterworks.com) Note: both Be...