[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.

 

 

 

Upvote 128
65 comments
Spot On Innovative Approach Stellar Advice
Avatar

I am up for a Markdown feature 👍

I believe we all love Markdown. I guess GitHub Flavoured Markdown is desirable.

5
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

When should we expect this feature, is it planned ?

Plus it should support @user and #wrike_task automatic linking (like GitHub)

3
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Markdown is key.

3
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Please implement highlighting, this is not hard in 2019.

Please implement an edit function for the description. Making editing directly possible costs memory and sometimes leads to a frozen view. This would also solve the problem of not having to change syntax during editing. Whereby this is really easy to solve via prism.

2
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi everyone, I wanted to let you know that Markdown is not planned at the moment; I'll get back to you if that changes.

Having said that, we recently launched the updated Description Field, know it's possible to perform some actions without using your mouse. Please check out the article on our Help Center for more info.

Thanks for posting!

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

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I write notes in markdown no matter where they are written.  For me, I'm already writing my notes in markdown on wrike, it just doesn't know how to format it.  Then to print and publish I have to copy and paste the notes to another program.  Including a markdown interpreter would be wildly useful for a number of us that are used to markdown support pretty much everywhere.

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi, I also would like to see this prioritized.  I use tasks for meetings, and it's very useful for the flow to be able to quickly type the meeting notes with as many keyboard shortcuts as possible, such as the "three dash" that creates a section break in markdown.  And generally we use Wrike integrated with Jira, so code snippets, for starters, are a great benefit of markdown we are missing.  Generally a lot of other tools out there have this, what I'd consider, very basic feature, so really eager for you guys to get this implemented fully!

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi again, everyone! I've checked with the team, and this is not planned for 2020. Thank you for the feedback, our team has reviewed all of at, but right now Markdown doesn't fit in the roadmap along with other important product releases. We really appreciate your input, and I'll be checking with the team again later to see if anything changes. 

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

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice

Hello Lisa, is there an available roadmap so the community can see how is Wrike prioritizing its goals and evaluate if the path aimed at match with customer goals? Having such a roadmap would be great for customers to determine if their own teams should plane to move out of Wrike if our feature priorities diverge to drastically.

6
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

+1 for Markdown

2
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Hugh

Hi Mathieu LOVATO STUMPF GUNTZ, I'd recommend checking out this Product Feedback post about Product Roadmaps to add your support for this suggestion. This way, you will be kept posted on any changes or updates in relation to that idea.

Thank you for your input, Ryan Hanson!

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Markdown please!

3
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Hugh

Thank you for sharing your interest, Kenneth O!

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

+1! We were shocked when we couldn't get markdown going! If it's too expensive of a task to complete within, what, at least 2 years, maybe 3 since this has been requested ... I can't imagine the spaghetti that's being cooked in the backside.

Hope you guys can find time to get this in here soon! It is a nice solution for the less tech-savvy product-owners and managers and such -- at least, they seem to like it quite a bit over here! :thumbs-up:

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Reading between the lines Andrew MacKenzie, I get the impression that the staff think this is a good idea but they're constrained by owners who do not want to fund changes to the application. 

Of course if there was a public roadmap of changes this would show me that I'm wrong about this.

 

2
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thank you for the feedback! I've just checked with the team, and for now, there's no status change for this request. Any updates, I'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

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I feel some engineers prefer to use github issues or redmine instead of using Wrike. And I believe one of the big reasons for this is markdown!!!

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

+1 on this request. Markdown is essential to our workflow as it is everywhere in our workflow (Slack, Python, Jupyter notebooks, GitHub, StackOverflow, note taking, …). We are currently evaluating Wrike, but as of now, I don't see us fully adopting it without at least basic Markdown support. 

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Welcome to the Community Elias Mistler! Thank you for sharing your feedback here, and please let me know if you have any questions as you're evaluating Wrike 🙂

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

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

# Markdown please!

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thanks for supporting this suggestion Mike Burke, and welcome to the Community 🙋🏻‍♀️

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I work for a fairly good sized organization (5k employees globally w/ ~300 million USD budget) and we are considering leaving Wrike because of the antiquated commenting functionality. Seriously: we can't edit our comments... and we can't create hyperlinks in the comments (which seems odd because I can do that here just fine... kinda shows how important it is, huh?) or format quickly using Markdown. It's 2021, folks. I'd never used Wrike before, was pretty psyched because it looked good... but my God... it's like going back in time 10 years. From here on out I will be advocating as hard as I can for Jira, simply using Github, pretty much anything else... the fact that none of these are on the roadmap is insane. 

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Shadrock Roberts, welcome to the Community!

I'm sorry you're disappointed with the lack of this functionality. Please rest assured that all feedback here is regularly passed on to the Product team. Here's more info on what happens with Product Feedback after you post on the Community. 

Please let me know if I can help you with anything else. 

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

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

... product feedback ... it's kinda like Gabe from that episode of The Office where Dwight goes to Florida to interview for a position at Head-Office ...

... fluuuussssssshhhhhhhhh ...

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I agree, https://help.wrike.com/hc/en-us/profiles/1511787240841-Shadrock-Roberts - it seems the owners who do not want to fund changes to the application. This is a shame, it is a good environment and frankly the codebase deserves better owners. If it was open sourced I would have forked it and made the markdown changes myself months ago. It's not hard.

I think it's as simple as that, but if I'm wrong I'm sure someone from Wrike will correct me. After all, prospective new clients will see these comments and make their own judgements about the likely future mind-share being put into Wrike.

Lisa has a tough job, she has to put a upbeat spin on a company that has no roadmap, and apparently does very little development. And she does this with unfailing politeness.


 

 

2
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I have just created a full spec in Markdown and was looking in how in insert it into wrike...

Upvote.

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi again, everyone!

I wanted to share a little more detail on how our Product team works with your feedback to give some clarity here. 

Our team reviews a wide range of data, including user feedback, and Community suggestions/votes to determine what gets added to our Product roadmap. The team always aims to focus on implementing the functionality that will have the widest impact and benefit for the most users, and it's for this reason, that we can't implement all of the suggestions we receive via our various feedback channels.

You can check which Community suggestions have been implemented, are coming soon or are being researched by checking out our Product Feedback forum

For now, the team is focused on other priorities, so there is no scope to research Markdown support at the moment. However, this doesn’t mean that this will never be implemented and we will continue to share your feedback with the team and monitor the vote count here. If there are any changes to this, we'll be sure to let you know.

 We understand this is a highly sought-after functionality among some of our customers, and that this will be disappointing news for those of you who have been supporting this suggestion. Please rest assured that, as I mentioned above, we will continue to pass on your feedback regularly.

 Thank you for all of your contributions 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

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

OK folks, if you're following this thread, I think it's time to press this issue a bit harder.

It's clear from the post above that Citrix and Wrike don't seem to understand what's at play here. This is not merely a feature request like many of the others in the Product Feedback Forum. This is a request for Markdown in ticket descriptions, and Markdown is like Internet Plumbing! It simply has to be added.

Please help them to understand that this ticket is nothing less than their number 1 priority. 

What can you do? Well to start with, send this link to everyone who uses Wrike at your organization and get them to upvote the feature request. This is not easy, as the help.wrike.com domain sometimes asks you to login again even though you're already logged in to wrike. And sometimes this authentication fails when it shouldn't. But persevere and get those votes ticking along.

Secondly. do what I've done and reach out to your Wrike Customer Success Manager and book some time to talk to them. Ask them why this ticket is languishing and why there isn't a product roadmap for Wrike. 

Thirdly, post again here.     

4
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

+1...please do consider. Thanks.

2
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Critical for comments and description.

We could be so much more productive to have the possibility to also copy parts of documentations etc.

 

+1 here too

2
Comment actions Permalink

Folllowing List for Post: [Status: Not planned] Markdown formatting in Description field
[this list is visible for admins and agents only]

Top
Didn’t find what you were looking for? Write new post