[Status: Not planned] Convert a Task into a Project

Just got bit by this again this week. had to re-do a lot of work to make tasks into projects. then realized things like effort can't be set at the project but at task. The whole underpinning of task v project, when the UI allows so much flexibility is a really miss by Wrike. I like the tool and this is not a deal-breaker but it is a real shame.

Michelle Hartwell yes that's a big reason to get this done, it's a cornerstone of Asana and conspicuously missing here in Wrike.  288 votes and counting how much support does this need to get movement??

Found a reference to this as "coming soon" on another thread and hopped on over. It's disappointing to see the status has since reverted, and the feature will require so much more work to implement. Count me among those looking forward to this as soon as possible.

This seems like a major omission. This feature would add so much value.

Really want the functionality for task --> project and project --> task. This would be ESPECIALLY helpful when a team utilizes the Wrike Request Forms. When you use the request form, you get the choice of create a task or a project. But, what if after a request is made, you determine that it needs to be the other of what i set as default upon submission. Is this a roadmap item? 

I work for a software development company, and I have to say this is one of the worst software enhancement request procedures I've seen. I understand that there may be hundreds of requests that come in a year, maybe even thousands, and you can do them all. But items sitting out there for YEARS is crazy!!! Especially when it has so much support and makes sense to make a change. Wrike seems to provide all the bells and whistles on the surface, it just seems you all forgot the whistles on some of the functionality.

Our teams could also really do with this functionality. With onboarding new teams, it's very easy to create a task instead of a project by mistake. The work around to turn the task into a project is a real pain, and is becoming a significant challenge for us to get people comfortable in the tool. 

I'm currently trialing this tool to see if it'll be a good fit for our team on the Marketer's Performance Plan. After reviewing this thread, I will be reconsidering this. Not so much that I care about the feature but I am wary of investing my money in a company that takes so long to iterate. 

Skyler Reeves I dropped my Wrike license just for the reasons you cite, and in the other post re: the Product Roadmap.  I am still following this and some other requests that were of great interest to me, and literally got zero movement from Wrike.  ClickUp a great example of a proper roadmap approach.

I agree this is a good reason to avoid Wrike.  As a related point, you'll be lucky to see anybody from Wrike respond to these more problematic posts for months, and when they do, it's a canned response of "we'll pass to the product team."  What Product Team?  Don't they read this for themselves?  And it doesn't speak highly of Wrike as an organization that their own users slam them here right and left, and they don't even bother to respond.  Can you imagine how many times people Google this stuff, only to get this page coming up with a scathing review of Wrike, and Wrike itself is publishing that content?!

I wish you the best in your hunt for a tool.  Have you looked at Fibery?  Primitive, but also has a routine release cadence so you at least know what they are coming out with...

Elaine Community Team at Wrike Become a Wrike expert with Wrike Discover

I can appreciate that there are different teams working on various UX aspect of the system - but I sure would have taken the ability to convert a task into a project (an existing experience) over the New Experience rollout. The short notice of the New Experience rollout and the lack of attention to this item are both disappointing. 

Hi All,

Any update here? Currently trying to do this as well. 

Here's an idea for Wrike

Include "create a new project" option into the automation options.

Have an automation option to populate the new project using the attributes of the existing task (description, custom field values etc.) which would be a handy vairable for tasks as well FYI, to be able to pick and choose existing task values.

Using a change to status as the trigger. For instance creating a status in a custom workflow "Create project" which would be used as the trigger. Possibly then being able to automate moving the task into the new project created.

Therefore you don't have to "convert" the task to a project, which I'm guessing is what Wrike cannot figure out how to do. Instead you just create a project using all of the info/attributes from the task. There is the ability to link forms to task creation (creating a new project from a form would also be great), that's really where the idea came from, that and starting to play with the automation.

@jonathon Burrows - that was genius. Problem solved.

Hi everyone!

Rose Kilsdonk I'm sorry to hear you're disappointed! Please note that even though the New Wrike Experience is being rolled-out now, a sunset phase is planned, because the team understands that it might take some time to adjust your processes.

David Hice As Elaine mentioned above, there are no updates currently in terms of the status change. 

Jonathon Burrows John Gieschen Thanks a lot for your idea, passing it on to the team now 👍

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

upvote!

I would also like to add in my vote to this. This is very essential.