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

Hi Jonathon Burrows, 

Elaine Community Team at Wrike Wrike Product Manager Узнайте о самых популярных функциях Wrike и советах по его использованию

Elaine Wrike Team member Узнайте о самых популярных функциях Wrike и советах по его использованию

I would also want to express my need for this feature. I'm currently migrating 100s of tasks to rectify a mistake made while setting up a project / task structure. The tasks now need to be assigned to the workspace and be converted to projects manually. It would save a lot of time if this feature would be available.

I have to admit that this could be prevented if we started with the correct structure to begin with.

I would like to bring this topic up again. It's scary that it has been sitting here fore 3 years. It's incredibly time-consuming to convert existing tasks to projects/folders. Please work on this feature! Thanks!

Anna Grigoryan Community Team at Wrike Wrike Product Manager Узнайте о самых популярных функциях Wrike и советах по его использованию

Anna Grigoryan Wrike Team member Узнайте о самых популярных функциях Wrike и советах по его использованию

I can't believe that there is still not a functionality to convert a task into a project yet.

It seems that Wrike may have listened to those of us calling out on the regular mods in here rehashing the same lip service messages of "great!  Thanks for the comment..and we have nothing to offer in the way of actually addressing these requests" and thinks that a PM coming in here, I'm looking at you Anna Grigoryan, saying the exact same thing in so many words, is going to appease myself and fellow, legitimate, paying users, users who are taking their own valuable time to come in here and provide very relevant feedback, use cases, even asking legit technical questions re: what is blocking this.  It is uncanny the degree to which you insult the intelligence of your users Wrike!

All you have to do is read just one page back here looking at the very succinct commentary from my colleagues Joey Horst, the author Phillip Adams most recent post one page ago, Jonathon Burrows, Bill Vincent, Rose Kilsdonk, and the ignoring of Mary Hess saying what is said in the forum daily - where is the roadmap shared?  And I don't mean a link to your same tired old post about "the product feedback" section, but what you guys actually are working on?!  I read fairly religiously your Weekly Release Notes, and maybe 1 of 30 of the items in there I can trace back to this forum.  So who does the prioritization?!  So much for working in an Agile or Lean manner, where you actually are supposed to factor in User Request.

Wrike has some truly unique features, so after not renewing my license, I evaluated again the last month, and - I'm not coming back.  The lack of this feature, code snippets in Task Descriptions, editable closed date, subtasks in boards, etc. etc., and seeing no movement on any of them since I first came to Wrike in 2018 - while entire new tools like Clickup and Clubhouse.io have come into existence and developed tons faster - is a big reason I'm not coming back.  And speaking of ClickUp, many of us watch their very TRANSPARENT feature board, and I could not imagine in the slightest hearing from one of their PM's that a #2 request is just "quite complex and requiring more investment than is possible at the moment."  I'm sure ClickUp is eating you guys for lunch, and you better hope your strategy of sucking in Enterprise accounts with 100's of users who are too bloated to organize an evaluation of more effective, cost-efficient, agile-moving tools works.  Because years are going by and you guys are getting passed by the minute.  And if you think a dinosaur of Citrix is going to help, just have a look at how well regarded their Podio suite is these days.  Talk about an enterprise software company from the dark ages...remember GoToMeeting?  How many of those users are still not on Zoom?

After seeing the stalling, obfuscating, and finally the outright denial of the Wrike team for 3+ years to do anything regarding this feature request, I can only assume that the following scenario (or something very similar) has played out here:

 - The original dev team is long gone, replaced by cheaper maintenance developers who do only minor cosmetic changes designed to make the product appear as tho it has been updated when in fact no changes to the actual architecture have been made or attempted.

 - The original dev team was never contracted for upgrades over a period of years - which now means that Wrike would have to basically pay them whatever they asked for to come back to Wrike for an unspecified amount of time/effort in order to make significant structural changes to the software architecture.

 - Wrike in it's current form did not write or have anything to do with the original rollout of this product, possibly bought or inherited from another company or third party.

It is painfully obvious that at this point, this request would cost them money. It always comes down to money and resources. Money they do not want to spend, or resources they do not want to devote. If they could have done this without spending money or using significant resources, they would have done it long before this. So, if what I'm saying is even partially true, Wrike is between a rock and a very hard place, and chooses to do nothing.

I'm no Nostradamus, but it doesn't take a genius to deduce the above scenario, or something close. And even if my predictions are not accurate, it's still no excuse. This feature request being ignored for SO LONG after SO MANY have asked is nothing but a conscious decision on Wrike's part to not invest in having this work done. In other words, THEY DON'T CARE. They just don't, and any attempt to "soften the blow" by having everyone but the CEO come in here and give us the same tired BS about how they really do care is just that - BS. 

So, HERE I AM, WRIKE. PROVE ME AND THE HUNDREDS OF OTHERS ON THIS FORUM TOPIC WRONG. PROVE TO US THAT YOU ARE WILLING TO FIX WHAT IS OBVIOUSLY A HUGE DESIGN FLAW THAT YOU NEVER BOTHERED TO DEAL WITH (for whatever reason!). Otherwise, this entire topic serves as a testament to how Wrike does NOT care, right down to the latest load of excuses and avoidance posted by the PM which gave absolutely no answers at all to why this has not become a priority and not been fixed.

It’s uncanny how similar the frustration is here just like it is over in the Asana feedback forums.

Every one of these tools is getting outclassed by Clickup by the second. I’ve been evaluating Wrike as an alternative to Asana but it’s posts like these that immediately make me say, “Well, they’re still just not a viable solution yet.”

It would seem to be that "our second most popular suggestion" and "Been our radar for a while now should be incompatible statements.

I think the community would like to see a top 10 dashboard with roadmap and progress details. Shouldn't be hard to detail and share.

Great to get all this solidarity, and of course, Wrike doesn't care!

Skyler Reeves great point, but at least in Asana you can convert a task into a Project!!  I don't know which board is more littered with key feature requests ignored though - Wrike or Asana's.  Somebody should do a case study.  It's not just ClickUp outclassing them - they are losing out to Monday, Hive, even the likes of Notion, Clubhouse.io, etc etc.  Once the enterprise customers using each tool start to realize they can move to cheaper, better solutions that let their teams work much better - or, those tools start to target enterprise contracts - Wrike and Asana will have their hands full.  Airtable it turns out has many, many $100k/year contracts, and has grown much faster than both...

Elaine Community Team at Wrike Wrike Product Manager Узнайте о самых популярных функциях Wrike и советах по его использованию

Elaine Wrike Team member Узнайте о самых популярных функциях Wrike и советах по его использованию