[Status: Not planned] Markdown formatting in Description field
It would be incredibly helpful if we could use Markdown in description fields.
e.g. instead of having to use the mouse to choose the header level, simply type ## at the beginning of the line for a level 2 header etc.
Dropbox Paper is a good example of this working well. Markdown is enough of a standard for this to be worthwhile.
I really like using Wrike as a note taking tool (for meetings etc) but the mouse-based formatting makes it rather slow.
Thanks.
This is important. Markdown features are needed. Please consider adding these features. Thank you.
Thanks for your continued support here, Simon Taylor, Alex Hendershott, Tobias Zimmermann!
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
Four years has passed and still don't have support for markdown in the description field? 😐
Let's keep this ticking over Christian Predebon and others.
Have each of you on this thread done at least the following?:
Also, it's time we started a user group I think. If any of you think the same, feel free to reach out to me at: simon@unisolve.com.au
Markdown please!
Why, in 2022, does any collaboration product still not have Markdown support? It is not convenient to write and format text in a web browser, so for anything longer than a sentence or two, I write markdown-formatted text in Vim and copy/paste it into the web interface.
Hi Po Shan Cheah, welcome to the Community, and thank you for posting.
We’d love to be able to implement all of the suggestions that our customers share with us, but we have to prioritize certain requests over others based on various factors and considerations at the time. Although this isn’t currently planned, we continue to pass on all of your feedback and insights here to our Product Team, and of course, I'll be sure to let you know if anything changes.
Still not planned?? 😵
I'm thankful we've moved to Atlassian -- it's got its moments and areas that could improve, but I find it far more developer friendly. Wrike seems to be stuck in the early 2000's.
Hi everyone! Just a quick note here that for now, the status remains Not Planned. We understand that it may be disappointing to you here, but our team has to concentrate on other improvements (we'll be sharing those updates here on the Community as usual). As my colleague Cansu mentioned above, our product team can't, unfortunately, commit to implementing all suggestions from you. At the same time, your feedback does play an important part in their decision-making on future releases (please check out this post to see which of your suggestions have been implemented or worked on last year). We thank you for all the product feedback that you've been sharing with us!
Andrew MacKenzie We are really sorry you've left Wrike. Thank you for all your feedback on this thread!
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
So Wrike just added Generative AI for text and NOT Markdown support?
This is laughable.
There's a reason other tools still prevail. I only use Wrike because my lab demands it, but we see it as a necessary evil - not a product we enjoy using.
I'm never going to use generative AI because I actually put factual information into Wrike and not just templates.
It's a cute feature, but how about adding something useful?
Shaurita, thankyou for bringing this request up again.
The lack of markdown support in Wrike is striking. And for goodness sake, it's not hard to add.
We use Wrike very heavily, and I have to say, overall we love it. It's a reliable and helpful tool.
When the people making the calls can find the resources to add support for Generative AI almost overnight, and yet find adding markdown so burdensome that it has to languish forever in the "not planned" category tells you that perhaps the decisions are made by people who market technology rather than by people who use technology.
Nobody in the chain of command appears to understand how odd the omission of markdown is. This has to mean that none of them are developers.
Thank you for bumping this thread, folks! Please rest assured your feedback is shared with our team.
We don't have an update for markdown support at the moment, but we'll let you know if we have news 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
Since the Wrike team appears not to understand how people use markdown in collaborative workflow, perhaps it's time to put us out of our misery?
Please move the status of this feature request. Either bin it as "Will Not Be Implemented", or move it to "Planned".
Having it stay as Not Planned for 6.5 years and:
is too much. And moving it to "Planned" does not commit you to doing it this year, it just sends the right signal to the user community.
We are bullish on Wrike. It solves lots of problems for us elegantly and reliably. The inability to add MD support is so at odds with everything else you're doing at the moment.
Hi Simon Taylor, thank you for your comment. The current status of this request is "Not planned", which indicates that the suggestion is unlikely to be part of the Product Team’s roadmap in the near future. However, changes can be implemented and, in that case, please rest assured that we will gladly inform you of the updates.
I can clearly see that this suggestion is a popular one, unfortunately, as Lisa and Cansu mentioned previously, not all ideas can be prioritized by our Product Team. However, the team is aware of the interest in this feature and we will keep passing your feedback to them 👍
Thank you for your understanding!
Hi @..., just so you know: my team has completed our sunset of Wrike. The lack of response to this thread and a few other extremely common and useful features available in almost every other product (it's 2023 and in Wrike we still can't edit our comments) eventually made the decision for us. While there are a few teams in our organization who still use it, we are actively encouraging migration to other platforms since we will no longer support working in it and it is no longer considered our enterprise solution for project management. Please pass that on to the Product Team.
Hello Juan,
A little baffled by your response.
I'm going to mull it over for a day or two.
Perhaps if I dig deeply enough, there's a way we can speak to your devs directly. They'll get it.
- Simon
Shadrock Roberts We're sorry to hear it. Please do let us know if there's anything else we can help you with.
Simon Taylor I'll share your feedback with your Account team, thank 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
Would _love_ to use markdown in Wrike task descriptions! +1
Should note that I'm also fond of using Wrike as a note-taking tool, but the lack of markdown slows this down significantly!
Noted Mary Buers, thanks for sharing your feedback here. We've shared it with the team 👍
Elaine Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Elaine Wrike Team member Become a Wrike expert with Wrike Discover
For some reason we did not check Markdown-Support before signing up - as we _assumed_ that it works. Because it works everywhere. The most ridiculous thing is: There's not even some other kind of monospace-font formatting. And Elaine and others can not explain me that it's hard to add. We are planning software development inside Wrike like 160 other orgs explained by registering, signing in and then upvoting (and those are just the ones that did care to go through the process). Come on, it's really not _that_ hard. At least make the baby-step and add a monospace font-option.
Hello Franz Josef Kaiser, welcome to the Community, and thank you for your feedback. I've passed your comment on to our Product Development Team.
I understand you find it frustrating that this feature has not been implemented yet, please rest assured that your feedback has been noted and we will keep you updated in case we have news about it.
Please, let us know if there is anything else we could help you with.
You blocked my most recent post on this topic. But perhaps your response to Franz shows that you team is starting to be concerned by how this feature request, (which you do not understand), is refusing to die.
At the risk of getting another post blocked can I ask that you please stop infantilizing us with phrases like 'feedback has been noted'. As far as I can tell you have no intention of adding this feature. I suspect this is because none of you monitoring these feature requests use markdown in your work and as a result you can't see what the fuss is about.
The solution is simple Juan, mark the feature request as planned.
Simon Taylor, we're confirming the status for this suggestion now and we'll let you know if we have an update 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 or Juan, can you please help with my request Id #1396887 ?
It's related to a post on this thread.
Hi everyone! We've now checked with the team - this idea remains in our Product team's backlog for now. We'll continue sharing your feedback and we'll let you know if there are any changes here.
Simon Taylor We have a content flagging system built in that automatically marks certain content as spam. Usually it happens when there are links to external resources added to comments or posts. I can see that's exactly what happened to the comment you tried posting. I can suggest posting it again but without the links.
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 you just unflag the post?
Wrike staff, to keep this ticket rolling along, (and as your devs maybe aware), there are wysiwyg editors that *generate* markdown.
The best of these that I've seen is stackedit. I can't enter URLs here, so just google "stackedit app" to see what I mean.
The user experience of a non-markdown user using such an interface is almost completely preserved. They are unaware that they are generating markdown. However, markdown savvy users can jump right in and get to work.
For instance, by manually entering markdown such as:
```javascript
if (window.addEventListener) {
window.addEventListener("load",ptLoadScrollRows, false);
} else if (window.attachEvent) {
window.attachEvent("onload",ptLoadScrollRows);
}
```
A Wrike ticket description (or comment) could contain a syntax colored code block sample. This is the sort of thing that the users on this thread are clamoring for.
Thanks for reposting Simon Taylor, we'll share your feedback with our 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
Happy 2024! Just showing up to say that yes, we would **still** love to have Markdown support (and it's funny that I keep typing out MD syntax and my brain just expects it to expand, because, well.. as has been mentioned, just about every other professional tool suite out there has implemented it).
I understand that it's probably a "little thing" but it kind of reinforces my hunch that Wrike is not a tool that's built to include technical and engineering teams in its scope of users (another example being GitHub sync as a paid add-on.. where many other PM tools include it as bog-standard).
I work on a small engineering team inside a larger organization, and to be completely frank, I currently feel like I use Wrike because I _have_ to, even though I can see how powerful it is under the hood. Features as simple as Markdown would go a long way toward warming us engineer-types up to the product, I reckon.