Add support for markdown in description and other rich text fields

Are there any plans to add support for markdown or other formatting languages in the text editor? These can be much faster when doing a lot of composition editing than using the menu based options.

  • Jonathan Berg
  • Jan 23 2015
  • Likely to implement
Release time frame
  • Attach files
  • Brian Dailey commented
    March 11, 2015 15:55

    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.

  • Guest commented
    March 11, 2015 15:56

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

  • Nauman Mithani commented
    October 05, 2015 17:22


  • Andrew Weeks commented
    October 31, 2015 19:42

    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.

  • Chip Ray commented
    March 09, 2016 17:28


  • Josh Whitman commented
    April 08, 2016 18:11

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

  • Dennis Micky Jensen commented
    April 12, 2016 10:05

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

  • Guest commented
    April 19, 2016 07:47

    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

  • David Clark commented
    June 01, 2016 15:10

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

  • Liora commented
    June 16, 2016 01:05

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

  • Martin R commented
    July 28, 2016 11:28

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

  • Shivi Aggarwal commented
    August 06, 2016 18:32

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

  • Till Harnos commented
    October 18, 2016 10:53

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

  • Marco N. commented
    December 19, 2016 18:56

    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.

  • Jared Morgan commented
    December 21, 2016 04:58

    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.

  • Liora commented
    January 11, 2017 17:11

    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!

  • Chiara McPhee commented
    July 18, 2017 18:47

    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!

  • Liz Yee commented
    July 18, 2017 18:50

    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. 

  • Nathan Dintenfass commented
    September 05, 2017 18:41

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

  • Arthur Soares commented
    October 25, 2017 14:07

    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. :(

  • Adam Weinstock commented
    November 01, 2017 19:37


  • David Vins commented
    12 Jan 03:51

    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.

  • Jesus Figueroa commented
    06 Mar 15:01

    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?

  • Thiago Benvenuto commented
    15 Mar 21:32

    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.

  • Juan Manuel Arias commented
    15 Mar 21:34

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

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

  • rahul sharma commented
    25 May 17:14

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