Default pre-ticked options when duplicating

Hi Brendan, thanks, that's an interesting request! This isn't on the roadmap, but we are internally discussing ways of managing templates and other fields of the Workspace. I'd love to hear about your processes a bit more in regards to this. How and who typically builds out templates, and do you encounter any difficulties with managing them and the processes revolving around these jobs?

Hi Anastasia,

Thanks for the quick reply!
We’re only 3 months into Wrike, so I am the only one responsible for building templates for now.
All graphic design work (and the interdependent tasks) are initiated via templates.
We currently have 4 project templates based on what needs to be produced.  

1. Design only
2. Design + print and delivery
3. Design + translation
4. Design + translation + print and delivery
   

The description in each project template’s task contain essential information (design brief template) and prompts for marketing staff to ensure they follow the design process (see screenshots below).

If marketing staff don’t select ‘copy with description’ when duplicating a task, then all this important structure is lost.

Staff are being retrained, but I also want to help streamline the process for them.

Hope this helps! Thanks again.

Brendan

Brendan, that's really helpful! The first thing that comes to mind here is the Request form feature. Have you had a chance to try that out? You can include all of those questions into the Request, and select the option for a submitted form to launch a Project from a template. Something like this, but you can obviously swap the questions out for those which are relevant to your team:

In your case, it would be best to create four separate forms, one for each of the templates:

1. Design only
2. Design + print and delivery
3. Design + translation
4. Design + translation + print and delivery 

Each of the forms will have relevant questions and only after those have been answered will the template actually be launched. Would this work for your team?

Thanks Anastasia,
We’re using forms to manage requests from our sales team and other departments, who are all collaborators. These forms then trigger one of the four project templates mentioned above. See screenshot below.

We considered applying forms to the marketing department (who are regular users) also, but the marketing team need flexibility when creating projects – all design jobs are treated as projects, with multiple tasks, which are assigned to different people. Request forms seem like an additional step. Plus, the number of variations of “marketing > design jobs” are endless.

Hope I'm making sense :-)

Thanks for following up, Brendan! I think I understand now, but the main question that remains for me is how do duplicated templates prove to be more efficient than kicking off the same templates through a Request form? Really eager to understand the setup here! :)

No worries :-)

We use dynamic request  forms. But they don't seem to work well when we need to capture information for two multiple-selected options.

For example, our request forms ask users to select what they require from a drop down.

Ideally, I want users to be able to select everything they require (Flyer, Brochure, Poster, eDM, Banner, Digital, Social images etc.) and the form will take them to a screen that contains only the questions for everything they selected (e.g. Poster, eDM, Banner). Instead, it will just take you to the questions for one option (e.g. Poster).

To overcome this, we would have to make the request form incredibly long, or have so many variations of requests form (e.g. one form each for (Flyer, Brochure, Poster, eDM, Banner, Digital, Social images etc.).

Unless I am missing something – which is likely J

This is difficult to explain in text, so I might explain with our customer success manager over a shared screen.

Brendan, thanks for the explanation! The last part you've described here is a scenario our Product Team is aware of, though we don't currently have this on our short term roadmap. Here's something one of my team members suggested after we discussed your request:

Dynamic sending to other form pages can be done via drop down questions, so we can use them to achieve the goal here.

1. Create a yes/no dropdown question for all your service/product types on the first page of the form. Let it be the "corridor", while other pages will be "rooms" for specific service/product requests. 
2. Question: Do you need Service A? If the answer is "No", we go to the next question.
3. Question: Do you need Service B? If the answer is "No", we go to the next question again.
4. Question: Do you need Service C? If the answer is "Yes", the submitter is redirected to "room" 3 (or page 4 in this case if we are counting the front page as page 1).
5. At the end of each "room" put a door leading back to the corridor, such as: "Do you have other services/products to request?", where "Yes" leads back to the corridor, and "No" submits the form.

It might sound tricky to initially set up, but with the logic in place, it can do the trick here. Happy to answer further questions if something is unclear here! :)