Task Template should not override Word Request Fields and assets
Work Request

-
Roman Bobiš commented
UPDATE 12 August 2025:
When selecting a Task Template at creating a Task from a WRQ, we can choose what will be overwritten by the Task Template but NOT the Brief - this checkbox is locked. In lot of cases we need to pull in also the Brief from Task Template. For example if the Work Request is "Multichannel initiative" we need to create multiple Tasks from it - e.g. for Social, Web, Event, etc. But here we cannot pull in the Briefs from the Task Templates. We would appreciate to have the option to check also the BRIEF checkbox (ideally unchecked by default) so we have the freedom to choose if we want the BRIEF from WRQ or Task Template. -
Roman Bobiš commented
This is important for us as we create Tasks from Work Request and benefit from the WRQ inputs being automatically pushed to the Task Brief - this is super helfpul. We also love the Task Templates where we define also the Workflows and files in the Content tab (e.g. working docs templates). Unfortunately, if we choose a Task Template when creating a Task from a Work Request, the fields pulled from WRQ are overridden by fields from the Task Template. So we cannot benefit from the Task Templates anymore. I just noticed in our TEST instance (on Edge env.) that Brief is not overwritten, but the Fields still are - so we cannot then use the fields like Region, BU for filtering views in Plan module, or reporting. So, we request to be able to choose what is to be taken from the Task Template - incl. the Fields