Populate custom fields on work request based on feature

What is the challenge?

When creating a work request using an automation (say, feature hits a certain status, work request is auto-generated. However, I can't auto populate any custom fields on the work request because it is not a 'related record' (not until it is created).

Then once it is created, work requests are not available for any automation as the primary record.

THEN once the work request is created, certain fields should be the same between the first workspace and the second. There are no automation capabilities for creating features and populating data from the work request into the new feature.

What is the impact?

Users have to manually re-enter data when new features are created in a second workspace from a work request. It results in a lot of re-work.

Describe your idea

When a work request is created as a part of an automation, certain data fields should be available to populate based on the feature from which the work request was generated. (ex: A work request field for "target launch date" has to be manually populated after creation, but that same field exists on the original feature.

When a new feature is created from a work request, data contained within the work request should be able to be mapped to the new feature.

In this example, the target launch date from the original program is passed to the work request then the new feature without any manual data entry.