Request Form Prefix Building

Hi,

I'm not sure if there's an answer to this question, but let's see what creative solutions are out there. I have a request form that builds the name of the project from the answers to a few questions. This is an important naming convention setup for us. I want the project name as the prefix to my tasks, but I can only use one form question as the prefix.

Does anyone have a workaround or suggestion for accomplishing this?

And a side note, I'd love to have the option to choose the separator for the spaces between the question answers that make the project name. Right now it's space-hypen-space, which takes up a lot of characters. I'd like to be able to choose what separates segments of the name.

Find more posts tagged with

Comments

Pietro Poli

Hi @Steve Mruskovic, at this time you cannot do it by form.
Project name can be created by several fields in form, but for Prefix you need to add a specific question.

You can do what you need by API or Wrike Integrate, triggering the project creation you can take Project Name, manipulate it and then use as PREFIX for all tasks, folders, inside the project.
I've done something similar for my customer with Wrike Integrate.

Mike Fank

@Steve Mruskovic - It sounds like you and I do the same thing. I have a few questions that build the project name, and 1 question that creates the prefix.

Kelsey Rudolph

I've been wanting this to be a feature for some time as well. Unfortunately, since this isn't currently an option, we actually did away with the "request form title building" solution and just have a project title question that has a descriptive helper text on how to name your project and use that question as the prefix for tasks as well. It isn't a perfect solution, but it works best for us.

Steve Mruskovic

Thanks, all. This is what I feared, but expected.
Part of the reason we're switching from one question with detailed instructions to 4 questions building the title is that there was too much variability in the responses no matter how explicitly I explained the naming process. So, having the one question on top of the 4 gets a bit redundant and starts entering into question fatigue territory with my reqesters.
Since tables allow us to show more details, I may just set up a view and only use one part of the title for task prefixes.