+1 for implementing markdown in the comments. 

I was actually just now was writing in markdown in the comments in my project, trying to find out why it doesn't work as I discovered  to my astonishment that there's no support for it ???

Please reconsider adding markdown support in Jira comments - this would simplify many issues regarding formatting

How is this still not implemented in 2023 for an expensive paid product, when Markdown is now the de facto standard and it is so readily available on free platforms and applications from GitLab to VS Code?  This really goes to show just how Atlassian's priorities are backwards.  There really is no excuse for not providing this built-in when there are so many FOSS implementations of Markdown parsers and converters out there.  For Java, there is CommonMark, Flexmark, MarkdownJ, and others, all three of which are permissively licensed.

dt

No movement on this??

Please reconsider! This affects developers' productivity. How come Jira Cloud has this feature, but Jira Data Center does not???

Not even in 2010 it made sense.

While this decision might make sense in 2010 I cannot understand that in 2021 we still get no official markdown support in Jira (server). All major Git repository providers, all modern IDEs, all modern Chat tools, etc. support Markdown. Even your own tools like Confluence and Bitbucket support it. It seems to me that Jira is the only development tool that does not support markdown, making it a kind of dinosaur - and you might know what happened to the dinosaurs in the past.

Is Atlassian our of their mids? It's 2020 and Jira doesn't support Markdown, while all other Atlassian tools do support it? This is ridiculous.

Markdown would simplify so much, if it was allowed in comments. Please reconsider.

Please reconsider. Help us and standarise to help yourself, anyone using markup at all, markdown is the standard. JRASERVER-39919 seems to be the ticket for this.

Yes, please reconsider this now, Atlassian! JIRA will be the only tool with an alien markup language not compatible with Confluence and Bitbucket.

Any plans to re-consider?

Confluence is finally moving in the right direction:

