All the current Markdown posts seem to be locked.
I take notes in Sublime Text as they happen, in Markdown. When I then copy & paste them into Asana for task tracking, I have to manually reformat links, unordered lists, block quotes, fenced code… Why doesn’t Asana just support CommonMark fully? It should be a drop-in plugin, it’s available in pretty much every codebase…
3 Likes
+1 totally agree.
Don’t forget to upvote your own post 
2 Likes
This is thing about Markdown and how it is continuously dismissed is totally silly. Just dropping by to support this request, again.
Also to add that Markdown support should not only mean parsing a few syntax elements from the text and immediately converting to the RICH equivalent, as if they were “shortcuts” (as they are called in the docs)
No. Supporting Markdown means: letting the user enter plain text that does not change at all while being typed, and then parsing the text as Markdown and formatting it accordingly when it is rendered.
To prevent confusing users that are already familiar with ASANA text formatting, I would suggest that this is optional, and let the users activate or deactivate it depending on their preferences like Slack does
1 Like
Yes! The way Slack does it is great. In my experience, people are either RTF people or MD people, not a mix of both. So letting me set my perference would be ideal.
However, unlike Slack, it’d be neat if Asana implemented pure CommonMark 
1 Like
Upvoting. This is needed.
1 Like
Markdown support. This means being able to dump in an entire markdown document if someone really wanted to, and it be formatted using standard markdown (e.g common mark spec 2).
Adding support for bold, italic, link and lists in a similar but not quite the same way as standard markdown was not markdown support, it was just a step in that direction.
Markdown support should include:
Full support for h1 - h5 tags using the hashtag
Blockquotes
Code tags (with support for language specification)
Thematic breakes
Tables
plus all the standard, widely used items on the spec linked above
3 Likes
How can be possible that it’s been more than 2 years since the “markdown release” and haven’t been able to improve it yet? I believe is the feature with most votes. Please dev team, take a bit of time to complete this, should not be that hard.
1 Like
My team also really needs this feature. Being unable to include code or logs in a legible way inside issues is a total non-starter. Ironically I can post code in this forum!
package asana
import (
"fmt"
)
func main() {
fmt.Println("Hello, Markdown!")
}
3 Likes
Bumping this along 
@asana we NEED this feature (full markdown support).
Is there an update on this item? This is sorely needed feature. Microsoft Teams supports quote blocks, but I’d much rather use Asana 
It would be beneficial if Markdown format were consistently supported in all aspects, similar to YAML. Imagine how wonderful it would be to create a Markdown file and upload it without any api intervention. Additionally, this allow automation process for the batch retrieval of Markdown files from a directory, it would greatly enhance efficiency.