The honest answer is partly, and not in the way most people mean. Jira Cloud will convert some Markdown while you type it, but it never stores Markdown, and it has no mode where you edit an issue as a plain Markdown document.
Jira Cloud keeps rich content in Atlassian Document Format (ADF): a JSON tree of
nodes, not text. A heading is not the characters ## Title; it is a
heading node with a level. Nothing you type is kept as Markdown, so there is no
"show me the Markdown source" view to switch to.
This one fact explains almost every surprise below.
The Cloud editor watches your keystrokes and swaps recognised patterns for real nodes.
Type ## and a space and you get a heading: but what is saved is the heading
node, and the characters you typed are gone.
This is input assistance. It fires on the pattern you are typing at that moment.
h1., {code}), and it is a different language from Markdown.
The Cloud editor does not accept it.There is a long-running request for a plain Markdown editor, JRACLOUD-72631. As of 18 August 2026 it has 1,742 votes and 509 watchers, it was filed in July 2019, and its status is Future Consideration: Atlassian's label for "not on the roadmap, may be revisited". So this is worth planning around rather than waiting on.
These notes are written by sellerkit. We build a Markdown editor app for Jira (below), which is why we had to work all of this out in the first place.
Everything above this box works whether or not you install anything. Where a workaround is enough, we say so.