"Looking for Markup? We're removing all markup from the editor, and switching to markdown instead. You can still use markup in other parts of Confluence" [SOURCE

Different markup languages for Jira and BitBucket is the biggest usability issue for Atlassian products

Just doing my programmerly duty to note here that JIRA markup blows in comparison to Markdown, and your unwillingness to support what is basically the lingua franca of the web drives me to further hate using your product on a daily basis.

Please try out our Markdown plugin for JIRA (https://marketplace.atlassian.com/plugins/com.fulstech.jira-gherkin-custom-field/server/reviews). It supports custom fields, system fields, and comments. If you have any suggestions or requests, feel free to share here https://github.com/fulstech/markin/issues.

cannot delete comment

There is now a bounty open to get the markdown add-in fixed for JIRA 6. See here:

https://www.bountysource.com/issues/11875358-jira-6-support

Throwing $10 at this would definitely help!

philipp.austermann There is an open ticket for this. I guess all we have the power to do at this point is to vote up this issue: JRA-39919

Absolutely no Markdown support in Jira 6 (the aforementioned plugin only works up to JIRA 5.2.11) !?

I am struggling to grasp any advantage to have JIRA markup language here (JIRA) and Markdown perfectly at work there (Stash). As such, i am seconding @jason - many developers already "speak" markdown very well - why not simply give admins the ability to switch to markdown by default (or even better, have automatic recognition which markup language is used)

Plugin I mean

Is there n addin on marketplace to do this?

Please reopen. Markdown is much more widely used than the JIRA/Confluence markup language.

+1 for Markdown.
Please, reopen this issue as the plugin does not work for JIRA 6 (we also would like native support).
See: https://bitbucket.org/bbaker/atlassian-markdown/issue/9/jira-6-support

Stash supports markdown too.

We're considering migrating over to the Atlassian stack from our GitLab/Jenkins combo, and nobody on my team is going to want to learn a new syntax for formatting messages when Markdown is used by almost every other piece of software out there.

Oh, and it should be mentioned that the plugin that caused this to be closed doesn't work with JIRA 6.

Agreed. Please reopen.

+1 for Markdown. We don't use Confluence so we don't really want to be forced to use the Confluence style if we don't use it anywhere else.

+1 for extending the "Markdown for JIRA plugin" to work for OnDemand instances

+1 for Markdown, at least as a plugin.

Please reopen this, so people can vote on it. Also, it would be a good idea to check peoples' opinion regarding if they would prefer on having the markdown syntax as default in Jira instead of the confluence-ish one which btw was kinda deprecated from Confluence.

Just to check others opinions I created a poll http://poll.fm/4cwrs - obviously this should end-up in another page than this because otherwise it would be biased. I will put this on the 3 Jira instance banners so we will see some results soon.

+1 for Markdown support for JIRA OnDemand.

+1

We just switched to JIRA OnDemand and I can't believe there isn't an option to use Markdown... We imported hundreds of tasks from a different tool into JIRA and now all the Markdown formatting in descriptions & comments is not only useless, but messy.

From what I've seen, GitHub flavoured markdown is superior to wiki-markup in every way (wiki-markup doesn't have syntax highlighting??). I can't imagine it would even be very difficult to integrate into JIRA considering the open-source community has already done 90% of the work for you...

sigh... Sorry for the rant. It's just that your reasoning for not adding this feature doesn't make much sense.

:+1: for this

now that we use github extensively, we'd really like to do:

```ruby
class Foo
def initialize
@bar = nil
end
end
```

and have it work similarly.

@Jake I just assumed Atlassian have a commercial interest to promote their wiki markup over other markup right?

So, because you've closed this, it means:

1. No one will really see this request
2. You can't vote on it, so how exactly are you working out popularity?

The open source plugin doesn't work for OnDemand instances - so not totally sure why it's been given as the solution.

Just for the record that field renderer and wiki macro support have always been pluggable in JIRA. These plugin points are what I used in the new Markdown plugin for JIRA

I would vote for it being pluggable. That certainly makes sense.

Is there a JIRA case for this already or do we need to make one?

Too bad Jira isn't open source

@Borek for sure. Got a Jira for it?

Certainly the text parser should be pluggable. JIRA wiki format is quite fragile, not properly documented, it's not very easy to use etc. Better than nothing but Markdown is miles better.

I wonder if instead of campaigning for this, perhaps we should campaign for a new feature, make the comment parsing a replaceable plugin. That way we could create our own plugin for markdown?

Guys, since voting is disabled, at least watch the issue so they can gauge interest...

Yes, please support markdown! It's a de-facto standard.

Apparently Confluence 4.0 has removed wiki syntax, so basically now it means Jira just has its own wiki syntax. It seems to me that the reason this ticket was closed is no longer valid, and it should be considered again.

Markdown major advantages over Confluence-style:

• The markup itself is easily readable as text (in fact the primary goal of markdown is to not look like it's a markup syntax)
• It is popular and thus well-known by many people

I recognize that long-time Jira and Confluence users (and likely, Atlassian employees) don't get this since they're familiar with and used to the Confluence syntax. As a relatively new Jira user, frankly, I think the syntax is terrible. It is not intuitive, and it looks terrible plain-text. Even after using Jira for 5 months, I constantly have to edit things because the syntax didn't do what I expected.

I would love to see this reopened, or a new issue created to have the ability for a plugin to provide the wiki rendering engine.

Markdown has become so prevalent for lightweight text formatting on the web that it seems silly to stick with something homegrown just because it's already there. Supporting it in both Jira comments and Confluence page editing would make using both of those tools much easier due to the abundance of editors/formattings/previewers for Markdown.

markdown is indeed a lot easier to read and understand. Especially since it is well readable even without html knowledge. It would be nice to have an option to interpret a certain page with different engines. like confluence style, markdown etc ...

Im sad that this has been dismissed outright, and we cant even vote on it! Surely having the option of using Markdown would be an extra feature that might attract more customers. I have dismissed using JIRA outright as it does not allow Markdown.

That's a shame. Markdown is very much easier to read, (visually) parse, and work with in general, as well as introduce newcomers to.

We currently have Confluence style wiki-markup so we do not plan to introduce another style into JIRA.