I don't want to have to force my team to learn a proprietary syntax for just one tool when every other tool we use speaks Markdown. The plugin I'm seeing is out of date and doesn't support OnDemand.
This also makes importing from our existing issue tracker (which uses Markdown) painful; switching costs are high for us if we end up with existing ticket descriptions and comments mangled after the import.
I'm curious... do people here not vote for things using the voting arrows on the question? Why are there seven "me too" "answers" on this thread instead of 7 additional votes for the question? I've noticed this a lot throughout the forum and am wondering if things work differently here than on StackOverflow et al. Someone even up voted this (non)answer.
Voting and +1's on questions/answers here on the community forum don't help that much in terms of getting Atlassian's attention for a feature request.
I know they do look here, as we occasionally see employees commenting/answering, but I'm not sure how much weight is given to peoples "+1" answers & upvotes here.
Upvotes here really are supposed to be an indication of the usefulness and clarity of questions/answers, and give reputation points to the author.
If you want to support a feature request or raise a new one, then it's probably better to use https://jira.atlassian.com.
There are a number of 'Suggestion' issues there on the subject of markdown support in JIRA (Server and Cloud)
It's probably more effective to add your vote to one or all of those, if you haven't already.
+1, having to use 2 formatting styles in Bitbucket and JIRA makes it very confusing to managers and developers, it is a time waster for me to having another layer of context switch changing the writing style between JIRA and Bitbucket when they are supposed to be integrated - it certainly feels like they are disconnected and gets into the way. Atlassian, please provide a way for JIRA to migrate to markdown!
UGH, GitHub-flavored markdown would be NICE! Markdown task lists anyone???? This is the problem with "marketplaces". It alleviates the pressure of companies from having to add good features like this to the core of their product.
Anyway, +1 from me. JIRA cloud and Bitbucket should both consistently use Markdown.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs