[Status: Backburner ⌛️] Sort function for sub-tasks

It's amazing to see how many people are asking for this feature. And how long they've been asking for it. Adding my voice to ask for this feature to be included.

Welcome to the Community Chris LeBrun! Thank you for voting and sharing your feedback 🙂 Once this post reaches 60 upvotes, we'll be adding a Product status 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

For anyone this might help, I was trying to sort and found this workaround! 

Create your task and for your subtasks number them. When you do it in this way, it'll insure that 1 still comes before 10. For example:

Single numbers you'll want to use a double underscore:

__1.

__2. 

ETC.

Then when you get to double digits, do the single underscore:

_10.

_11. 

This worked for me and is SO helpful with those subtasks! 

Hi Julie, 

Thank you so much for your time in sharing this solution. It has been a bit frustrating. Our team has also found using the numbering system (00X) for tasks and subtasks to be incredibly helpful! 

001. 

002. 

003. 

Hey Jules Aldag, Brooke Knowles, thank you so much for sharing this! 🤗

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

Can we get this feature added? 

Hello Jen Derry, thanks for posting and adding your support for this suggestion. 

Our Product team has access to each suggestion posted in the Product Feedback forum and according to our Product Feedback Guidelines and Statuses, a suggestion receives a status after receiving a minimum of 60 votes. It means that there is a threshold that, once reached, automatically requires the Product Team to provide an update.

We have so many great ideas here on the Community, it's impossible to investigate, comment, and implement them all, but we can at least commit to updating everyone on ideas that have 60 or more votes. You can find more information about our Product Feedback process here as well.

Please let me know if you have any questions 🙂

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

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

Wrike, What is the status of this request?  Looks like it has 60 votes but I can't tell when it got the last one needed for your team to work on this.

Hi everyone, thank you for the continued support for this request. I've checked with our Product team, and this suggestion is not on the short-term roadmap currently but they will continue to gather feedback and review it in the future. Therefore, we've assigned the "Backburner" status for the time being.

Please continue to vote and provide use-cases by commenting and we'll be sure to update you here if we have more information to share 👍 

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

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

This is sorely needed. It's sad to see it's been "backburnered" for five years without progress. They've redesigned the interface (excuse me, experience, what a load of hogwash) several times but can't find time to add this useful quality of life feature.

Hi Alexander Numann, thank you for posting and sharing your feedback. The Product team is still interested in this suggestion, but due to other priorities, there are no plans to implement this idea in the near future. I understand that this might be disappointing, but rest assured that your input has been shared with the team and that if there are any changes, I'll be sure to let you know.

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

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

I would say disappointing is a huge understatement. This has been requested/needed for years - actions speak louder than words, and the actions indicate little to no interest in implementing this. To say otherwise is just lip service.

I agree on the disappointment. This is very confusing to our users who are tasked with doing things in a certain order.  Having to manually click on sort by title every time they open it is not ideal at all. At least if we could make it default to a particular sort that would help. I thought we had this before but do not see it any longer.  We use prebuilt blue prints with tasks in them that are performed linearly. Which blueprint is used depends on how questions are answered in a form.

Hey folks, thank you for your feedback here. I did want to add some additional detail for context. 

When deciding what to work on for future implementation, our team looks at a range of factors, including Community votes and feedback. The popularity of a suggestion helps the team to determine the impact new functionality will have for users, so the more votes a suggestion has, the more the team can see the need. You can read more about the process in this post.

I understand that it's disappointing that this suggestion is 'Backburner' for now, but this does not mean the suggestion will never be implemented. In fact, the more support and votes added here for this suggestion, the more the team will understand the demand. Check out this wrap-up post to see how Community feedback made a difference in 2021. 

We've passed on your feedback to the team and will continue to do so and if there are any changes here, we'll be sure to let you know 👍

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

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

So the threshold to consider an idea is 60 votes, but there's a higher threshold required to implement the request? How many are needed to implement something other than an interface overhaul?

You linked to blog post showing 12 completed requests; only 2 had 60 or lower (45) votes. The next highest after 60 was 80; average was 159.3.

Will 80 be enough? Do we need to break 100, or get all the way to average of that list?

I can ask every user at my company to visit this page and add a vote if that's really necessary.

I do not think it is a correct policy to put this type of threshold but I think it is more correct to evaluate from a technical point of view what the change request entails. If two hours of work are sufficient for a team of programmers, why wait years?

Hi Alexander Numann and Tomasi Mattia!

Thank you both for letting us know your thoughts, we appreciate your feedback and questions here.

My colleagues have mentioned that the amount of those votes and comments are important as they help the team understand how popular different suggestions here in the forum are. When deciding what to work on, the team looks at these votes and comments as well other information like data and analytics, research outcomes, and reviews all of these elements together to determine if a suggestion should be worked on. As an example, for this particular suggestion, our analytical data shows that for most Wrike users, subtask lists don't have many items, and that’s why for now, the team doesn’t plan to prioritize this idea as there are other feature updates that will have a greater impact for more users. 

The 60+ threshold is in place to allow us to shine a light on the more popular suggestions on the Community and to make it easy to see at a glance what the current status is. The team isn’t able to commit to working on every suggestion that has reached this threshold, but they do review all of the suggestions that have reached this threshold regularly to see what factors are at play at the time and to determine if they can be worked on. This is why we encourage users to continue to vote and share feedback on suggestions, as the more votes and comments an idea has, the more the team understands how many users will see a positive impact from its implementation.  

We understand that this isn’t what you would like to hear from us in relation to this, but we’d like to stress that this doesn’t mean that the team won’t consider this suggestion in the future. They will continue monitoring your feedback from this thread and we will let you know if there’s any update/news to share here. 

