nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why is markdown different between JIRA and Stash?

Mike Kessler

markdownstash.png

markdownjira.png

Same company, similar looking interface, different markdown. What's the rationale behind making the markdown different?

markdownstash.png

markdownjira.png

Screen Shot 2015-02-26 at 9.23.53 AM.png

Screen Shot 2015-02-26 at 9.25.00 AM.png

Accepted answers

Marcin_nf84fv

The rationale has been addressed previously in https://jira.atlassian.com/browse/STASH-4385, but essentially the rationale is that Stash uses Markdown to be consistent with other software development tools.

All comments

Pedro Cora

Mike,

JIRA does not use Markdown. It uses it's own Wiki Markup: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all

-- Pedro

Mike Kessler

Ok so it's not called Markdown, but that doesn't take away from the fact that there are two separate interfaces to accomplish relatively the same thing. Why would Atlassian choose to handle things differently between the applications? I'm most interested in the philosophy behind that decision.

Marcin_nf84fv

MattS

JIRA uses a suspect of what confluence used to use. Stash was written later when a different markup language was more popular

MattS

Subset not suspect

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

bitbucket-server

markdown