Alex Kuznetsov: Hey Alex! Thanks for the feedback, we'll allow you to use source markdown in the future. This most likely will be implemented with our new editor features in May.

Zeb: Awesome!

Zeb: Any update on this, such as a feature request I could track?

One of the biggest pains for me as a developer is the fact that most of the PM tools I've worked with seem to favor a formatted text approach, where markdown symbols are converted in-place to their formatted version.

While I understand that outside of the programming circle, text in this format could be very confusing for people, since they'd be completely unfamiliar with markdown (vs more familiar with rich text editors), as a developer it's one of my biggest pains, as it makes everything so much harder for me.

For example, take this sentence:

"We should deprecate in favor of ."

When typing this sentence, when I close the code backticks and press space, they'll be removed and the text in between set to be formatted as code.

Right off the bat that has a problem - The sentence ends with a full stop, not a space, and so for it to be converted I actually have press space before the full stop, and then remove that space.

This leads onto the second problem: If I remove that full stop, I'm in text that's being formatted as code. While "inside" this text, any more text I type will also be formatted with code. The problem with that is that b/c I'm at the end of the sentence, I can't move "out" of the text formatted with code - I have to instead add some arbitrary text to be selected so I can disable the code formatting.

All of this is painful for me b/c this stuff is half of the documentation I write - the other half is written in MD files, or on github issues, where I don't have to keep stopping and starting to fix this little bits, and it all just reminds of how markdown is meant to be used.

Finally, the biggest thing for me is the ability to copy and paste - If I was to paste that above sentence into a README file, I'd have to re-add the formatting.

All in all, I'm pretty excited if you're really going to add support for source markdown (which I'm hoping really does mean something like the github preview/source editor), and doubly so if its anytime soon.

Like I've said, this is honestly one of my biggest problems that I have with a of tools, including platforms like BitBucket, JIRA, Trello, and Confluence.

Let me know if there's anything I can do to help get this as a feature on Clickup - I can provide gifs of the pains I've mentioned above in action, if you'd like clarification (they're rather hard to describe).

I did see this feature request, that has a comment at the very bottom that mirrors my request.

(I do find it a bit ironic that this comment editor is actually a perfect example of what I'd like)

Gareth Jones: Hey Gareth! If you could, please add your comment to this post: https://feedback.clickup.com/feature-requests/p/use-a-more-common-markdown-flavor

Also a Loom (or video) would be super helpful for the product team when we consider this.

We are implementing an updated text editor (for the real-time collaboration like Google docs where you can highlight text). We'll consider updating it for something like your request during that time.

Zeb: No problem - I've done as you requested, and included a video showcasing one of the frustrations I described.

Gareth Jones: Thanks Gareth! I've also added that comment internally to our task for the updated quill editor.

Zeb: did you scrap that feature? I'm currently evaluating Clickup's docs feature and in my use case I will have to paste hundreds of markdown files in to the document structure. However, pasting markdown into a page doesn't work.

Oscar: We added this to the scope of our "importing docs" features coming soon. Right now it's planned for December so that you can import (and export) docs in different formats. This would indeed allow you to import markdown but it's not currently available unfortunately