[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 Wrike Product Manager Become a Wrike expert with Wrike Discover

Elaine Wrike Team member 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 Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

upvote!

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

Thank you Nan Chen, Pebble Lee! 

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

Please fix this.  I am tired of looking for a solution. :(

This would save me an immense amount of time, especially since I cannot bulk upload projects and only tasks. Seeing as I can convert between folder and project, but not task, I am wondering how much effect this has on the program as a whole. I would love to see this happen but seeing as it looks to be almost 4 years now, I am doubtful. Bumping this in hopes that it can be on the roadmap and, if not, where is the roadmap shared?

Just had to add another comment of dissatisfaction that this key feature is stuck.  Wrike is really holding pat and not actually evolving the product for the way modern teams are working - no Wiki capabilities, relational data or @mentioning of work, improved communication like threads in comments, etc.  All these areas are being rapidly developed by other apps that are passing you guys by.  Thankfully for Wrike, and something that keeps me around here, the fundamental Folder/Project/task structure is so well thought out that you continue to have a unique product just with those basics.  But it continues to be very frustrating on a daily basis to be stuck not having access to all the great functionality you can see other apps building out, that Wrike could easily add.

I cannot understand why this feature, given all the support and dissatisfaction with its absence that is voiced here, simply will not be addressed.  Rose Kilsdonk could not have said it better - the New Experience is of little benefit to me as well, and imagine quite a few others.  It makes the UI look different - hard to say "better", and there is a bit of improved navigation, but you guys remain woefully behind in keyboard shortcuts.  The keyboard combo to get to the search box is a nightmare - "ctrl" key on a Mac?  Where clickup you can click "s" to search tasks, and "k" to search spaces/folders.  These are true improvements to Navigation, and not cosmetic movement of the big "+" sign to add something.

I truly hope you guys will change and start to listen to the voices of Andrew McAllister and others (I'm similarly scaling a smaller company) and be mindful to the dynamic nature of the market and competitors that will start to take away those large enterprise accounts you seem to build around.  It's such a shame that you can't seem to understand that you need to keep up with the market with some basic changes to your aging app.  Your users are seeing these other features elsewhere are are going to be tempted again and again to use them if you continue to refuse to add them into Wrike!

My team starts using Wrike on Monday and we will need to convert tasks into projects at times. Finding the first google result asking for this functionality from 2017 I can not believe it is now 2020 and this functionality is not in place! Upvote from me.

Thank you for sharing your feedback Mary Hess, Al Sape, Judith Frost! I've checked with the team to see if there are any updates on converting tasks into projects, and for now, this is still not planned for the near future, unfortunately. They understand the need for this and they continue to keep this suggestion on their radar. I'm sorry I can't share a different kind of update with you, but I'll also keep bringing up this topic. I or my colleagues will share an update here if there is one in the future. Thank you again for letting us know your feedback even when the status here remains "Not planned". 

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

Coming up on the 4-year anniversary of this request... It's clear that this and plenty other requests are not being considered seriously and receiving the attention they deserve. Our team has already begun the transition to another platform that fits our needs better and at about half the price for our small team. There is plenty to like about Wrike, but there is too much to frustrate as well. Making changes that no one wants, feature 'upgrades' that make the user experience more difficult, and lack of real improvements based on user feedback all just compound to drive us towards other solutions. The new platform we are moving to isn't perfect by any means either, but the considerable cost savings makes that a much easier pill to swallow. 

Hi Phillip Adams,

I can appreciate that it's frustrating when a feature you've requested is not planned, especially when it's a request that has been on the radar for some time. 

As outlined in one of my previous comments above, we prioritize the roll-out of new features and updates after researching and referring to the feedback received throughout our various channels, and although we'd love to be able to implement all of the suggestions made by our users, unfortunately, isn't possible. I have passed on your feedback to our Product team and we appreciate your insight here, thank you for sharing.

I'm sorry to hear you're currently planning a transition to another platform. If there is anything else we can do to help here, or if you'd like to discuss this further, please do let us know. 

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

Elaine Wrike Team member Become a Wrike expert with Wrike Discover

Extremely well said Phillip Adams!  My team is in a similar situation, but finding Wrike's fundamentals still helpful enough that we are coming back after a break.  Sadly, it seems the same broken record responses are being given on key, years-old requests in here that Wrike simply refuses to address, in most cases with no reason other than "sorry we can't prioritize them."  As I've said many times and will not be bashful about repeating, that is disrespectful to most of the users in here, many of which also develop software.  It's one thing to have other priorities, it's another to let requests pile up, receive good feedback with quality use cases, being written by folks like us who don't have time to provide this to Wrike, and still have it essentially ignored.  There are maybe 2 good, legitimate instances in this entire forum where I've seen an actual engineering-based response in here by somebody who is actually developing Wrike, and in those cases the questions that ensued were ignored anyway!

I continue to hope for some reform in the way Wrike approaches feature prioritization.  You are so right in that we get mostly shallow enhancements, many of which in fact seem to indicate that the decision makers at Wrike are building based off personal conviction about what the user "should need," and not actual assimilated user feedback, testing, etc.  Many upgrades actually degrade the experience.  Such as the removal lately of "request an update," a half-complete feature that had potential if it was built out to include that request in the Stream, etc. per this discussion:

https://help.wrike.com/hc/en-us/community/posts/115001496505-Feature-Request-Add-Status-Requests-Task-History-

but now somebody decided the feature isn't worth having and it's gone!  Is that because it wasn't being used?  Well, that's probably because it was incomplete as users were requesting this key addition to it!  

Regarding this request, as teams evolve in tools like Wrike and seek to centralize information, you will have more and more creative uses of the atomic data type in Wrike - Tasks.  It's the way of the future - just look at the likes of Notion, ClickUp, Roam Research, etc. that allow full manipulation at the atomic level.  If Wrike decides that Tasks are going to continue to remain siloed, so you can't convert them to Projects, or do things like relate them to other tasks per this request https://help.wrike.com/hc/en-us/community/posts/115003384329-Feature-Request-Automatically-add-task-references-to-comment-stream-of-referenced-tasks Wrike will lag further and further behind other tools that are becoming more useful.  I am back due to the strong flexibility of Wrike with multi-homing across all entities, as well as the distinct notion of a "Project," which is surprisingly absent among a lot of the competition.  But I remain eager to move back off if another tool emulates what Wrike can offer, strictly because it is so frustrating to see the product development at Wrike summarily disregard most of the key requests in this forum!

I would like to add another +1 to this request. I have a large amount of tasks with subtasks that I would like to convert to projects with tasks. Alternatively, I have created duplicate project titles from the task and retagged the subtask to the project. The problem is, even after I delete the original task after moving the subtask the ghost tags remain from the original deleted task. 

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

Elaine Wrike Team member Become a Wrike expert with Wrike Discover

Hi Elaine,

My two cents to add here, is that this is just as much an issue with comms and engagement as it is about the actual functionality (even though highly sought after)

Wrike have created a mechanism for their users to submit feedback and their vote as to what they see as the most important items to be developed by Wrike. I.E the voting system. This request for functionality is currently sitting as the 2nd most voted for item across the whole product feedback category. Voting is a priority system, highest votes spells "winner" in general day-to-day life.

It's all fair and well to explain that not all ideas will be implemented etc., as a dev issue, cue of work, capability etc. I understand the practicality of the matter. But as long as you have one of the most voted for pieces of functionality sitting there, whilst delivering other functionality that doesn't register for a number of users, your users will get frustrated because they feel like they are not being listened to, and you are basically feeding that narrative. Bill Vincent nails it in expalining a practical way of dealing with the explanation: be honest. Your community is pretty tech savvy, I wouldn't ignore that with your communication to them.

Nothing is going to change, until something changes. To close this loop you need to create the functionality, close the request as being unachievable, or create a new system to supercede this one, as it is not working for your community and is only really breeding more negative discourse toward the community's view of Wrike and their demonstration of customer service/experience. If highest votes doesn't equal highest priority for Wrike, bite the bullet and get rid of the voting system so that the community can have their expectations managed honestly.