My ideas: Features

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

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

Similar to Capacity line in the feature board , we would like a target, commit, and stretch line with user defined % of capacity. Ex, 80% = commit, 100% = Target, 120% = Stretch with 3 lines. This way I could have a quick visual of my capacity in ...

Just as you can merge ideas, it would be great to be able to merge features.

Related to: https://big.ideas.aha.io/ideas/APP-I-2911. It would be great to have the option to bulk delete integration links for features in Aha. For example when you know the corresponding issues in JIRA don't exist anymore.

This has been requested to provide more default options for sorting. Enable the ability to automatically sort the feature cards in each workflow column (by score, estimate, rank, etc.)

When you create or copy a feature, its ID is automatically created based on the product code. The ID is a combination of the product code and an auto number (and that is perfectly fine). But when you change the release reference to a release of an...

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

Aha! allows you to create feature workflows for a product, but not for a feature type. It would be helpful to have product workflows applicable beyond the product - allowing users to customize completion workflows per feature type. Let's look at ...

Hi, I'm looking to have the ability to change different behaviors based on field values. For example, let’s say I added a custom field called “expected feature date”, and I assigned this feature to a release, where the release date is larger than ...