[Status: Not Planned] Code formatting in task descriptions

4 years of this request, people making it very clear it's an absolute need, and you still can't find the time and resources? Get a freelancer on it, please, something to get this one through!

Thank you for supporting here Stevie Kirk, I understand that this is disappointing that code formatting in descriptions isn't planned for now. I'm passing your feedback to our Product team, and if we get an update in the future, we'll make sure to let you 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

Is it planned to implement this feature in the near future, if so when?

Hannes Treml Not to be the bearer of bad news, but this feature is almost certainly never going to be implemented. I've been following this thread for a year at this point, and we've heard everything from "Not enough time" to "It's not a popular enough feature". My understanding is that features are chosen almost exclusively by popularity. This request is already 4+ years old, so unless every dev team using Wrike suddenly comments in and likes all the comments in this thread, it'll be another 4+ years before it hit's anyone's development queue.

+10000

Hey folks, thanks a lot for your continued support for 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

Lisa Is that 60 votes per year? This request has 81 votes currently.

Grayson Lorenz Once it reaches 60 votes in total, it receives a status. For this suggestion, the status is currently 'Not Planned', but we continue with our process of feedback gathering and we pass it on to the Product team. 

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

Grayson Lorenz I like your idea of getting a whole team to upvote, sadly I already tried that with another request (logging half day holidays in Wrike). My whole Studio upvoted and pushed it way above the threshold, yet still, the same response was given. Were just voting for it to be 'discussed', it seems.

Upvoted. Please add.

Adding the 90th upvote, 10 more to 100!

It is really unfortunate that people have to lobby like this for a paid software feature request. It is also driven from so many teams needing this kind of capability in their day-to-day operations and making Wrike work for ALL teams across their company. In effect, we are trying to make Wrike more valuable.

Unfortunately, the wrike team doesn't really care about any of that. I will keep this in mind when my wrike contract comes up for renewal and look for other platforms that do.

Thanks for your support of this suggestion, everyone!

Tushar Ranka Welcome to the Community! 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, and Wrike is an out of box solution. 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

Lisa - Thanks for your stock reply. I have seen the same reply many times over when people express their frustration at your process. Again, I hope you can take this feedback about your process to your product and leadership team, and let them know that it is frustrating, but I am not holding my breath. Being an engineer by background myself, I can go out on a limb and speculate that this is a very easy feature to implement since you allow other kinds of formatting in the task descriptions.

Lisa The thing I find most interesting is that because Wrike doesn't have code formatting it likely means that your own developers don't use Wrike for planning and task management. I can't imagine making a Dev team work without code formatting. Is this true? If so do you have a recommendation for a project planning tool that works well for people who work with code, maybe JIRA? If your developers do use Wrike, can you ask them for suggestions for how they work without code formatting?

For what it's worth, I lobbied successfully for our team to stop using Wrike over this issue. We use Jira now.

Hello again, folks! I understand your disappointment about this suggested functionality not being planned by our Product team. Please rest assured that all your feedback here is being reported to the team. Right now, there's nothing more that we can do apart from passing on your feedback and asking for regular updates on the topic. Our team has many exciting enhancements and new functionality planned this year, and many of them are those that the Community has also suggested. We'll be letting you know about them in the coming weeks and months.

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

I can't believe that this feature is still not implemented for 3 years ... 
This must be a cost effective feature. I don't know services which doesn't support code formatting. It's a standard HTML tag.

I understand your point Junya Hayashi, thank you for providing your feedback, it will be passed to our team shortly 👍

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 would love this feature as well.

Whatever the votes, for our team, if we look at Wrike's competition this will become a deal breaker very soon.
Wrike has obviously no interest in their competition features & their customers needs expressed over the years, especially any software related customer like us.

What also bothers us and it as been stated multiple times here, this is a simple feature to implement. It's a "no-brainer". A lot of requested/upvoted and delivered features have been much more complex to deliver. Some of them have had iterations after "delivery" and a lot of them had a very limited UX impact compared to this one, whatever the number of votes they get. Still Wrike product & dev team seem to favor votes (or other business strategy/factors) over a simple game changing feature like this one. In the (huge) meantime Wrike even took some off to open a "lab" to experiment some complex and very low benefit features... Priorities 😂 

