New Issue Modal: Manually Typed Markdown Doesn't Render Following Issue Created

[Michael Handschuh]

This is bizarre. When creating a new story markdown never works. I naturally type in markdown, so I end up typing up my story description and creating the issue, but then I go to look at the issue and it's all just plain text not being rendered as markdown. For my short code segments (single backtick syntax), I need to go to each one, delete the last backtick and then type a new backtick and voila, it's real-time mark-down-ifier kicks in and renders it properly. It's worse with code blocks (triple backtick fence). I need to copy the contents of the codeblock, type my fence, the real-time markdowner kicks in and then I can paste into the special code fence section.

Is this normal behavior? Is there a setting to let me just type markdown w/out having the view update to show rendered markdown in real-time? Is there a way to create new issues using markdown and not have to edit EVERY single issue I create?

After creating my screenshots I realized that _some_ markdown works, such as bold and a numbered list was created due to the `#` character (but it was inside a code fence). Luckily the emoticon rendered! It's also worth mentioning that if I use the buttons at the top to generate stuff, for example, a fenced code block, that *does* work... but not when just typing away like a markdown maniac.

Here's a related issue, someone seeking to disable the real-time markdown rendering (which would be AWESOME!).

https://community.atlassian.com/t5/Jira-Software-questions/How-to-turn-off-new-Jira-issue-editor-markdown-rendering/qaq-p/1009547

I'm actually wondering if the little markdown I've provided in this post will render... we shall see!

Screen shots (I was *wrong* about none the markdown rendering):

[Brian DeShong]

Please address this, Atlassian!  Having this corrected would make for a decent time savings and quality of life improvement.

[Tyler Brown]

Please fix this, Atlassian!

It was painful enough to figure out how to make the "default text renderer" (the one that enables markdown) actually be the default (cuz it was not in a brand new account)... once I finally did that it's pretty great, BUT...

1. It just doesn't work in the Create Issue modal - I have to first create, and then go edit it.

2. We're all software people here used to using github - we want to write in actual markdown and _then_ see the rendered result after saving. The WYSIWYG style is just annoying to devs.

[Jason Yu]

I don't understand why there is a complicate rendered editor but a simple markdown input box is missing.

[Luis Nachtigall]

This is still a issue for us.

[Michael Handschuh]

It's a shame support doesn't even acknowledge these tickets at all...

[Rupert Chen]

I am also highly interested in this getting addressed. For now, I've resorted to dropping in a place holder "TODO" just so I can save since once I attempt to edit the issue, the editor accepts markdown as expected.

[Michael Handschuh]

It looks like this forum suffers from the same bug, manually entered markdown doesn't get rendered after submit. Although, this forum perhaps has it better (or worse depending on how you look at it) -- since at least _none_ of it rendered, but in jira _some_ of it renders, making for a really wonky experience.