Skip to Main Content

Share your product feedback

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.

  • Attach files
      Drop here to upload
    • Mike Jacobson
      Reply
      |
      Mar 3, 2023

      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.

    • Johannes Wa
      Reply
      |
      Mar 22, 2022

      Yes please!

      Especially with Integrations, it is sometimes required to fill fields on each requirement.

    • Guest
      Reply
      |
      Oct 14, 2021

      It would be helpful if when assigning an initiative to master record that it would also apply to feature record. I vote yes


    • Guest
      Reply
      |
      Aug 6, 2021

      This would be a massive improvement at the moment we have to manually put the release number in the Requirements

    • Peter Frederiksen
      Reply
      |
      Apr 13, 2021

      Would be nice if the feature would expand to all work items:

      Field for auto-inherit parent record data to child records

    • Jiyaad Naeem
      Reply
      |
      Nov 7, 2019

      Please do this, our PMs are requesting this to avoid duplicate entry of the same fields.

    • +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...
    Karla Johnson about 2 years ago in Features 1 Future consideration