Is there any Markdown support for JIRA OnDemand?

[Yoni Samlan]

I don't want to have to force my team to learn a proprietary syntax for just one tool when every other tool we use speaks Markdown. The plugin I'm seeing is out of date and doesn't support OnDemand.

This also makes importing from our existing issue tracker (which uses Markdown) painful; switching costs are high  for us if we end up with existing ticket descriptions and comments mangled after the import.

[Stephen Deutsch]

I wrote the Render Markdown plugin for Confluence Cloud (OnDemand), so I could take a look at it.  It was pretty easy for Confluence, but no guarantee it will be so easy for JIRA.  Stay tuned...

[Lawrence Dol]

Any word on this?

[Patrick De Young]

I'll add a +1 for a markdown renderer in JIRA Cloud

[Lawrence Dol]

I'm curious... do people here not vote for things using the voting arrows on the question? Why are there seven "me too" "answers" on this thread instead of 7 additional votes for the question? I've noticed this a lot throughout the forum and am wondering if things work differently here than on StackOverflow et al. Someone even up voted this (non)answer.

[mhulse]

Do both! Just clicking an upvote seems silly when it's a feature that is sorely needed. 

[Sam Hall]

Voting and +1's on questions/answers here on the community forum don't help that much in terms of getting Atlassian's attention for a feature request.

I know they do look here, as we occasionally see employees commenting/answering, but I'm not sure how much weight is given to peoples "+1" answers & upvotes here.

Upvotes here really are supposed to be an indication of the usefulness and clarity of questions/answers, and give reputation points to the author.

If you want to support a feature request or raise a new one, then it's probably better to use https://jira.atlassian.com.

There are a number of 'Suggestion' issues there on the subject of markdown support in JIRA (Server and Cloud)

https://jira.atlassian.com/browse/JRA-61738

https://jira.atlassian.com/browse/JRA-37594

https://jira.atlassian.com/browse/JRA-44898

https://jira.atlassian.com/browse/JRA-39919

It's probably more effective to add your vote to one or all of those, if you haven't already. 

https://jira.atlassian.com is not a perfect feedback/suggestions mechanism (read about it, and some criticism, here), but it's a better place for feature votes than here.

[Charles Bandes]

Another vote for this, the idea that there's no way to format text in JIRA is driving my team crazy.

[Nar Kumar C_ - Narva Software]

Jira Cloud now supports Markdown format, see confirmation here: the new issue view.

I verified with my instance. Markdown format is recognized on the fly, not need to preview.

However, it is not saved as Markdown.

[mhulse]

UGH, GitHub-flavored markdown would be NICE! Markdown task lists anyone???? This is the problem with "marketplaces". It alleviates the pressure of companies from having to add good features like this to the core of their product.

Anyway, +1 from me. JIRA cloud and Bitbucket should both consistently use Markdown.

[Sunny]

+1, having to use 2 formatting styles in Bitbucket and JIRA makes it very confusing to managers and developers, it is a time waster for me to having another layer of context switch changing the writing style between JIRA and Bitbucket when they are supposed to be integrated - it certainly feels like they are disconnected and gets into the way. Atlassian, please provide a way for JIRA to migrate to markdown!

[Grant Kemp]

+10 for me - it would make integrating with other services much easier