Request Form: Adding Due Date option for each subproject/subitem

We use Wrike for our marketing team. Our current request form allows you to choose a project type (ie. collateral, email, blog, etc) and we've added a due date question, which then creates a project from a specific blueprint and reschedules it around the "latest task's due date".

We are looking to create another request form that allows you to choose several "project types" and to "add subprojects" from each but when adding a subproject there is no way to schedule a due date. Note: Not all of our campaigns require the same "project types".

Ideally, we would be able to choose each project type in a multi-select question and...

1. When choosing "add subproject" another option would be added to "reschedule around [latests or earliest task date]" and then adding a due date

2. Add a follow-up question for the due date that allows it to be rescheduled.

I would love to hear how your team has found a workaround for these types of campaigns. Thank you!

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Tiffany Sands

I haven’t done this exact use case, but I do have a form where depending on the options people choose they get different tasks, which also then have different due dates. I set this up by setting an action based off from the choices they would make that then go to a different page with questions. Some of the workflows go through multiple pages but each workflow only hits one specific due date question and that’s worked for us in that case. In this particular form, we have like five pages which can lead to 3 different task types and I do have some of the same questions on different pages so you have to really map it out to make sure you’re getting all of the information but not making the user answer the same question more than once but it allows people to go through the process very quickly and cleanly. Please let me know if this works for you.

Florian Kislich

Hi @Tiffany Sands,

your use case sound interesting. I also tried to set up a complex request form to gather all necessary information in one form, and found myself in need to repeat the same questions on different pages.

Maybe you like to support my feature request to be able to use temporary variables within a request form to redirect to different pages: Request Forms: redirecting depending on variables – Wrike Help Center

Florian

Anna Giacobbe

@Kelly St Cyr thank you for making this post. I thought I made a similar one, but turns out I didn't so if I could upvote this 100 times I would!

As MOps in a Marketing team, we are struggling with the exact same thing. A lot of our Marketers are on the road and don't have time to open multiple requests and have asked for a request form with a "menu" of sorts for them to select multiple assets that they need, but most importantly, be able to set different due dates. Cross-tagging also is a concept that a lot of our users struggle with - the ones who aren't in it as much as service teams, for example.

A use case that I'd have is for an event: we may need graphics, event logistics, a landing page, and 3 different emails, but obviously everything has a different due date but we'd want the event dates to be populated on the parent level.

Another would be for any type of campaign, i.e. product launch, where we'd want to incorporate many different assets (with different due dates) in this overall pulsepoint.

The idea you shared is something I have tried to explain/have asked about multiple times in different Wrike-led Marketing-oriented workshops. I would encourage you to sign up to those to share your thoughts with other Marketing peers - there's power in numbers!!

In the meantime, what we are stuck doing and to many people's distaste, is asking them to open a request for their assets separately, and cross-tagging them into one main project for their initiative. This however leaves tons of room for human error, mis-tagging, etc. and is not ideal. Not to mention, it's VERY time-consuming and also frustrates/annoys people, which affects their adoption/usage of Wrike.

I think if Wrike implemented this logic into their request forms, we'd see higher Wrike usage, cleaner projects, and a reduced number of request forms (easier to manage the backend).

Thanks again for sharing this

Tiffany Sands

@Florian Kislich Done! I had been wishing for an option to duplicate question and answer sets it would save a lot of time. As it was I had to have someone else take the time to go through some of our forms to set the actions based on the persons answer for some of them.

@Anna Giacobbe Thank you for the added context and idea!

To give context for the Wrike Team:

Specifically I will use our Creative Request Form as an Example. We need to know how the Creative will be billed and where time will be logged. We have retainers with different departments for each client. So first we have a question asking which department is making the request.

Then we have an action based on their answer here. For each department we created a DB that just list out all of the retainers for every client that has a retainer with them. So after the User chooses the Department they get a Single Answer question that pulls from this DB.

Then for each retainer we set an action to add it to a Parent Folder based on the Retainer chosen. We have well over one hundred Retainers and this needs to be updated every time a new retainer is signed or cancels. This then has to be done on every Internal Request Form we have. This is very time consuming. Being able to save this in one place and just edit it once to update across all forms would be amazing.

Florian Kislich

Hi Tiffany,

thanks four your support! I agree that duplicating questions (or pages) would also be very helpful, but it would still result in much work if something has to be changed after a form was created.

Tiffany Sands

@Florian Kislich Agreed. Being able to save the modules/questions to be reusable would be best.

Basudha Sakshyarika

Makes sense! Thank you @Kelly St Cyr for this post and everyone for your inputs. I have passed this on to our product team for consideration. 👍🏽