Option to not copy Requirements when Copying a Feature
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...
Lorena Connolly
8 months ago
in Features
2
Future consideration
This applies to all records with required default fields, not just Features: I would like to be able to customize fields that are default/'out of the box' fields on records. Specifically, I would like to be able to rename and add descriptions (hov...
Ankar S
over 4 years ago
in Features / Ideas
13
Future consideration
Improve Attachment Management for Ideas / Features / Epics
What is the challenge? There are multiple ways to add attachments to ideas/features/epics. The only standard attachment field is on the description. When creating work requests, must move attachment to description to carry over. When integrating w...
Guest
about 1 month ago
in Features
0
Future consideration
Showing running total of capacity field in prioritization view.
What is the challenge? PM can't easily tell which items are beyond the current remaining capacity. What is the impact? Currently, only board view can shows limit line. However, many users use prioritization view to prioritize records based on capa...
Ashton Tsou
about 1 year ago
in Features
1
Future consideration
Allow the creation of to-dos in a custom "create new feature" template
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 ...
Guest
about 8 years ago
in Features
19
Future consideration
Automation of feature to another release based on custom field
Who would benefit? Product Management Team What impact would it make? Ability to cut down on manual work, reducing mistakes and time spent on administrative work How should it work? Under automations, be able to set a rule as such: When a feature ...
Danielle Martinez
over 1 year ago
in Features
3
Future consideration
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...
Guest
over 4 years ago
in Features
7
Future consideration
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...
Zach Rose
over 8 years ago
in Features
8
Future consideration
When creating a new tag (as a non-admin user), select the color of the tag
What is the challenge? When creating a new tag as a non-admin user (on a feature) the color of the tag is pre-determined and cannot be changed by a non-admin user. What is the impact? When a product manager creates a new tag, the tag color is auto...
Guest
4 months ago
in Features
0
Future consideration
Capacity for teams currently allows you to create teams and add detailed estimates to records. However, we have a challenge with the way a team's capacity is calculated. We have cross-functional teams, which include people in product management, Q...