I concur: editing content is faster in Markdown because you can indicate formatting without interrupting your typing (and train of thought). Additionally, this makes it easier for developers who are already familiar with Markdown.

Great idea, would be very useful. I'd put the editor preference in account settings. 

+1

Would also help with pasting formatted text from elsewhere -- quite a lot of destinations & editors use Markdown primarily these days (Github, Slack (almost), iA Writer, Ghost, etc.), so transferring snippets would be easier with this available.

+1

Wysiwyg is not fast. Support for markdown is essential for speedier workflows. Please consider implementation.

Yes, please implement this, as it's way more developer friendly!

Most PMs are used to markdown and also having it lets us sell Aha to engineers. Most people come from the likes of Trello and in our case we use the integration deeply. 
WYSIWYG is definitely not fast for us I'm afraid

WISIWIG is neither flexible enough or fast enough. Markdown would be great because of its wide adoption by development teams.

+1 for this - WYSIWYG is just not powerful enough for me. Nor is it what i use in other contexts

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

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

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

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.

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.

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!

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!

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. 

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

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

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.

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?

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.

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

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