[Status: Launched 🚀] Code formatting in task descriptions and comments

happy one year anniversary to this post 🍻🍻

Hopefully the 2nd most upvoted post in the forum will get somewhere next year

This is a major friction point in our org adopting wrike. Wrike has so many other good things going for it, if wrike could support markdown this would be a no brainer. 

UPDATE? are you going to do this ?  @wrike 

i hope so. its allready a long wait and before you know it people will have moved on to other products..  its a fundamental feature

can anyone provide a justification of why this fundamental "issue" does not get the attention it should get? and why the choice is made to focus on items that also important but only after this is fixed ;)

Absolutely agree. I plan to re-evaluate the use of Wrike later this year. While this specific feature isn't necessarily a deal breaker for me and my team... The fact that it's been over a year, there are 4 pages of comments saying please add this feature, with over 100 upvotes, is definitely concerning to me. As well as other threads that are not getting answered.

The product manager posted an update back in September (page 3) where he did outline some of the challenges, so that can be appreciated. Nothing is ever as easy as it seems. I think it would be wise to provide another update soon. You mentioned the dev was to far off to provide a timeline, perhaps now you could provide a better estimate @Andrey Verbitsky. Thank you.

I've already left wrike...now how do I stop getting emails from this thread.

@Thread I have some updates from our team: they've added a task and comment section upgrade to the roadmap for 2018. Like Andrey said, updating the legacy code in the comment stream is the first step before we're able to make any functionality changes to comment and stream functionality. Updating the legacy code in those sections is a big undertaking for the team and a step towards being able to address requests for upgrades. At the moment I don't have details about what will happen along with or after the code updates and I don't want to promise something before it's a guaranteed release. We're bringing up your requests as the team is making development updates. More than anything else use case information helps fuel productive conversations with the team. 

@Grant you can definitely unfollow the post. At the top of each page on the thread you'll see a blue "unfollow" button, just click that and you should stop receiving email notifications. 

This thread is a year old.  Markdown is pretty simple to implement.  WTF you guys?

In our team, there is a lot of demand for this feature. Any news?

> More than anything else use case information helps fuel productive conversations with the team. 

We sometimes have to share code or configuration snippets. Devs and Sysadmins also use the platform. 

I'm on a trial, evaluating a merge from a few tools (including Asana) into Wrike, and I'm really worried reading all of this, which is unfortunate because I was really liking Wrike's potential...

This thread offers a very concerning, cautionary tale of what seems to be Wrike's total unreliability when it comes to reacting to user needs. 13+ months for simple markdown (2nd highest feature) is astonishing, totally unacceptable, and frankly an embarrassment.

Is fixing the #2 most common request on your Forums not worth the relatively little time it would take? To prevent Churn of paying users? To keep trial users like me from being worried upon reading the Forum?

We're running businesses, teams, etc. and we have to be able to count on the tools we choose to do the job. Those who are extra hopeful that Wrike will work are those who come here and write, but many others will just see this mess and leave.

As I evaluate the tool, should I count on Wrike to be reasonably responsive to reasonable customer needs?

