All ideas

By default, have the Epic based data values copied over to the Feature data fields when the user creates a new feature from an epic card. This eliminates the need for re-entering and possibly inconsistent values for the same fields. If inherited f...

What is the challenge? Users are able to associate new features/epics to closed or cancelled initiatives What is the impact? Reporting on end dates for the parent is not reliable Describe your idea Force users to reopen parent OR select an alterna...

What is the challenge? The current voting mechanism for Aha!Ideas lacks clarity and actionable feedback, leading to confusion among product stakeholders. The binary "Vote" option does not provide sufficient context or guidance to requesters, res...

What is the challenge? When reviewing and analyzing interviews, I want to clip moments from interviews so I can easily share then with my team and stakeholders. It is not easy to share a section of the video where a customer describes the challeng...

Who would benefit? Any user who is using the Now, Next, Later roadmap, or those who are creating their own version with a Pivot table. What impact would it make? It would allow users to more fully customize Now, Next, Later roadmap view to tailor ...

Epic, feature and initiative layouts allow you to require certain inputs when these records are created in the platform. But if they are promoted from an ideas, portal, individuals are able to bypass the completion of these 'required' fields.

What is the challenge? Restrict closing records (Epics) if child records (Features) are not closed What is the impact? Data Inconsistency Describe your idea Allow to define a rule or validation when users are trying to close an Epic ...

What is the challenge? The prioritization report cannot display strategy fields tied to multiple records (like goals, objectives, and key results). What is the impact? Goals, objectives and key results are vital reference points when determining a...

When using master releases, it is not possible to select the release template for the sub-releases to be created. Which means the workflow to date looks like this: Create a master release Resist the temptation to select the products in the produc...

What is the challenge? The existing functionality for showing dependencies in custom roadmaps only works for "depends" but not other relationships What is the impact? If we want to visualise dependencies on custom roadmaps, we can only select eith...