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

Hi again, everyone! The status isn't updated currently, but I'll keep checking with the team and passing your feedback - it's clear how important it is to so many of our Community members. 

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 am about to spend a few hours this week doing just this the long way - Updating many tasks to projects.  There should be the ability to reassign type across the board.  Especially since the difference between a folder and project aren't the clearest for all users.

Having started using Wrike in Jan 2019 I quickly imported three years of historical projects into Wrike as tasks... hoorray! - however its crazy that I have to search through them in one way and then search through all my 2019 projects another - because they are projects!

I need to be able to select all tasks (projects) in a folder (e.g 2018) and convert to projects so they are part of any search I undertake for historical projects.

The worrying thing is that this thread is over two years old now!

Why oh why is this not a feature and why is it on the backburner?! We need this NOW! Very time-consuming to have to manually recreate tasks into projects.

Seriously. There are so many features we don’t use and I’d dare say Wrike over engineered for how they thought/hoped people would use their tool, yet this languishes and would benefit everyone. User responsive design, it really is an important concept. I’d ask that the good folks at Wrike, when this comes up, please have an exec read this thread. I assume the engineering behind this is significant and I get that - but this is a black eye on a good tool and worse, makes Wrike as a company seem unresponsive which is unfortunate.

Another +1 for this. This functionality is important for us too!

Just got bit by this again today. We were working on something that seemed unlike a project in its nature, but then our guy decided he wants to create tasks that link to this work but can't because we didn't start the original work as a project. This happens all the time. 

It's painful even reading this thread now. So many comments, so little action. Wrike - this is losing you customers.

I appreciate this may not be any easy thing to fix, but leaving it alone will not make it any easier, and will not make it go away.

After using Wrike for just 10 minutes I encountered this limitation, Googled around for a solution, and ended up here. The inability to turn tasks into projects is a big turn off for me. Consider me another frustrated user!

Hi everyone! I'm really sorry to hear you're disappointed! If we could, we'd love to implement a lot of the suggestions from this forum. The team are working on some of them, and will definitely consider (or are already considering) implementing more suggestions if they fit into their vision. Here's more info on what happens with your feedback: https://help.wrike.com/hc/en-us/community/posts/360019106654--Read-Me-What-happens-with-Product-Feedback-

I know it's not a solution to what we are talking about here, but I really want you to know that your inputs here don't go unnoticed for sure.

I totally understand where you're coming from with this, and I'll keep passing on your feedback. 

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

Thanks, Lisa. I think most of us appreciate this stuff is never simple and changes that impact the underlying architecture of the system are particularly challenging. I am hoping some out-of-the-box thinking might get a solution that would work for everyone. Thanks again. 

Let's be honest here. This thread is THREE YEARS OLD. Lisa, with all due respect, you are here only to placate us. Please don't tell us that Wrike is serious about wanting to do what users want/need when this thread is three years old and almost EVERYONE on this thread has said this issue is a MAJOR issue and should have been addressed LONG AGO. Wrike is ignoring this issue, and doing it at their peril - because many will go elsewhere where they feel they are being listened to. I certainly don't feel you are listening, nor is your company doing the right thing here by coming into this very thread every blue moon and saying that you "care" about our needs when it is obvious that they don't. That just angers the rest of us even more who have been waiting for (in my case almost two years) for this to be implemented. 

Maybe it takes a post like this to get Wrike's attention in a real way. But don't tell us you are listening when you obviously are NOT. Your product is forcing people to do things YOUR WAY, when the whole purpose of Wrike is to be able to design a workflow database solution that makes workflow easier, not adding more work for everyone! 

Seriously - get it together, quit making lame excuses and placating us with periodic posts saying you are "listening to your customers" and FIX THIS.

Well said. 

And I follow other threads.... with the same results. I'll be leaving Wrike. 

Lisa Hey Lisa, I just saw this post of yours at the end of this thread:

