RELATED IDEAS
Inherit field values from Epics to Features
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 fields are changed in the Epic, those changes should also be applied to the related Features.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
© 2024 Aha! Labs Inc.•All rights reserved
This would be amazing to have. We currently do not pass Epics as part of our integration with Jira. We would like Features to include some information about the Epics so we can include that and do analysis based on it.
Agree that having the tool be smarter about inheriting values (in general) would make life easier for many admins and reduce the chance of user error
When can this idea be delivered? It will save a lot of time
100% on this one .. need it badly, and currently have to add many auomation rules to work around it.
Lots of "clicky" work required and missed information within the Feature (e.g., Completion Percentage, Assignee, Due Date, Initiatives, Goals, etc.)
Lack of this capability is causing a lot of easily avoidable manual effort and causing frustration within an org and in a way paints Aha! as inconsiderate to customer/user experience :-(.
While I know it's not generally true, there are those low hanging fruits that leave quite a bit of bitterness in users' daily experience with the product
Agreed this would be highly valuable. I tried Enterprise + but it did not work as i was expecting. We need to do custom fields and initiatives