Request Forms Using Project Templates

Hi Kate, thanks for sharing this idea! I do agree that this could be useful, and I'm really interested in learning about examples of Project, Task and Request Form titles you use (and their potential combinations), this would be really helpful for getting a better picture of different use cases here. Looking forward to hearing from you!

I agree with Kate 100%.  We love the new-ish Project-from-Template feature as it helps organize and launch projects in a streamlined and organized way - without requiring someone on our team to manually build or duplicate a project.  Our issue becomes, that our projects from templates have ~10 tasks that are identical to (nearly) every project.  Tasks include: scripting, review, deploy and others.  These task names alone are far to general and the user is forced to look to the parent folder (project) name for the context about WHICH project this instance of the task they are currently working in.  In most spots, the parent folder/project name is visible, but it is small and light gray font.  In some cases, like on mobile or on dashboards, you are not shown the parent folder/project name at all and must open the task to realize which project it is from.  When manually duplicating a project template (not automated via Request Form) the user has the option to add a prefix (for each task).  In fact, the info section for 'Task Name Prefix' option that comes up when you duplicate a project/folder specifically outlines this exact use case (see attached screenshot).  That feature solves the issue - but isn't currently available via 'Request Form - Project from Template'.

Alex, thank you, I really appreciate the screenshot! This makes sense and I agree that it would be a helpful addition to the current functionality. The good news is that we continue to work on Request Form enhancements, so it's great that you're voicing your thoughts and idea here for our Product Team to learn about.

I agree as well! I posted about this feature myself before finding this string. In our forms we use the Title feature to auto fill the task name and would LOVE if that could also be the prefix name.Often our projects, like webinars, have a dozen tasks and sub tasks. Its cumbersome to have to add a descriptive pretext to each piece. And if we don't then the assignee does't know which event they are looking at until they open the task from their dashboard. 

@Naomi, thanks for commenting here too, I didn't notice at first that you already found this thread. Thank you for adding your insight here!

Please implement this..

Agree with the Prefixing, very useful.

Wrike Requests are great.

At the moment we can create:
* Task
* Project
* Project from template.

In our work flow, It would be really useful to be able to create a

Task from template (duplicating a task) without this being a Template Project.

This way standard instructions and dependencies to sub tasks could already be set up in the task and would be copied as well, creating mini workflows.

Paul

I agree, this is a must for our company to be able to use the form to Project feature.

Please make this addition. We just ran into this issue as well.

Hi Wrike,

Please could we have an update on the above request this is very common for us and the functionality exists in Wrike already when a user currently manually duplicates a project.

Regards

Paul 

Hi all, good news 🎉

You can now specify prefixes in Request forms that create Projects from templates. Now, you can select a question to trigger the prefix (except Upload and section header) and the answer to this question will be added as a prefix to all Subfolders/Subprojects, tasks, and subtasks of a Project. The Project title will not have any prefix.

Any questions, let me know!

Tried the prefixing above, works perfectly for us, thanks :)

Paul

This is awesome!  Thank you for implementing this feature.  

Is there any way to auto generate the prefix with a custom counter? All of our projects are based on a four or five number sequence starting with the last two numbers of the current fiscal year and ending with the two numbers that represent the request number - so for instance 1837 would be fiscal year 18, and are project request #37.  This number is how we reference the invoice, the project materials, and the archive database.  It also becomes a very handy number when we use the extension for creative cloud, as it is a simple number to call up the correct task for seeing comments or uploading reviews.  

In an ideal environment, we could add two prefixes, or a prefix and a suffix - the prefix being our number that autofills with each request, and then an answer from the request form for "project title".  

As I'm fairly new to the request forms within wrike ( we were previously using a different system and manually entering the data), I'm also open to other ideas to streamline our workflow!

Thanks again!

-Kyle

Kyle Howerton Digital Media Producer

One more follow up on this - is there any way to have a character limit on a short answer field?  If clients are filling things out, I could see them getting a little too detailed, causing the prefix to be longer than it needs to be.  

Kyle Howerton Digital Media Producer

The functionality works great with the Task Prefix on Project from Template in Requests. However, the Task Prefix shows up in the description.  Why is this?

This does not need to go there.  I'm assuming no one needs this.

Hey Wrike team, where are we on this?

Is it not a simple field added to the forms?