https://help.wrike.com/hc/en-us/community/posts/360015641334-Convert-Task-to-Project

You referenced this thread and said it has now "coming soon," at least that's how I interpreted what you wrote.  But this is still on "backburner."  Getting this done may potentially get me back to Wrike, as I still have 1/2 year on my license.  But otherwise I agree with the sentiments here, and many places elsewhere, that you guys don't really prioritize based on user requests.  My tone has gone sour since I started in the community with enthusiasm for that reason.  Your weekly releases seem to come out of nowhere - you never reference in Hugh's posts over there ANYTHING out of the community!!

If you guys do have this on the docket, would still like to hear about it.

Oh and Bill Vincent wanted to applaud you on your post.  I agree 100% and really hope this sentiment will get the attention of the higher-ups at Wrike, as fundamentally it's a great tool but some key features are out and out ignored, like this one.  I don't really understand how the other stuff that comes out in the Release Notes is determined, because you don't see anybody voting for most of that, while this and a bunch of other stuff is not addressed!  We are all taking our precious time to voice sentiment, provide use cases, but we just get responses from the moderators in here that "sorry, not now, and we won't tell you what our real priorities are but they aren't yours" in so many words.

This needs to be implemented and it's a travesty Wrike hasn't done it yet.

Hey everyone, thank you for all of your feedback here. 

I understand how frustrating it can be that this has not been implemented in to the product yet. We appreciate all of your feedback, and rest assured that all of it is passed on to the Product team. The team is interested in this idea, but it is currently not on the short-term roadmap. I'm sorry that you are disappointed at this current status, but as soon as I have any news for you, I'll be sure to let you know as soon as I can.

I would recommend continuing to provide us with feedback, votes, and use cases. They are invaluable to the team as they have discussions around future updates to the Product Roadmap.

Thanks again for your input here, and if you have any questions, let me know.

@... OP here. It's been over three years since this idea was created. While we've made do up to this point, out team have been seriously looking at other project and task management solutions - alternatives to Wrike. 

At this point, you do NOT need more input, votes, or use cases. I'm pretty sure the community has done their job sufficiently in providing you enough use cases and ideas to develop your framework. They've also clearly asserted their desire for this feature. 

Your reports do nothing to satiate your users - paying subscribers. You have provided no reason as to why this isn't on the roadmap. It's clearly important enough to your users that it should at least be in some sort of active research and development. I would have more patience and understanding if we were given more information. The Product Team has a reason for not adding this on their timeline. What is that reason?

Please, do yourself a favor and provide more transparency into your process. As others, and I, have observed, Wrike continues to release updates and feature 'improvements' that haven't been anywhere in the community request section. So it appears as though Wrike has their own utopian agenda that doesn't necessarily line up with their users needs. When new features pop up that no one was asking for, we are forced to ask, why? Why this instead of the thing that's been sitting out here for three years with hundreds of backing votes and one of the lengthiest discussion boards in the entire community?

This is a call to action for Wrike. Please, hear the voices of your users. Don't patronize us with a "thank you" and "we hear you." It's time to move forward and make this happen.

Thank you.

Echoing what Phillip Adams just said, and I see two possible explanations. One: Wrike doesn't care what we want/need from a product. In that case stop wasting our time asking us to "provide you with feedback, votes, and use cases". Two: Wrike was built with a very narrow use case in mind and is too inflexible/expensive to support this (very basic) use case. If so, admit it so we can all move on.   

Wrike did attempt to implement this thread back in 2018-2019. This thread had the "Investigating" status starting on August 06, 2018, then went to "Backburner" on April 15, 2019 from a comment by project manager Arkadiy Rushkevich. Arkadiy mentioned that there was other work to be done before they could re-visit this thread. 

Hugh, has the product team been keeping threads like this in mind to work towards even if they aren't on the short-term roadmap? I understand projects can be very complex and require other tangential features and changes first, but if they aren't making (other) changes with this thread in mind for the mid-to-far future, they're working away from it, not towards it.

