Thank you for your feedback!
Now other members can find, vote, and discuss your idea.
Our Community Team reads every suggestion (yes, every one) then compiles and shares the feedback with our Product Team. Happy posting!More about Product Feedback
Folllowing List for Post: [Status: Not planned] Convert a Task into a Project
[this list is visible for admins and agents only]
Must get this feature! It is a major source of product frustration-😕
At least 4 reasons:
I appreciate that during discovery, the dev team realized this is not so easy an effort, but this is really, *really* a critical need. I often create a project that is really a program, so I can get the whole scope timelined out, and when it comes time to fill out the details, instead of converting a task into a project, I create subtasks in a task - this does not allow me to accurately report out designer assignments and workloads.
I strongly encourage the dev team to carve out an allocation to investigate and solve this problem. Your competitors have this solution - you should have it too. Thanks for listening.
I thought it should be already done by the very beginning but... Often a single event (customer issue, bug, sales team insight) can initiate a task that is growing then like a snowball and you have to treat it as a project. That would be a very useful feature!
Also want to levy a huge +1 on on this. Wrike has great flexibility, and being able to use tasks as things like "ideas," "talking points," "Decisions" etc. is very useful. With the app and other ways to quickly enter ideas into Wrike as tasks, it then becomes paramount to be able to transition these into projects and work items.
Aha, a Product Management tool that I passed on in favor of Wrike, because I think Wrike can handle a lot of what Aha is trying to do, has a feature for the users to create "ideas" and then actually promote to features and releases, all the while saving some visilibility: The original "idea" is marked as "closed, converted" and the new Feature picks up a link to the original. Here is a link talking about it:
It would be terrific if with this feature you would also have an option to change the status of the task once it becomes a project, and then in the new project have info back to the task. For now, I am doing this manually as a workaround, an example:
- I have an idea called "Allow my website user to post on my forum under a pseudonym, not real name." I enter it in Wrike. I create a folder called "ideas" and put the task there. I put the status of the task to "under consideration"
- I create a meeting task (also a special type of task I use tagged "meetings") and pull in the task as a subtask. This way there is visibility on the task that it was discussed in that meeting. We decide to investigate further this week. I note that in the meeting task's description, and move the status to "discovery" in my unique workflow for the "ideas" folder
- We then decide to roll out on this feature. I move the idea task to "accepted" which is a closed status. I then create a new project called "Build ability for user to post in Forum with pseudonym." In the project description, I link to the task, which still lives in Wrike, so I can see the origin of the idea.
- Back in the idea folder, I can filter for tasks with "accepted" status any time and know that they became projects.
It would be even better if the newly created projects had full info brought over from the original task, and other, tighter integration, but this workaround for now gives some of that.
Really hoping you guys will make this happen soon, thanks!
Our company really needs this 'task to project' option. Half my department uses Tasks and the Kanban or Scrum agile style of project management due to the many different statuses that a task passes through, and another part of our department use projects witha simple set of statuses. Both options work for each team in different ways. But from a throughput point of view, the task-orientated department and the project-based team can't follow a project through from A - Z. So being able to convert a task which has history, attachments and custom fields into its own Project is very important.
Any Reason why this tread has gone to a "back burner" status? the post that led me to this thread (Feb 2019) https://help.wrike.com/hc/en-us/community/posts/360015641334-Convert-Task-to-Project - makes note that it has a 'coming soon" status?
Please let me know if this is going to be developed further.
I just AGAIN created a folder of tasks that then became projects and had to re-enter data because of the lack of this feature. I really like Wrike, but this is not a great gap to persist.
Hoping to get an update on this soon.
My use case for this is similar to @John 's above. My team creates a list of events to pitch for the year, which makes sense as a list of tasks housed in a folder; however, when an event moves forward, we need to create a project (duped from an event template). So they then have to duplicate all the communication, attachments, etc. from the original event task into the new project. It's definitely not a perfect solution, lacks flexibility, and takes time away from doing the job (vs. "doing the Wrike").
It would be great to still be able to build that event task list and convert the tasks to projects once they are approved.
+1 for this request. Surprised to learn this has been an ongoing request since 2017 - would love to see this resolved as it would expedite our work!
Just had yet another occasion today where that fix would have been so very helpful. Instead was cutting/pasting and messing things up.
Hi everyone! Here's the latest update on this suggestion: it is considered as a potential improvement and your feedback and examples help a lot to keep this on the team's radar. At the same time, I can't provide any ETA at the moment. I will get back to you as soon as I have more info though. Thanks a lot for your support here!
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 is wonderful news! To be able to convert a task to a project and a project to a task would be a HUGE game changer for us.
Thanks Lisa. I am sure you guys would be happy to have this point of friction out of the way. It is such a natural way to work though - start with a task and build it up and build around it into a project that this is really never going to go away. Of course, no one is going to simply ignore using Wrike due to this one particular issue, but from a CX perspective, this will be a grain of sand that will be an irritant until it goes away. But, thanks for responding.
Piling on here, we need this too!
Please make this happen. Sounding in and being repetitive but it is a natural progression to work with ; Tasks group together to become a full on Project. Why has this been a 2 year thread? :)
I am totally in with this! need this feature as tasks potentially grow into projects.
Please please please make this into a thing. It would make the flow of requests that come in from Wrike Forms into actual Projects so much easier without losing the metadata attached to the original submission or creating an extra layer (which we do now) that is totally unneccessary.
Thanks Anastasia for this idea however it does not solve for any text information or attachments to the original task. I am having to copy/paste over information manually and the cumbersome process of downloading/uploading files.
We developed a case management flow from our salesforce queue to Wrike where the projects are managed. Many Cases submitted by 'boots on the ground' turn into projects, and sometimes even Spaces. The inability to directly push a Task (or even a Subtask) into a Project is prohibitive and has been causing our team to examine Trello as a viable alternative due to its inherent simplicity.
Please develop the functionality to convert a task to a project ASAP.
Yes sadly this gap always comes up at the worst possible time - once you are deeply committed to your content only to find out they are locked into being tasks and can't be liberated.
I am also wanting this feature to convert tasks into Projects. Does anyone have a work around?
Priscilla Dodd the only 'workaround' I've found is to create a parent project and move the task inside of that project. Any subtasks can then be re-arranged.
My workaround is to be very very incredibly thoughtful and cautious so I don't have to re-do a bunch of work. Have done that once to often already.
I have to say the lack of movement on this by Wrike's product team is giving me major pause in continuing on with Wrike. We have found Wrike extremely useful in logging various "quick hit" items that the team comes up with - ideas, thinks to remember, etc. They all have to go in as tasks with the way Wrike is currently structured. But many of them are not tasks in the end by any means. We really need to be able to convert these - not only have Hive and Asana allowed this for a long time, but Clickup just introduced the capability as well:
Without this capability, we have to do this type of workaround:
- force my team to think through if something is actually a "project" type activity when entering in Wrike - that's a lot of overhead when you are trying to jot something down quickly via your iphone
- potentially make things that when in as Projects converted back to Tasks, as it turns out we aren't ready for them and they shouldn't have been projects in the first place and simply crowd up Wrike with too many Projects while we plan and/or table them.
You guys have these other tools I mentioned beat with the way you have project management handled through your excellent Project/Folder system, the new custom status on Projects, and other features. But without this my Wrike is becoming too messy, and it is such a big factor I may move on.
Thanks for listening, and please get this done ASAP!!
Well said Al Sape you hit it right on the head. For all the things I like about Wrike, this issue stands right in the way when you are first engaging with work - it literally kills your brainstorming and creative mojo as you have to work within the tools limitations of what an idea is - is it a task, it is a project. It is a real bummer this can’t get resolution.
One days use of Wrike and it is very clear that the ability to covert a task to a project i much needed.
Please Wrike team...............
Would love to see this as well! We have robust request forms that spits out projects. Every now and then, though, our clients would submit a custom request that too small to be a project and would be more suitable as a 1-assignee task. Having an option to convert this would be awesome! Right now we create a new task and delete the old project. It's not a big deal until the client tries to search for the project with the ref# they have from the email confirmation.
Chiming in on this one. We are looking to move a process from spreadsheets into Wrike. Currently, a request is entered onto the spreadsheet and then another team reviews the request. Based on their review, they determine to move forward with the request in one of three ways; 2 of those require a project to be created. It would be great to have the initial user submit a Request Form that creates a task that goes to the appropriate team. That team reviews the details and can then 1) Convert to Project Template A, 2) Convert to Project Template B, or 3) No Action. That would be fantastic!
+1 On this. As many have said I also create tasks to keep a quick list of things that then become projects. I am a freelance writer who submits proposals on a freelance site, after i submit a proposal I create a task for the job with the details so I know what possible jobs will be coming up. Once the contract is approved I need them as projects and having to then copy and paste takes extra time. I have been doing them as projects but that is not truly working out so having them as tasks first and then having a quick way to turn them into projects would be extremely beneficial.
Another +1 for this. This functionality is important for us too!