Convert Tasks to Projects or Projects to Tasks

We have created a new request form currently set up as a task. We have found often times client requests are more project oriented with multiple tasks. Yet other times client requests are simply tasks. It would be helpful if the original request could be converted vs creating a new project from the originial task request and maintaining the information at a project level. 

Upvote 29
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
16 comentários

am seeking same answer we set up request forms in our account and it is set up as projects for each new submission realize we want to change it to task instead of project...how can we convert project to task then we can assign to the correct folder or project

3
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi folks, thanks a lot for sharing your feedback! This isn't planned by our team at the moment, but we'll share your feedback internally.

Please let me know if there's anything else I can help you with 🙂

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

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hello,

It appears that this request originated in 2017. It was upvoted plenty of times obviously: Convert a Task into a Project 517 times. I also see that there were many, many workarounds, suggestions and follow up requests that justified this feature by MANY people. I also see that this request: Convert Task to Project was picked up/requested again in 2018, 77 upvotes on this one. Now I see in this thread that AGAIN "This isn't planned by our team at the moment, but we'll share your feedback internally.", why? Just exactly how many times can this same request, and all of the follow up conversations happen, for Wrike to actually do what is being asked? Again, this seems like a no-brainer. Yet things that don't appear to be as clear-cut are ever revisited and eventually implemented? 

4
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Hello Catherine Wetzel, thank you for your comment. I completely understand that it is frustrating for you not to see this feature being implemented, and we are aware of the popularity of this idea. Unfortunately, not all suggestions can be implemented by our Product Development Team, and they need to prioritize other improvements aligned with their current projects.
It is also true that feedback is one of the most valuable sources of inspiration for the team, therefore please keep sharing your comments and thoughts with the Community. We are passing all this information to the team, and we will inform you in case there is a change related to this suggestion. Thank you for your understanding, and if you have any other questions or if I can help with anything else, please do let me know. Thank you!

Juan Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Juan Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Okay, lets drill down on this response. 

When you say "Unfortunately, not all suggestions can be implemented by our Product Development Team, and they need to prioritize other improvements aligned with their current projects."

Can you please explain how "their current projects" take precedence over requests that appear to more than meet your requirements over a long period of time in order to actually be implemented? 

What exactly IS the criteria that needs to be met AFTER the upvote number is met, and many years of the consistent need and request,  in order for a request to take priority over "their current projects"?

You see, when that many folks who consistently NEED and request a feature, and do so for many years, with numbers that far exceed your requirements, over and over, the frustration should be considered justified enough to not just respond with the usual indifference and vague explanation, such as "their current projects" take precedence over requests; But to respond with "maybe it's time to look at how we can meet this request and move on." 

Help us understand that you do hear requests and give us a solid understanding of why not, particularly in this fully supported request by your many clients.

 

 

5
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Amen!  I am having to create a project and then move a Task (which is really the project) into the new Project.  Wowza very redundant when a drop down would suffice.  

2
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hey everyone!

I understand that it can be disappointing to see some of the suggestions, especially those that were created a while back and have 60+ votes, not being developed in Wrike. I'd like to shed some light on how this forum operates to provide you with more information.

The forum works based on votes and statuses, but it's important to note that Wrike can't guarantee the implementation of all or even most of the suggestions. While our Product team would love to work on the majority of the fantastic suggestions our users share, it's not always feasible. Sometimes, user suggestions may conflict with the needs of others, or adding new functionality may require resources that we currently don't have available. Additionally, there are ideas and enhancements in the pipeline that haven't been posted yet but are known to benefit the product's evolution.

That being said, we truly value all the feedback we receive, and that's precisely why we have this forum and the processes mentioned above. We carefully track and report on all data, as well as request status updates. Your ideas and concerns are regularly shared and discussed with the Product Managers at Wrike.

Our team strives to allocate some of our resources to customer-generated suggestions. As an example, you can check out this post where we highlight some of the suggestions released last year that were generated by the community. At the beginning of each year, we create wrap-up posts to showcase all the user ideas that have been implemented.

I hope this provides you with more context on how we work with feedback from the Community. If there's anything else I can assist you with, please let me know.

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

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Thank you for this response. Doesn't really answer the primary question though. What criteria needs to be met? 

Clearly very basic functions that only create barriers between your clients and their most simple of needs, are not priorities.

Good to know.

 

2
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

I think this could be a very useful feature.  Sometimes you may have a routine task that then involves more work which would then warrant promoting to a project. 

3
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Thank you for your continued feedback and support of this idea, folks!

Currently, there's a threshold of 60 votes for a suggestion to receive one of the Product statuses. However, it's important to note that reaching this threshold doesn't guarantee that an idea will be implemented. I hope this information is helpful to you. If you have any further questions or if there's anything else I can assist you with, please feel free to let me know.

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

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Chiming in to say that this feature would be very very helpful! 

3
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Looking forward to this feature also. We really need this in our operations.!

4
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Rachael GuichardDesiree Ligtas thank you very much for your comments! We will keep you updated in case there are any changes 👍

Please, let us know if there is anything else you need help with 🙂

Juan Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Juan Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi, I'm new to Wrike and am building my first blueprint.  I set up the blueprint at the "project" level with several tasks, each of which has sub-tasks.  I'm now wishing I had set it up so that my "tasks" were sub-projects, and my sub-tasks are the tasks.  (This would make my blueprint structure match other blueprints that my team has already built.) 

I'm gathering from this chain that it's not possible to change my tasks to sub-projects now that I've already built the blueprint?

I do see a function that's called "change item type," so I'm curious what that function is intended to do if not change a task to a project or vice versa?  

Thanks!

Gretchen

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hoping to see a new feature, really soon (hint hint) for the option to change a TASK to a PROJECT. This happens more often than you realize, and I think it trumps all the revamping of "new views" for the Dashboards, etc. which just confuses people. 
When do you think this will be "on the table" to be included in an upcoming release? 

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Gretchen Hall Carrie Watzka, welcome to the Community!

Gretchen, when using the option to change the custom item type, you can choose from items of the same type. This means that if the custom item type you created is a task type, you will only see other task item types as options. 

Carrie, I understand this would be a valuable implementation for you and I've passed your feedback on to our Product Team. 

If you have any additional questions, please let me know 👍

Also, you can visit our New to Community forum to get the most out of your experience with our Community 🙂

Juan Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Juan Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Convert Tasks to Projects or Projects to Tasks
[this list is visible for admins and agents only]

Alto
Didn’t find what you were looking for? Write new post