I agree with Ellen - a simple “it’s not gonna happen so work around accordingly” would be a better strategy then letting this linger and eroding people’s trust.

I have been vocal in here and in some other similarly ignored, but equally of huge importance, posts.  Joshua Balentine very astute, I also watched with huge disappointment as this moved ahead, then reverted last year.  It was nice to get the Arkadiy's input, but if you look at this whole thread, and see that the only time anybody bothered to get in here and explain anything was that one time, it's really an insult to the community's intelligence - to echo a fellow user's sentiments.  

I actually think given the continuation of the neglect of these requests that @... and Lisa are actual victims in this whole situation.  Clearly some supervisor has told them to state the same canned response in so many words again and again, and whoever is really making these decisions within Wrike has zero regard for lining up the roadmap with the actual needs of the users.  You guys actually do a good job with your weekly release notes - few other competitors are that systematic.  But it has absolutely no tie-in to this community, aka actual Feature Requests!  

Phillip Adams agree wholeheartedly with your comment as well, spot on.  I have been back in Wrike the last two weeks, trying to make it work after giving up some months after my license started, but the lack of this feature, and several more like https://help.wrike.com/hc/en-us/community/posts/115002373265--Status-Investigating-Shorter-Job-Numbers-or-shortlinks (equal dissatisfaction on a post with 112 votes) have blocked me, and I'm on the fence as to whether to keep going.  The Decision Makers at Wrike can keep this policy going at their folly - it will cost customers to other, more agile and lean apps who actually listen to customer feedback, and when they do get feedback, something very valued by all software makers, they respond and show those who provide it some appreciation!  Wrike's policy appears to be the exact opposite!

I just want to add here, and this may be known to many of the 229 (!!) voters of this feature, that Asana, arguably Wrike’s biggest competitor, has this feature well built out, making it all the more conspicuously lacking here in Wrike.  

Asana is a tool with a mass of tech debt and iterating arguably slower moving than Wrike with releasing new features- at any rate, not quickly.  Took them forever to come out with the ability to change from “List” to “Board” view, or have a start date on a task.  That is some basic stuff.  But whatever the reason Wrike is stalling on this, and fully agree with Julie Tilke - this problem is not going away.  There are more and more flexible solutions out there - see Coda, Notion, ClickUp, ZenKit, Monday, etc. that were not around when this thread was started.  Wrike can either show us that it’s taking this seriously by actually providing a response of substance, or let us find the solution - and those tools and others have many, many more things that Wrike is lacking - in another tool.  The market is getting swamped, and tools that recognize basic Agile & Lean ways of building - in other words, you listen and respond to and respect user feedback - will win in the end.

Thanks for the status update.

I wish Wrike would provide more context as to why such a popular request is not perceived as an urgently necessary product improvement.  Its concerning/frustrating to watch much less requested product improvements come to fruition while this one seems to be actively ignored.

Hi Matt Aldridge, thank you for this feedback. It's been passed on to the Product team.

Yes!  Another vote for task to project.  This comes up all the time as an issue that causes friction (and friction hinders adoption).

Does anyone besides me find it highly ironic that the company whose entire business is to make project management easier cannot do this one thing that they have been told for over three years would make their client's project management easier? No excuses, Wrike. Do your job already.

+100

Julie DeLoyd and Bill Vincent  Glad to see the continued pressure on Wrike to get this done, maybe finally somebody will take notice!  This  is probably at the top of my list of missing features and why I am unlikely to renew Wrike,   I, and many others have said that before, but stubbornly nobody with any pull around this bothers to weigh in here.  Among other problems, there is no way to do seamless Idea Management in Wrike without this.  But probably more scathingly, Asana handles this terrifically.  That’s Wrike’s chief rival, and I’m sure they’ve siphoned off a great many users who could have otherwise stuck with Wrike if this feature was in place.

Yep, same here. How can this not work in wrike? It does in Asana. Just sayin'