So I'm asking myself, does Wrike internal product management only weigh in votes in here ? Or do they also account for Wrike's UX impact per feature and does their product team know, somehow, how much this is a pain & a loss regarding Wrike's competition ?

Don't get me wrong but Wrike isn't the cheapest tool out there and they somehow still manage to not deliver a multi-year requested feature that is simple as hell to implement, regarding other delivered & "lab" experiment.

Oh and for other software company reading this, just know that this tiny missing feature sits just on top of a product that isn't stable with multiple & repeating downtimes with regular "read-only" periods which still occur today. But also a product that still relies, after several years, on an external Github/Gitlab/Jira two-way sync provided by a premium third party (Unito), which requires a subscription on top of Wrike's subscription... 😤
Again, Wrike seems to have very little love for their software making customer and their competition is way ahead.
Between those and this very simple feature request, as a software company, we now clearly feel that betting on Wrike for our project management is a call that we won't be making again.

Anyways after reporting this in multiple feedbacks queries & on several occasions to our Wrike account managers over the years, if we don't get this feature in the upcoming quarters this will be a deal breaker when we re-evalute our position on our Wrike subscription. We are already studying & experimenting with alternatives to Wrike because of this default that annoys every layer of our company, from decision makers all the way to our junior developers.
Finally, to Wrike's "customer success" managers and CMs, don't bother with a standard delaying answer here about votes and Wrike's own product team priorities : Wrike's roadmap & delivery has proven over the years that this platform doesn't now and won't in the future drive software customer success. Either you deliver basic features like this one OR you don't care about your software customers. After all those years, those are Wrike's only two possible outcome/commitments to software companies, period.

What Philippe said! Seems Wrike favour taking the edges off their boxy graphics, more than fixing this deal breaker and others. We're reviewing our options for 2023 also.

You're right, Philippe. I can't see why "We don't want to" is a sufficient answer. The less effort it takes compared to the more benefit it gives, the faster it should be implemented if there's nothing serious that prevents it from being implemented.

I strongly agree with Philippe. I'm waiting for this feature for years.

Well said Philippe! This is just one of many "small" but very annoying things missing in Wrike for us Software Developers.
And the standard answers about votes and process etc from the Support guys have started to annoy me as well. Sure I can understand that not everything can be worked on or prioritised, but more transparency would be good. 
I wonder/hope that their own software team (actually all the company) is using Wrike to "eat their own dog food" as someone suggested even earlier in this thread, I think changes would happen faster then (or maybe slower if it is not good enough for them as well... but that would be quite telling on what they should focus on).

Hello again, everyone! I apologize for the late reply here, I was checking with our Product team to see if there are any updates on the subject of code formatting in descriptions. For now, this isn't on their short-term roadmap. They do receive your feedback and would like to act upon it, but it isn't possible at the moment due to conflicting priorities and the complexity of this functionality. Please rest assured we will continue bringing up this topic internally, and send your feedback to the team for future consideration, so do continue to share it here (please share your use cases and keep to the topic of this discussion). Thank you again for your continued 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

As a software developer using Wrike every day I wish you would implement this feature.

Another developer here.  I've been wanting this feature since I started using wrike for my job two years ago. Please add it.

This whole thread is so painfully frustrating to read through.  You already have code blocks in task comments... you have a code block in the very text editor I'm typing in right now(I know this is zendesk, but come on... just about every javascript wysiwyg editor in existence can do this)

How is the feature too complex to add on task descriptions, but not too complex to add on comments?

This is a 4-year-old thread and has only gotten lip service from the Wrike team.  I don't know what billion-dollar feature they are working on that prevents them from implementing this low-hanging feature. The simple explanation is Wrike doesn't care about your feedback.

Anyways, I am not holding my breath for this and simply taking my business elsewhere. 

We'll be very sorry to see you go Tushar Ranka. I do understand your disappointment about the fact that this feature is not currently planned by our team. I would just like to point out that some of the asks from the community do get implemented when possible. For example, you can check out this post to see which Community suggestions got implemented in 2022. At the same time, our team can't commit to working on all ideas due to various factors, like the number of suggestions we receive daily, analytics, and the overall vision. At the same time, we have a process that ensures that all feedback is reported to the team for consideration, so please rest assured that your thoughts are passed on to the team. If there's anything else that I can help you with, please do 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