What gives, markdown has become (sort of) an industry standard, yet you fail to support it.
And for the record the help link for "Text Formatting Notation" is not markdown.
Information about the formatting can be found here: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all
If you want another standard, you can create a feature request (if it does not already exist).
Thanks for the response, and providing direction, I'm aware of the "Text Formatting Notation" in the link you provided.
I've since used the search box above, and (for others) there are additional plugins that support markdown. Just use the search.
However that still raises the issue as to _why_ its not a default, and what that bizarre text formatting is.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1 for real markdown. We write docs in markdown and when copying to Jira it simply doesn't work.
What a very, very odd thing to standardize on for Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What I recently came across that was most bizarre was the inconsistency of markdown support when in the text area.
Use case #1: Add a comment from an issue root URL, i.e., foo.com/issue/1
Use case #2: Add a comment while clicking "comment" when viewing an issue in a modal/dialog
You'll notice that both do not support the same type of markdown.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Saw that too - absolutely baffling.
And... this Markdown appears to be different than Confluence
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But... WHY?!? What PM thought custom text formatting would be a good idea?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ReplyI have imported all my Github issues to Jira and the markdown is a mess now. Any suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems obvious that Atlassian does not WANT to support Markdown. After all, a universally-supported document formatting scheme would make leaving Confluence easier.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have imported all my Github issues to Jira and the markdown is a mess. Any suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Considering they do support Markdown, depending on where you add it.
So, I'm not sure if that is a bug, that markdown is supported in some textarea's and not others, or that when you add markdown in supported textareas, then view the contents on a different, i.e., a URL vs. a "modal/dialog" you get no markdown support, or you get some markdown support.
...from what I'm gathering they will not support markdown, and instead are expecting us to use one of the plugins for markdown.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.