[Status: Backburner ⏳] Auto assign requester when making task via request form

Hi there! :) Thanks for taking the time to post this request on the Community after discussing it with our team, I really appreciate it! In case it helps anyone else, I wanted to share what Dina from the Support Team mentioned about Request assignments: If the requester is a member of the Wrike account and is submitting an internal Request, then the requester is shared on the resulting task. Hence although the requester would not be assigned to the task, they will be able to see it and collaborate on it straight away. They will also be able to assign to themselves after the Request has been submitted if the user is not a collaborator.

Hi there,

I have something similar whereby I need to auto assign all tasks within a project created via the request form. I can specify the owner of the Project so this is automatic when the form is submitted but not the owner of the tasks within a Project. Are there any plans to automate this step?

Thanks,

Stuart

We also want this feature.  We want to do some task automation for approvals and need to know the email addy of the user who submitted the task.

This would be useful for me as well. We have internal requests that require an initial task by a static assignee other than the requestor, but then subsequent follow-up tasks to be assigned to the requestor themselves

Up vote here! I use request forms for vacation requests and such. I want the requestor to be assigned it!

We need this or a function to create a report of requests made by a particular user. We use internal request forms a lot and people want to check up on the status of their requests and then can't find them. We use a workaround of creating a x's requests labels so that the requests can be tagged into one folder but a more direct functionality would be much better.

This function will be really helpfull for the requester to follow-up the request !

What is the status ?

Double Thumbs up here! If you're following this and haven't hit the plus button on the wrike page, it wont get promoted to higher priority. So, please do!

