Upvote
558
Folllowing List for Post: [Status: Not planned] Convert a Task into a Project
[this list is visible for admins and agents only]
Страница, которую вы ищете, не переведена, но у нас есть другие материалы на русском языке и служба поддержки на русском языке.
Чем мы можем помочь?
Learn. Share. Discuss.
Folllowing List for Post: [Status: Not planned] Convert a Task into a Project
[this list is visible for admins and agents only]
I'm still figuring out how to use Wrike effectively and I've already discovered the need to convert a task to a project.
Thanks so much for supporting this suggestion, folks!
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 too just realized we could use the easy feature of converting a Task to a Project with the click of a button. Here's to my vote!
Honestly, this has been a feature request since 2017. Is it even on the road map?
Hi Nathon Hay, welcome to the Community 👋 Thank you for supporting this suggestion!
Please let me share some detail on how this Product Feedback forum works. We have a voting system here where any Wrike user can upvote a suggestion when visiting the Community. There are other ways to let us know your feedback, and the Community is one of them. We have a process for reporting all suggestions, feedback, and votes from this forum to our Product team, and they continuously review all of this data.
Once any suggestion reaches the 60 votes threshold, we add a Product status to it. You can check out more info on that and on the list of statuses in this post. The status for this particular suggestion is currently 'Not planned'. The team has been reviewing and continues to receive the feedback here, but they can't prioritize it over other planned releases and enhancements. If we do have an update for this suggestion in the future, we will let you know about it here in this thread.
Our team can't commit to working on all or even most of the suggestions in this forum, but at the same time, feedback from this channel is still important to them. As an example, here's the list of Community-generated suggestions that the team has released last year.
I hope this info was helpful, but if you have any questions, 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
The status says "not planned". When do you plan to release this, Lisa
There are no plans to work on this suggestion currently AH. I understand this can be disappointing, but we continue passing the feedback from this thread to our team.
We'll let you know if there are any changes 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
Hello Lisa,
Does the team include the Product Owner and the Scrum Master directly? If so, could you please let them know that while I understand there might be priorities, I think the most voted feature in a user voice platform during 5 years should pull a higher weight than other lesser requested features such as the recently announced "duplication of work schedules", am I right?
I'm not trying to be bitter or rude, and definitely not blaming the community managers/service reps. But I do have to say that I think it's apparent that the 5-year-old most requested feature not being even in the planning stage indicates either a communication issue, disregard of paying clients' feedback, or the third alternative (which would really suck): there is an issue in the development area; either devs lack the skills to make the change or maybe the platform has spaghetti code.
Besides passing the feedback from this thread to your team, what other alternatives do have users to communicate this to the people in charge of the change log?
Thanks in advance and again, sorry if I sound frustrated but at this time, I think I really am.
I realize this is not planned and adding my feedback here may be a wasted effort, but as a newer user here I'd like to share my scenario. I have an item I started as a task and then realized I should put sub-tasks in to better track everything that needs to be done. Twenty-three subtasks in with more to be added, I'm realizing this really needs to be a Project and not a Task. This is particularly needed because the completed sub-tasks are cluttering up my view in the task.
I know in a Project I can show only the active tasks. Also, this is really an ongoing project, and there will always be additional tasks to do in the months and years to come, so it is better tracked that way. I've seen the workarounds to convert this and that's what I'm going to do, but it will be somewhat time-consuming and would be great if there was a faster, easier way to do this.
Hello folks, apologies for the late reply here!
I wouldn't say this is a wasted effort to share your use case and a need for converting tasks to projects even while the feature isn't planned by the team. They continue receiving and reviewing your feedback here, so thank you for sharing it!
As I mentioned previously, our team can't commit to working on all suggestions in this forum, but your feedback from this channel is still important to them. Please rest assured we'll let you know if anything changes in relation to this suggestion.
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
Adding my input here as well. The ability to convert tasks to projects, and vice versa, would enable the PM to restructure a project hierarchy if the project needs change.
100% this is a must-have feature and it's incredibly short-sighted not to include it on the roadmap
Our teams (68 people), are awaiting on this feature. We have plenty of projects that start as a small task and then it turns into a project of its own, making the original project a program. Having to do all the duplicate effort to create a new project with information that is already there, seems like a waste of time and energy.
Please give WAY MORE priority to this feature in your Backlog.
Thanks!
While I don't have the glaring need many other users do, I simply tried to convert a task to a project today and was surprised I couldn't. Found this thread, and realized that while this particular lack of functionality doesn't affect me much, the lack of product response to consumer need is discouraging.
Thank you for your continued feedback here, everyone!
I understand your point here, and the team regularly receives new feedback from this thread. Unfortunately, as I mentioned above, the team can't commit to working on all or even most suggestions in this forum. At the same time, they do refer to Community feedback when researching and planning a lot. For example, the release of the Email Communication With Non-Wrike Users feature was completely based on a very popular Product Feedback thread on the Community.
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
Hi Lisa,
Another vote here for this shockingly neglected and important feature Wrike should have.
Any news from the project team concerning this 'Convert Task to Project' feature?
Is there anything else the community can do to get this feature on the Wrike team's map? Voting here doesn't seem to be sufficient — This is pretty clear considering after 5 years of many user voices it has still no movement or update on its consideration.
Welcome to the Community Donato D. 👋
There's no update since this comment of mine in June this year. We will let you know if there are any changes here in the future.
Please let me know if I can do anything else for you.
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
Regardless of the request itself, I find this an interesting case of vendor/customer relationship management. The value of this request is obvious and clearly Wrike is not going to do it, no judgement just stating a fact, so instead of letting this linger, would it be better just to own it and inform the community that it is not going to happen and close the case once and for all? Or, is it better to keep this open an maintain a lingering annoyance that maybe it will get done, but most likely not, but we welcome people to keep asking. Again, just as a thought exercise it is interesting. I am wondering what users would prefer? A hard NO or a rolling maybe that goes on and one.
Hi John Gieschen, thank you for taking the time to share your thoughts, I do understand your sentiment. We do have a status assigned for this request "not planned" yet Wrike is dynamic and our team is constantly working on improvements and additional features to our platform.
The roadmap of the team is shaped based on various data and research so nothing is a hard no since we constantly review customer feedback and data. As an example, the Due Date time request is where the user's voice played a major role in the release of this functionality in Labs after substantial support from the Community and other channels.
Cansu Community Team at Wrike Wrike Product Manager Узнайте о самых популярных функциях Wrike и советах по его использованию
Cansu Wrike Team member Узнайте о самых популярных функциях Wrike и советах по его использованию
Thanks @... that makes sense, and I see Wrike is responsive where they can be. This particular request though is so fundamental to the common sense workflow of using Wrike, it seems pretty clear there is a fundamental hurdle to making this happen and it was discussed earlier it is most likely an architectural issue with the way the software is constructed. So, I wonder if it would be more productive to identify this is a gap in a common sense workflow and get out in front of it and ensure people know this is a bit of pothole and how to avoid it. Or, keep it in an ambiguous status for another few years. Again, I don't fault Wrike here and I got passed this by various work arounds and being educated that you can't convert a task to a project, I just find this an interesting case study of community management/engagement.
Hi John Gieschen, thank you for getting back to me, we do try to share as much as information we can and try to be as open here with our Community members. Part of this effort is also to bring Product Managers and other team members to contribute to the Community and connect with our members to close the gap. I will definitely take your feedback to our Community team for discussion as well.
Cansu Community Team at Wrike Wrike Product Manager Узнайте о самых популярных функциях Wrike и советах по его использованию
Cansu Wrike Team member Узнайте о самых популярных функциях Wrike и советах по его использованию
Adding my vote to this thread. It's certainly not a deal breaker, but it is making me reconsider other products.
Hello Briggs Alden, thank you for sharing your thoughts and feedback here. I'm passing it on to the team.
Cansu Community Team at Wrike Wrike Product Manager Узнайте о самых популярных функциях Wrike и советах по его использованию
Cansu Wrike Team member Узнайте о самых популярных функциях Wrike и советах по его использованию
Adding my vote as well. Many simple tasks, like an audit for a prospective client that turns into an actual client, can snowball into larger things with a lot of information and work history attached. This is a rather common occurrence in our use case, and the ability to change tasks to projects would be a huge time-saver.
Thank you for adding your support and sharing your use case here Mark Kaufmann🙌🏼
Cansu Community Team at Wrike Wrike Product Manager Узнайте о самых популярных функциях Wrike и советах по его использованию
Cansu Wrike Team member Узнайте о самых популярных функциях Wrike и советах по его использованию
Adding another vote, this is desperately needed and adds a lot of manual work when you decide a series of tasks would work better as a project.
Seeing as this thread is 5 years old at this point I suppose there isn't much use to voting, but this feature would help a lot in situations where things that start as simple tasks evolve over time into projects.
Hey folks, thanks a lot for your additional feedback here! Our team is definitely aware of this suggestion. Even though it isn't planned at the moment, we continue passing on your feedback to them.
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
Agree, this feature is much needed, convert folder to task and vice versa.
Thanks Aaron, we appreciate your input here. We've passed it on to the team 👍
Elaine Community Team at Wrike Wrike Product Manager Узнайте о самых популярных функциях Wrike и советах по его использованию
Elaine Wrike Team member Узнайте о самых популярных функциях Wrike и советах по его использованию
Upvote here! Our team would really benefit from this as we are going through a big transition. Would love to see this become a thing