Jira forcing users to give write access to GitHub and drive

Re:Jira forcing users to give write access to GitHub and drive by sgt on Saturday May 16, 2020 @10:39AM (#23203726)

The most annoying thing on a daily basis for me with JIRA is how slow it is. It seems like a cloud hosted one and a self hosted one are are equally slow. By slow I don't mean abysmally slow, but every action typically takes 500-750 ms. And if you use it regularly, that makes doing stuff a chore.

[ Parent | on HN ]

Re:Jira forcing users to give write access to GitHub and drive by colinjoy on Saturday May 16, 2020 @11:46AM (#23204353)

> The most annoying thing on a daily basis for me with JIRA is how slow it is.

I can't comment on the cloud offering, but I agree that the performance and resource consumption of the self hosted Jira is not great either.

To me it is not quite slow enough to negatively offset its usefulness. Perhaps I am also too used to working with even slower web applications to really take note of anything < 1s ;)

Again, to double down on my previous point: where it can get very slow very fast, is for ill configured systems... i.e. when running unnecessary permission checks on very large groups.

[ Parent | on HN ]

Re:Jira forcing users to give write access to GitHub and drive by imglorp on Saturday May 16, 2020 @12:22PM (#23204760)

The 300+ mb page load to see one sentence of text on an issue is a big factor.

[ Parent | on HN ]

Re:Jira forcing users to give write access to GitHub and drive by Maxion on Saturday May 16, 2020 @10:55AM (#23203871)

Surely 750ms is already in the absurdly slow category?

[ Parent | on HN ]

Re:Jira forcing users to give write access to GitHub and drive by dheera on Saturday May 16, 2020 @12:29PM (#23204833)

In general UIs should always respond in 100ms or less. For lord's sake GMail takes a full 3s which is slower than any desktop client took in 2000. Somehow people think it is okay to make your page slower because "ooh aah AJAX" and "oh I can just add a spinner" or something ...

Back when I used pine it just loaded instantly! No spinner, no splash screen, no progress bar needed.

And don't give me that "oh but it's in the cloud" crap -- the cloud isn't an excuse to be slow when I have a 300mbps downlink with sub-10ms ping times to headquarters and datacenters of these companies.

[ Parent | on HN ]

Re:Jira forcing users to give write access to GitHub and drive by sgt on Saturday May 16, 2020 @11:03AM (#23203932)

If you're used to fast paced web apps like Trello, yes.

[ Parent | on HN ]

Re:Jira forcing users to give write access to GitHub and drive by sjwright on Saturday May 16, 2020 @11:31AM (#23204202)

It begs the question what could it possibly be doing to take half a second of wall time. That’s an eternity for a modern computer.

[ Parent | on HN ]

Re:Jira forcing users to give write access to GitHub and drive by iforgotpassword on Saturday May 16, 2020 @11:10AM (#23204001)

So it's not just me. I never used it professionally, but a handful of open source projects decided to use it. It felt like a slow, convoluted process to just open a bug report.

[ Parent | on HN ]

Re:Jira forcing users to give write access to GitHub and drive by colinjoy on Saturday May 16, 2020 @11:29AM (#23204186)

What about it caused this feeling?

Creating a bug report with Jira can be as simple as filling in a summary and a (optional) description, then click submit. If you use issue collectors, you may not even need an account in the system or directly access the Jira application to report the issue.

[ Parent | on HN ]

Re:Jira forcing users to give write access to GitHub and drive by 0xffff2 on Saturday May 16, 2020 @12:23PM (#23204770)

When each click takes 500-1000ms to respond, it doesn't matter how simple the workflow is.

[ Parent | on HN ]