Exactly. There are some companies that go so overboard with Jira customizations that a single "create new issue" requires hitting page down three times to get to the end. And they arrive at that by adding a field here for the QA team, a field there for the Sales team...
In the end, you get a monster. New users will be exposed to that monster, not the vanilla Jira installation.
Fogbugz's interface prevents this kind of crazy customization and thus it acts as a defense against the craziness. For a custom workflow with Fogbugz you have to grab a plugin. To get my manager to install a plugin for JIRA took weeks (and I still never got access to the REST API or approval for one plugin months later). So Fogbugz is developer-friendly because it makes it harder for a manager to go in an lock things down and mess around. With JIRA, the micromanager seems to be bundled with JIRA... ;-)
As a PM, Pivotal Tracker (used in a previous life) is one of the best work-tools I've ever used.
I can never remember how to write code into comments or titles. It literally changes from product to product and yet all of the products orchestrate together so that if you do happen to use Stash, JIRA, Wiki, etc all together, then you encounter as many different markup languages as there are Atlassian products.
It really is hellish.
I hope there's some good reason why they can't provide one "comment markup" language to all applications.
Markdown embraces HTML, and so a WYSIWYG mode based around HTML is compatible with Markdown.
Markdown's weaknesses for table design, image insertion, and complex layouts is all handled by HTML and WYSIWYG tools that edit that directly.
That would have solved the Git scenario, and the Confluence scenario, whilst having a single highly predictable markup across all of their platforms.
The problem really stems not from these problems being addressed per product as if they existed independently of all other products. But that's a terrible approach, as few people buy just Confluence without JIRA or Stash, people buy Atlassian because a consistent suite should work better than many myriad tools that don't quite know how to interop. Atlassian's strength is the consistent and integrated approach, so the UX should be focused on strengthening that.
It does make sense when you think about the context though - JIRA pre-dates Markdown by two years (according to Wikipedia) and Markdown has only got really popular in the last five years. Back when Jira's text formatting came in, everybody was doing their own thing...
The out of the box user experience is the best I've seen for a web application. A robust yet easy to use 'search' feature is at the heart of many things, like the scrum and kanban boards, as well as widgets that can be put on your own personalize dashboard. You get a nice visual designer for setting up workflows, and you can easily create new fields for issue types and have workflow depend on those fields.
I also find Stash to be well thought out and easy to use if your use-case is a pull-request workflow tied to JIRA. Sometimes it's not intuitive how to navigate around if you're just trying to view source, but that's not the selling point. If you're trying to navigate source history, use your local source control client, that's what it's built for.