Hacker News new | ask | show | jobs
by jpalomaki 1457 days ago
I like both JIRA and Confluence. I think many bad feelings towards JIRA are actually related to bad configuration. Like customizing the issues to add too many mandatory fields or creating a process that does not really match how people are working in practise.

JIRA configuration is pain. Unless you are large enough to afford a dedicated JIRA admin, it would likely make sense to just pay for somebody once in a while to implement the stuff you want.

3 comments

All my bad feelings are almost completely related to the horrible search, terrible UI and the hilariously bad performance of the app. The web app has two completely different markdown adjacent formats that are not compatible with each other so you get text rendered one way when you create a ticket and another when you edit it later. Search is almost never helpful beyond finding recent tickets. Multiple pages take so long to load abs the new UI is so laggy and busted
I was keeping a list at a previous company:

- default text size is too small, text block widths are often not constrained enough getting the "slashdot unreadability effect"

- 0.5s+ lag when clicking any textbox

- 1s+ lag when clicking any dropdown

- 1s+ lag delay when grabbing and trying to drag-and-drop to reorder items in the backlog

- 2s delay when clicking in an issue in the backlog before the loading starts (add about 2s more for the loading itself)

- "Link issue" using a hyperlink icon. The whole idea of using the word "link" to talk about related issues without spending some time to think whether that's really confusing with hyperlinking

- Error messages about what "might" be wrong with things rather than what is actually wrong: "We couldn't save your comment, it might be empty or have invalid formatting". Well which one is it? Did you really have trouble deciding whether my comment is empty or not? Be specific and tell me what exactly is wrong, or do you want me to binary-search / bisect myself?

I think most of the issues can be fixed by completely rewriting the frontend.

You've missed my main one, which is really hard to copy and paste issue numbers.

Normally have to ctrl+click to open an issue in a new window, then select the key from the browser's URL field.

> bad configuration

I briefly worked at a company with 1,000+ devs. They all used a single locked down Jira configuration.

It had something like 30 columns - it was almost totally unreadable.