Use the release "Date range" in automations

What is the challenge?

Trying to configure a release automation to set the "Feature start date" and "Feature due date" to be the same as the "Release start date" and "Release due date"

What is the impact?

Using custom/alternate fields where this information is duplicated

Describe your idea

Enable the "Release start date" and "Release due date" defined in the release "Date range" field to be used in an automation rule