I know that *some* forms are allowed to be anonymous, and *some* are public (which means you won't have a user to assign it to), so in order to implement this, I'd love one of the question-type options to be 'select a user' in a dropdown. Then this list would be dynamic (not manually managed) and I can set the assignee to the value selected.

Right now I create a dropdown question, manually type in users 'text' names as choices and then branch the task assignee to each selection. This means I have to manually update the form when we add/change users.

In either scenario above, the requestor has to actually choose themselves from a dropdown which is complete double work when (if filling out the form from the app) the app knows already who is logged in and filling it out. So the other way to implement would just be a form setting to always assign to the requested (if logged in).

We have a similar use case and just need Blueprints to be aware of who the Requester is so that they can dynamically become the Assignee of Tasks in the Blueprint.

I have a Request Form that creates a bunch of tasks based on a Blueprint when it's submitted.

Some of the tasks get assigned to someone in the function that serves this requesting user, but I'd like to assign some to the Requester themselves (dynamically in the case of each requester).

I haven't found a way to set that up such that whomever is the "Requester" becomes the Assignee of particular auto-generated tasks. Is that possible?

There are so many other dynamic data points available from a Request now (thank you), that I thought this one would be a no-brainer!

We use a form to create meeting minutes.  We need to auto assign the task to the user that created it so they don't forget to add themselves as assigned.  This would help prevent accidents where no one is assigned and it goes into a black hole for follow through.

A workaround is possible if you have Wrike Integrate.

I posted a community recipe at https://www.workato.com/recipes/1088366 that demonstrates a way to automatically assign new tasks to the task creator.

This example recipe requires a Wrike custom field to distinguish between new and updated tasks, so this approach requires either Wrike Business or Wrike Enterprise, in addition to Wrike Integrate.

An alternative approach using Wrike Integrate that doesn't require custom fields (great idea suggested by Admin Bot at https://help.wrike.com/hc/en-us/community/posts/360037787073) would be to tag the task to a specific folder instead of using a custom field, and loop through the parent folders looking for that known folder in order to determine whether the task is new or has already been processed.

Hey everyone, these are some great workarounds! Thanks for all of your input on this, it really helps our Product team when they discuss suggestions like these 😊

I don't have an update at the moment, but I'll keep you posted as soon as I do!

We also have this request in our business. I'd like to share scenarios that come up with us:

• Structured sharing of information & task management between internal teams:
• Request form is tool to initially create a task according to a pre-defined set of steps and drop-down menus
• Current situation: Created task can be complete or needs additional information, in both cases, the requester is part of the task and should follow-up, and thus should be assigned automatically.
• Risk: For the requester it’s not straight-forward how to find the created task, he can look into “created by”, but auto-assigning would cut down the steps needed to take and also the risk of “fire and forget” (requester shoots off request form, but then does not follow up on assigning himself and any action / follow-up by requester falls by the wayside)
• Sharing of files between internal teams:
• Similar to the scenario above, but including files sharing
• Current situation: Often the task gets created with one or some initial documents which need to be adjusted or more files uploaded later.
• Risk: If the requester does “fire & forget”, this follow-up / adding additional files might be forgotten. Same risk as above: missing information / files, incomplete tasks, “lost” tasks, collaboration in jeopardy, more manual steps and greater effort for everybody involved
• Manually assigning a standard project and all included tasks on the basis of Blueprints
• Requester creates a project from Blueprints, with sub-projects, tasks and sub-tasks
• Current situation: They have the mass-editing function, but still need to click trough all the tasks and sub-tasks, which adds additional & manual steps that might be incomplete (human error)
• Risk: Effort & manual handling required that has a risk of missing steps, and adds additional work for the requester which is not useful

This product feature would cut down manual steps, reduce risks and generally contribute to work management and collaboration in a large enterprise where distributed teams work together on complex projects and tasks.

This seems like such an obvious feature. I'm surprised it has not been added in to Wrike yet.

Hi Christina Fischer and Shawn Flanagan, thank you for these use cases and feedback! It's all been passed on to the Product team.

I agree with Christina. Currently you can manually create a project from Blueprint and manually place the project (with tasks and sub-tasks) as well as manually assign the project and tasks to owners. In one of our business uses, and the largest of our implementations, the same person is assigned throughout the entire project. It would eliminate manual steps in our business if a user can determine the location of the project and who to assign the project and tasks to within the request would eliminate many inefficiencies for us. This includes all the manual touch points by multiple people and timeliness. 

@... Hello! 😀
This feedback has reached well over 60 votes. Would it be possible to get an updated status assigned to it? Thank you

Perhaps it's going to be taken into account with the new "Automation" product?

Hey everyone,

Thank you for all of your feedback and use cases here, they've been passed on to the Product team. As this post has reached 60 upvotes, the team has provided a status update for this suggestion.

The team is interested in this suggestion, but due to other priorities, there are no plans to add this to the short-term roadmap. They've provided this thread with the "Backburner" status. I'll be sure to keep you posted on any new information or updates in relation to this idea. 

If you need anything else, feel free to reach out to me at any time.

I understand everything cannot be a priority, but this is such a crucial feature that I hope you can fit this into the roadmap sooner rather than later.

Thank you for weighing in, Jen! We'll make sure to continue to bring this up with the team.  

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

An update to a solution suggested by Marj Downey on this other related thread. I noticed working on an internal request form for task creation today that "user" is a question type now. So you don't have to manually map checkbox/dropdown options w/ an action to assign an individual (or multiple) users.

You can add this user question type, as required, then select "Assignee" instead of "Title" or "Description" for the field the answer will to be written to. This produces a question that looks something like this in the working request form:

Although it's not an automated solution—requiring the requestors to select themselves—it accomplishes what we needed in our particular case without being too much of a hindrance/barrier.

Thanks a lot for sharing Katie Wilborn! 🙌 

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

+1 to add the ability to automatically add the requestor to the task or project.

Hi Josh Bennett, welcome to the Community! 🤗

Thank you for supporting this suggestion! I hope that the workaround that Katie shared above can help you in the meantime! 

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

This really should be a crucial feature - can you please provide an update on this?

Hi Niall O'Flynn, welcome to the Community 👋

Thanks for supporting this suggestion. I don't have an update here as this isn't on the team's short-term plans for now. I'll let you know here if that changes in the future.

If you'd like to know what this Community has to offer, please check out our New to Community forum.

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

I have been able to figure out a workaround that actually does this exact process... utilizing the blueprints I was able to create the subtask with assignee's... then in my request form utilizing the checkbox option, I was able to assign subtask on the specific answer I want the subtask I created in the blueprints to be assigned to and select blueprint and attach it that way... one the request form is submitted the individuals who have received a task are automatically assigned to the main task via a subtask, this helped eliminate one employee closing the entire task when they had completed their portion and another employee had not... also eliminated the everyone receiving the task and notification(s) when they were not assigned a task; improved efficiency as well! this is an effective work around for this issue. 

Hi Remie Martinez, welcome to the Community 👋

Thanks so much for sharing your workaround 🤗

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

While there is a workaround, this function is desperately in need.  The workaround requires that the form-filler fills out the form properly - which is not a guarantee.  With constantly changing users/roles/groups, this lack of functionality is essentially nullifying the proper use of Wrike Request Forms overall.  The Request form feature is plagued with manual upkeep outside of this capability, like requiring manual updates when custom fields are used.