Add support for markdown in description and other rich text fields

This is not shipped as per today. Inline support (while typing) of fences and other Markdown elements is not what people mean by supporting Markdown.

What we want is to not use the visual editor, which has so many issues, but be able to edit Markdown, preferrably with syntax highlight, and edit it as-is. When the note is viewed, it can render to HTML.

If it is still unclear what needs to be done, please spend a few minutes to look how it works in GitHub, GitLab, Linear and other tools. Fighting with the visual editor to produce something that looks at least not broken is really painful and time consuming.

EVERY app in our product development toolkit supports markdown except Aha! Having to use a mouse or take my hands off the keyboard is a time killer. Copy and Paste from other apps and then having to reformat is a huge time suck. For now I am just keeping our full user stories outside of Aha and linking to them...which means I still have to click the link button and copy and paste rather than just type [What is markdown](https://en.wikipedia.org/wiki/Markdown) like I do everywhere else.

And another year has gone by... now going on nearly FOUR years. The constant formatting issues when syncing with JIRA is becoming more hassle than its worth, never mind the inability to at least add a custom field that supports Markdown.

This is a must have. We started trying to develop more documentation in our products and it's impossibly slow to write content without Markdown and richer inline-editing. 

By reading through the ideas it seems that there has been no movement on a lot of items since 2-3 years.

Editing large texts with Markdown is much faster than using the menus.

Also make the default text font a little bigger to enhance readability.

Hi guys, we are also missing this feature. Any plans?
There is plenty of solutions to implement this, I don't see why this is taking so long.

Our team would like to adopt Aha and this feature would be a huge time-saver in order to actually enable seamless integration with Pivotal. Any updates?

Can we get an update on this? The default rich formatting causes issues with integration to adoption of Gherkin for documenting features and requirements through scenarios.

 +1

Please, markdown is already the standard across several other apps. Slack, Github..

The WYSIWYG is a mess for formating. Really, I cry out while doing edits. :(

+1 for reconsidering Markdown, especially in Ideas. -- our Ideas board internally is getting less use than we'd like because everyone is so used to being able to take their ideas from internal markdown files.

Hi Aha team - any updates on considering this? Having to create docs in other editors and then linking them into Aha is a sub-optimal experience. 

All tools we are using in combination with Aha (Asana, Slack) are using markdown and not having it wastes our PMs' time as they need to copy paste. Please consider revising your approach!

Exporting to Pivotal Tracker is problematic because Pivotal converts to markdown and it screws up the display in aha, particularly for bulleted lists. Please reconsider adding markdown, it's a huge pain not to have it!

A year has passed since this issue was closed, and there seems to be a number of users (including me) who would value an easier way to interact with your product from a content creation perspective.

Please reconsider this decision to not support some form of lightweight markup support into the product.

I am not a huge fan of Markdown, but it's an emerging standard, with more and more tools supporting it natively. I'm using it more frequently in a variety of places, so it's becoming annoying to switch out of markdown mode just to use Aha.

Especially GitHub-flavored markdown (e.g., tables) makes a product manager's job easier and faster.

would be really cool to have this feature, as it makes technical description much easier based on Markdown. 

+1 Markdown has somewhat become standard for writing on the web! Please add support

+1 as well, using Slack/Trello/Github etc, having to go back to a rich text editor is super awkward. Or at least let the user choose if they want the rich text or markdown.