Automation: require field based custom field option

What is the challenge?

During the lifecycle of an Epic, we have fields that when a certain option is selected, another field should be required.

What is the impact?

Data is not complete so reporting is incorrect. We have features that that when a value is selected, we need additional information to ensure robust reporting.

Describe your idea

Allow for a fields to be set up for a specific value, another field is then required.