Applying a Task Template should not erase the information already captured in a Work Request.

The problem:

When creating a Task from a Work Request (WRQ), selecting a Task Template removes all Fields inherited from the WRQ — even if the template has no predefined Fields.

This forces users to choose between:

Preserving WRQ metadata needed for planning, Saved Views and reporting.

Using Task Templates to standardise workflows and preload working documents.

Similarly, organisations need to use Workflow Fields to capture information that only becomes available during delivery, rather than requiring everything at the initial Work Request submission. Applying Fields in Workflows overwrites the Fields from Work Request too.

These are standard, complementary capabilities that should work together.

Feature request:

Enable Task creation from Work Requests while:

Allowing to choose if the Fields should be carried from Task Template (just like it is possible for Content, Brief, etc.) or from the Work Request. This should be similar for Workflows - allowing to define mandatory fields also for completing the Workflow.

Value for CMP customers

Tasks created form Work Requests can use
A) Task Template to preload document templates
B) Workflow Fields to define which fields must be filled in before the Task completion
while the inputs from a Work Request are preserved in Task´s Field - displayed in Saved Views and used in reporting.