Wrike has some key outstanding features, but seems in my viewpoint to be stuck with older technology and no easy way to modernise without regression, and over-complication etc. Wrike has excellent hierarchical structuring and truly powerful tagging and search functions. The different views are great, but there are many niggling concerns ((e.g slow load from permalink), and I don't get a good feeling of engagement with customers, i.e. there is some kind of disconnect going I guess. My assumption is that product is quite old, and difficult to work with, so team is facing some major challenges to get out the of the dead ends. There aren't many alternative products yet with the power of Wrike, so they can ride that factor for a while, but not for too long, as I am sure other products, build with 2017+ technology with great UX, are catching up in the wings  If Wrike could just have the UX and speed of Trello it would be out of this world! Alas, it may not go there, and something better will probably come along. I will do a survey again toward the end of the year on what is out there before renewing our subscription. 

Anyway many do the same "talk to the hand" stuff. Try to get anything out of Google if you want to see a company who does not care a jot about silly users! - see https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/docs/ZSRZYzxPsUQ/5BH2ICfcAAAJ 

perhaps an actual example will help. perhaps wrike's team will see then the basic usage that is missing.

We not only type text, but we need markup and images in the descruption and the comment fields.

look at the below example of what a normal cms/ blog / wiki can do.  they have a markup where you make things like this.

in wrike it looks like this in the description field: (

and somehow its a wonder the column is made there,, but you cannot really work with it.)

and in the comment field it looks like this :

making good technical documentation  does not need a complete wysiwyg result but a basic markup. this is so basic that allmost everyone does it but wrike. ;( it is even so basic that you may assume this is present. its like you car drives and can steer left instead of only right.

I think we can agree now, that there was a fundamental design flaw in what wrike supports in the description or in the comment field.
pasting full html is nice. but markup like this is really minimal

The whole idea, when you work in a system like this is that you can communicate and organise clearly, but that does not work if developers and sysadmins cannot write clean technical documentation or comments, Then people will use other solutions and slowly they will use two or three systems again and there slowly the project management fails and people will start using other project management solutions

I do not want this. i want wrike but i am crippled with this missing fundamental basic feature. 

so personally i really do not understand why this fundamental design flaw is not on the #1 priority list.

I hope the screenshots give some more insight. it would help you wrike would help us make beautiful documentation and comments.

+40 for our entire (paying) org as well.

Are they trolling us? 

Wrike knows what's best for us. If they say this can wait, why, they are the genius start-up folks, that's how it must be. Apparently, customer is not always right anymore. I ran into a similar issue with the Dropbox team refusing to accommodate customer requests to integrate Paper and Dropbox for the past SIX years or so. 

I gave up on Wrike. Staying with Asana for now. They have their problems but... didn't feel the switch was worth it. Not gonna pay $1,800 upfront if their strategy to deal with complaints is to just ignore them. I'll check back in 6 months.

I suspect they simpely do not Care, its all about the $$ or somehow this fundamental change means a complete rewrite of the product, raising even more alarm bells, if you then think of the quality of code of wrike , if its the same mess as this, then i guess its time to move on.

Also i guess the dev and IT teams of wrike are clearly not using there own product , as how could they with missing this fundamental funtion

I cannot Imagine working on something Else then this by now if i was a dev at wrike

Why use the new feature to chat if you cannot fully use the fundamental basic feature. 

Makeing content!!!!!

PS we use skype for the chat. So i do not need another feature then makiing good content.

I use the @mentions for updates 

Focus wrike. Please!!

Sidebar here....

We use Gitlab for coding and have hooked up Unito.io to sync tickets between Wrike and Gitlab. (Github is also supported as are a bunch of other systems). So-- if you use a separate tool for code/ticketing management you can still use Wrike for the rest.

Still isn't a solution to this underlying problem tho!

--Noel

@noel Howel, and @all

but what use does wrike then have? only project management. that simply does not work for the most of us

there is a difference with adding comments to code in wrike or to add comment in clear understandable formats in wrike on the project you are working on, with all the time registration.

the danger is that when we accept this, then slowly wrike willbe fased out and for the cost of wrike i really think its not justifyable and subjected to get some percentage of money back on wrike

When I forward an HTML formatted email to wrike, the formatting is also looking very strange. Example https://www.screencast.com/t/m8OxjfXP 

Is this related to the same issue?

#Really 

If you tell me that there is a post with 144 + ppl asking for this I will shut up 

@Pedro Sanchez - Low hanging fruit, right? It's really easy and cheap to develop PDF export of an image, page, view etc. Seems it's not so easy to implement code formatting in an ageing app UI...

We also decided to move away from Wrike, when our current subscription will end.

The UI seems not easy to evolve, which is quite frightening. There are also more and more latency with task descriptions that do not show up, or only after several cache clear...

Whatever update they pushed on Monday basically broke the platform until sometime late yesterday. Poor development and QA team it would seem. Push broken code to Production and not fix it for 3 days?! "Oh, since we know how much everyone wants comments markdown/formatting, here's a 3-day break and a PDF exporter!" 😂

WTH, Wrike?!

• I was really starting to enjoy our extended trial of Wrike, and really went a long way in setting up various automations, but alas, hit this snag.  I won't even bother to "ask" about when this is going to be moved in.  This is really a deal breaker for us.  Guess its back to the "search" for the right tool.  After trial-ing roughly 57 apps in 4 months, I was hopeful for Wrike.  Only if Asana had halfway decent time tracking..... 

@ Jose Horta,

Until we switched to Wrike, we used Asana + Harvest integration. Nice flow! 

We switched to Wrike for timeline and shared folders between projects and a MAC app. But guess what Asana just added last week... timelines. LOL

We still love WRIKE tho!  More powerful.

@Noel Howell Thanks for the point, we will try Asana just now, as we are really bored by Wrike's lack of support...

Moreover we got more and more latency in descriptions display, sometimes they just not appear. This make the task creation sometimes impossible. This is a real problem when you hope to gain some time in project management, and indeed you are waiting (praying?) for the description to be displayed...

Wrike has definitely some big issues that need to be solved before pretending to be a real solution for project management, especially for IT. The prices are really too high regarding to those issues...

@ Noel Howell,

So you paid for 2 licenses for each employee??  One Harvest and one Asana??

@the wrike team.. Hi

any updates on this?, would expect a response here periodically, is it on the dev agenda yet?