Request Form Prefixes for Task or Folder

For Context, Just in case my verbiage is off. I'm 3 days new to Wrike. 

So when I say "task" I might mean "folder", I'm not entirely sure yet. Either way, that 467989...title right below here; that what I would like populated. Don't care too much about the sub-tasks.

Hi Jason Anderson! Are you creating this project from a Blueprint before the request is submitted? 

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

HI Jason Anderson, 

on a multitude of questions in the request form editor you have the option where the answer to that fiel should go, Description, Custom Field or Title. The latter is what you are looking for. Does that help? 

Adding my 2 cents to this question, but a bit disheartened to see it was asked in 2020 and still unresolved.

When creating a task from a request form, how do we get a prefix on a task created automatically in the same or similar way as a blueprint?

Hi Angela Kennewell, it's unfortunately not possible. I'm passing it on to our team.  

Hi Cansu,

Any update on this? This one is causing some frustration for us... and I can't be the only one who thinks it's a bizarre way to apply an option of adding a prefix, not to the item you are explicitly creating via Request Form, but only to imaginary future subtasks?!

For example, as per one of our Request Forms, we ask users to enter Project Code.
And the only thing that works to turn this into a Prefix is to instruct RF to send answer to "Title",

Like - WE - are literally just creating the prefix ourselves in this case!

So effectively, the "add prefix" option does NOTHING if you never create subsequent future subtasks...........

What we need (in our use case) is for users to answer Question; "Enter Project Code".
We instruct RF to populate "Project Number" custom field with answer to this question (needed for use in our reporting).
AND "add prefix" option over there on the sidebar does it's job, putting the answer as a prefix in new task title.

Right now to achieve, users need to enter the data twice, eg. answering "Enter Project Code" <- instructing RF to populate desired CF
...and then we make a second redundant question like "Copy Project Code here to add Task Title Prefix" <- instructing RF to send this second answer to "Title"... certainly not ideal!

Hi Angela Kennewell, thank you for coming back to us. I have good news: recently Wrike has launched a new action in Automation rules called "Change name" that allows you to automatically add prefixes to your new or existing items. Please, let us know if you have any questions on this feature and if this enhancement is sufficient to solve your case 🙂 Thank you!

Hi Juan,

Unfortunately no, this does not solve our issue, as the prefix or suffix that can be added in automation is static, and not able to pull data from a custom field or other source. It's good we can set automation trigger as "when new item is created" but a single static prefix is not what we use. Current automation actions available cannot help us unless it can be set to look to somewhere, like a custom field, for the data.

In our case each project uses a "project code" as a prefix, which consists of a 3-letter abbreviation of project full name, and a 6-digit number, which is of course unique to every project.

We require this code to be a prefix on every folder/task/sub-project created within each project, as we do thousands of projects a year, all fairly similar, so have tens of thousands of same-named tasks etc which would render search useless and dashboards/calendars etc near-useless without prefixes.