Hacker News Reader

Comment by DrBazza | Hacker News Reader

I've never used a 'fast' version of Jira at any company I've worked for recently, self-hosted or cloud.

Search is atrocious.

UX is awful. It's 2023 and whatever version I'm using, it still doesn't accept markdown properly. And it's wysiwyg mode is broken most of the time too - try selecting text and setting it as code/preformatted and the entire comment, or description changes instead.

It's a jack of all trades, master of none.

It's funny, because I was one of the first adopters of it for Megabank, back in the early 00s, because it was fast (flat ui on top of our own Sybase instance), and its UI was simple.

View on HN

I remember a colleague attaching a screenshot of the text of a JIRA ticket to a ticket, and setting the ticket text to "read the text in the screenshot". Turns out JIRA crashed when he tried to save a ticket with a long text, with the text box deactivated so he couldn't copy it. His solution was to screenshot the text and use it instead of risk losing it.

I've used Jira at three different companies. A high-priority item during my first few days at any new instance is (re)creating a handful of "where the fuck did I see that?" queries to help me find things. Because Jira search is not intuitive, nor helpful.

Poor performance, terrible UX, welcome to modern software.

> Search is atrocious.

Atlassian search can best be described as: "I couldn't find what you're looking for, so here's a PDF".

Does Bugzilla even have both WYSIWYG and markdown?

I have no idea. I haven't used bugzilla in many, many years.

I'd be happy for neither though. Markdown's origins were such that you could write plaintext files that could not only be easily converted to html or some rich format, but were easy to read as-is.

Displaying the plain-text of an issue in fixed-width font would be fine.

Markdown is supported in the Mozilla fork, which is what upstream is being harmonised with.

Reply on news.ycombinator.com