Hacker News new | ask | show | jobs
by allset_ 1862 days ago
I don't like Jira that much, but this is just blatantly false.

> A cache-less refresh for me on a blazing fast dev machine takes between 3-10 minutes on a normal day, though it might only take 1m if the internet gods are feeling particularly merciful

I use Jira daily, it's nowhere near this bad. It's not fast, but pages load in about 5 seconds.

> changing ticket status can't be done without opening separate pages

You select the new state from the drop-down and set it. This is available through a few different routes/views.

> good luck finding it later

Their search looks through title and description, what else do you want?

> Backlogs inevitably evolve into infinite swamps that no one knows the full contents of.

If you let them, of course. If you don't close the tickets, what did you expect to happen?

1 comments

They probably meant seconds. A website that takes seconds to open is unusable.
I wish I was mistaken, but I do literally mean minutes. I've measured it with a stopwatch before.
Your internet or Jira server is at fault. I've worked in some places that had really dystopian Jira installations, but never seen stuff quite that bad.
Better tell your Jira admin that something is terribly borked with your company's install, then.