Features

What is the challenge? If you are using a feature as a template for repeatable work and it includes a series of child requirements, copying the feature does copy the child requirements but any record relationship links between the copied require...

What is the challenge? When a Feature is copied, any field that is filled in will automatically be copied over to the newly created Feature What is the impact? Although most of time this is ok, some fields are Read-Only and therefore cannot be cle...

What is the challenge? Sometimes all the current requirements on a feature are finished before the rest of the requirements are added. This changes the feature to done. What is the impact? I have to keep manually moving the feature back ...

What is the challenge? Our PMs struggle with finding time to write all of the individual stories for their team. They'd like to be able to sketch in the story map and have an LLM flesh out the user stories: user Story statement, functional requi...

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...

You just launched a feature whereby you can create a list of to-dos in a feature, and then when you copy that feature the to-dos are copied over with them. However this is a very clumsy way to have to create new features every single time. I need ...

What is the challenge? While recent updates have improved shortcut functionality, there is still no quick way to insert dates into a document without manually typing them. This is a feature I frequently used in Notion, where typing commands like...

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? We have begun tracking high-level Requirement information in Aha! and have seen that when we copy a feature the stories are also copied. This may be appropriate in some cases, but not all. What is the impact? This may create...

As we continue to expand our use of Aha, one issue that has come up is that within a given product, there are different types of work/requirements that require different types of information. We're adding more and more custom fields, and it's star...