3 ms·
Native support for Markdown in comments would be a good win. In the Atlassian ecosystem, the markup languages are constrained by the following equation: JI
by papaf 6y ago
Native support for Markdown in comments would be a good win.
In the Atlassian ecosystem, the markup languages are constrained by the following equation:
JIRA Markup != Confluence Markup != Bitbucket Markup
- smcl 6y agoAlso even just within JIRA it can be inconsistent - I realised that to make monospaced text you need to use: - backticks when creating a Jira ticket, e.g. `hello` - double curly-braces when editing a Jira ticket, e.g. {{hello}} ... or vice versa. I cannot honestly remember which way round it is. Of the complaints I have about Jira this is probably the least annoying - but it really shows how irritating the product is.
- julenx 6y agoI haven't used JIRA recently, but as far as I remember the difference existed because they were rolling out a "new" editor, which was active when editing tickets, but wasn't available when creating new ones. I remember this caused me some data corruption when editing a comment created with the old version of the editor using the new editor. It was a mess.
- smcl 6y agoThis honestly would not surprise me. I’m kinda glad there’s an explanation, but I’m also annoyed it’s a stupid one
- Phelinofist 6y agoCannot confirm, I always create issues with {{...}}
- smcl 6y ago"or vice versa. I cannot honestly remember which way round it is"
- nicwolff 6y agoIt's vice versa, and this may be a small thing but it's my top example of how little they care about usability or product quality!
- smcl 6y agoOne hundred percent - it’s such a little thing, but as a developer it says a lot about the code beneath the product