We really appreciate your detailed feedback, thank you so much for sharing it! 

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

That's really great and all, but how many votes does this need to get implemented? This is a serious question; please don't ignore it this time.

Please let us know how many votes we need, and we'll get them.

Lisa? how many votes are needed to implement this missing feature?

Hi again Alexander Numann, as we've outlined above, this isn't just dependent on vote count and the team makes the decision based on all of the available information at the time, so there isn’t currently a threshold for the team to start working on a particular idea. We'll be sure to keep you up to date here if there are any changes or plans for this 👍

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

Well, that's intensely disappointing (but hardly surprising, unfortunately). Wrike seems more interested in telling users they're using the tool wrong than improving the tool to fit how people work with it.

Hi Alexander Numann, our team is constantly working on improvements that will enhance our user experience - you can see what's new by subscribing to the Weekly Release Notes forum. As mentioned previously, the Community plays a very big part in shaping the future of Wrike, and all Community suggestions are shared with the team. Again, we want to ensure that we focus on feature releases that will have the biggest impact for the most users and it's for this reason that we can't implement each suggestion. Thank you again for the feedback that you’ve shared in relation to this idea. We’ll make sure to let you know if we have any updates here in the future.

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

Lisa in my experience, your team is much more focused on "sexy" interface updates over fixing basic usability/quality of life issues. With all due respect, I am not interested in another forum for a work tool. I want wrike to fade into the background while I get my work done - that's what the best tools do. Wrike is not the star of the show; but an important member of the cast or crew - I hope that analogy makes sense.

I recently spent months going back and forth with your team about a bug. Your team assured me this was user error on my part and not a real bug....until they looked deeper and confirmed the existence of the bug I had been telling them about for weeks. That was last week; the original report was in January. Ticket #1109164. It took three months to get Wrike to admit the bug exists, but at least they will fix it soon right? Nope, it's in the backlog with no ETA.

Similarly, this subtask sorting is an important quality of life/usability change that should be addressed so the affected users can get more work done more easily. "Help users get more work done more easily" should be the company mission, in my humble opinion.

Here's a really basic one - why do I need to sign into the Wrike forum every time I come here despite my browser having a "remember this computer" logged-in Wrike cookie already? It would save me time each time I come to this site if it could inherit/share the login session from the actual Wrike workspace. Another basic issue which "isn't broken", but costs me a few seconds every time I visit this page. From the Wrike perspective, this is fine and not broken. From my perspective, Wrike doesn't care about issues affecting normal users regularly, instead favoring flashy interface redesigns no one asked for that introduce bugs that your team is reticent to admit even exist, let alone commit to or focus on fixing.

Hi Alexander Numann! First of all, we would like to thank you for the feedback that you’ve been providing us with here and on other channels. We really appreciate you taking the time to point out the things that you think need improvement. 

I totally understand the analogy you’ve used here, thank you for sharing. We do indeed aim to help you do the best work of your life and this is why, among other things, we are very happy to provide customers with this forum to be able to share feedback on how Wrike works and what they think could make the experience better for them. 

We have taken a look into the recent communication you had with our Support team in relation to the issue that you’ve been experiencing. Please be assured that the team’s aim was to get all the necessary information in order to investigate the issue properly. It can be tricky to recreate and identify bugs like this and the team was able to locate the issue thanks to your help. It’s been logged with our engineers now and they will keep you informed on how things progress.

In relation to subtask sorting, as outlined above, the team makes the decision on what to work on based on all of the available information. This includes reviewing all of our customer's usage, analytics, and feedback from the various channels that we have. Because we want to ensure that we focus on feature releases that will have the biggest impact for the most users, we do need to prioritize and that is why this is not on the roadmap at this time.

I’d also like to address the login process that you mentioned. This is something we’re currently looking at improving, so your feedback is very useful and we’ll be sure to update you on any changes to this on the Community. Thank you for bringing up this topic!

Please rest assured that we take your feedback seriously and we are very thankful to you for providing it. If you’d like, I can also notify your account team of your concerns and have them reach out to you to discuss. Please let me know if you would like for me to arrange this.

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

If you don't have enough engineers to implement basic usability/quality of life improvements, maybe you should hire some more, or prioritize them over another interface redesign.

I do a lot of IT work, so please trust me when I say I am more than familiar with difficulties around collecting information to investigate root cause and do troubleshooting. Regardless, blaming the user and telling them they're the problem is actively counterproductive. You can defend that approach or deflect from that issue, but it's something I experience almost every time I interact with your support team, which is deeply disappointing.

I obviously cannot force you to reprioritize, but I'll repeat my suggestion you hire or allocate resources to dedicate to basic usability, which can be lacking in several corners of the sprawling Wrike interface. Perhaps fixing what you have now should be placed above another full redesign.

Hi Alexander Numann, thank you for sharing more information about your experience with our Wrike representatives. We have taken your feedback on board and will be following up on this internally. We appreciate you taking the time to share your detailed feedback with us 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

Lisa I hope so, but those feel like empty words with no substance behind them (and more deflecting from the issue). Words are easy; actions show genuine intent.

Why don't you speak with actions instead of platitudes and commit to getting the devs to fix this basic functionality so all the users asking to be able to sort subtasks can?

Alexander Numann, our team is aware of the ask here but as outlined previously, there are no plans for this currently. We will let you know if we have updates on this suggestion in the future. Thank again for sharing your feedback with us 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

Lisa very disappointing, but consistent with my experiences using Wrike and dealing with your team. I hope things improve, but I don't expect they will.

Hi Alexander Numann, we have outlined the reasons why this isn't planned for now in our previous responses here, we're sorry that you're disappointed. Please be assured that we'll be following up internally in relation to the experience you shared above. 

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

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