RELATED IDEAS
Inherit Field Values from Feature to Requirement
We have a field that exists on both our Features and Requirements, and that custom field is being used in our JIRA integration. When creating a new requirement, it would be great to have the field auto-populate from what is specified in that field on the feature this requirement belongs to.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
1
MERGED
Feature become Initiative aware through a parent feature
Product Managers want to have an initiative with 5 parent features (Epics) that each have 5 features. Each feature needs to be able to know the Initiative Reference Number it can be passed through the integration to the ‘Funding ID’ field in Rally...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved
Our development team likes to estimate requirements grouped by fields at the feature level. Currently, you can only automate clearing a field or setting a specific value instead of inheriting the parent feature value. This would be great for us to add another option to field update automation rules.
We have a similar Use Case: We have an initiative with 5 Epics that each have 5 features. Each feature needs to be able to know the Initiative Reference Number it can be passed through the integrated record.
Yes please!
Especially with Integrations, it is sometimes required to fill fields on each requirement.
It would be helpful if when assigning an initiative to master record that it would also apply to feature record. I vote yes
This would be a massive improvement at the moment we have to manually put the release number in the Requirements
Would be nice if the feature would expand to all work items:
Field for auto-inherit parent record data to child records
Please do this, our PMs are requesting this to avoid duplicate entry of the same fields.