Enable automation to update related fields with parent field value

What is the challenge?

• When a feature is moved form one release to another, child requirements do not inherit the release name and so it is not possible to update user stories in Azure Devops

What is the impact?

• The release in User stories have to be manually updated in DevOps

Describe your idea.

• Expand automation to allow setting a custom field to the same value as a parent field. In this use case, we will create a custom field in the requirement named 'Target Release' and set that field to the same release name as the parent (feature). When it is created or updated.