Settings and activity
6 results found
-
1 vote
Roman Bobiš
shared this idea
·
-
13 votesRoman Bobiš
supported this idea
·
An error occurred while saving the comment -
1 voteRoman Bobiš
shared this idea
·
-
2 votes
An error occurred while saving the comment 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.An error occurred while saving the comment 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
Roman Bobiš
supported this idea
·
-
1 voteRoman Bobiš
shared this idea
·
-
2 votesRoman Bobiš
shared this idea
·
This has got very important for us as we implemented a new process where all marketing activities start with a dedicated Work Request. After accepting a request, associated Task is created with the Brief values taken automatically from the WRQ - this is great. However, colleagues need to manually choose a parent campaign for this task (based on a text input in the request) which is 1) extra work of choosing a campaign or even checking back with the requestor if not clear 2) prone to misplacing a Task and messing up the campaign structure. Hence, we see this as very natural and important to be able to associate WRQs with the Campaigns and keen to see this addressed.