The thing I dislike most about Atlassian products is that each of them has a completely different formatting engine and markup syntax. You’d think they’d be consistent but noooo
Atlassian doesn’t even have consistency within single products! I’m using Jira Cloud at work, and while most fields support markdown (e.g. three backticks to start a code block) there are a few that only support Jira’s own notation (e.g. {code} to start a code block). It’s always infuriating when I type some markdown in one of the fields that doesn’t support it for some inexplicable reason.
The thing I dislike most about Atlassian products is that each of them has a completely different formatting engine and markup syntax. You’d think they’d be consistent but noooo
Atlassian doesn’t even have consistency within single products! I’m using Jira Cloud at work, and while most fields support markdown (e.g. three backticks to start a code block) there are a few that only support Jira’s own notation (e.g.
{code}to start a code block). It’s always infuriating when I type some markdown in one of the fields that doesn’t support it for some inexplicable reason.In Confluence… the same emojis look different on page title on the sidebar vs the body. Two different font families.
It’s incredible.
Try to do any formatting more complex than none at all in Confluence. It just gets polluted with invisible markup and changes styling randomly.
The thing I dislike about Atlassian is everything from Atlassian
Thankfully these days I spend most of my time in Confluence, which supports Markdown
Both Bitbucket and Confluence partially support Markdown, but they implement it in different ways, which is maddening.