Back in 2018 I worked for a client that required we used Jira. It was so slow that the project manager set everything up in Excel during our planning meetings. After the meeting she would manually transfer it to Jira. She spent most of her time doing this. Each click in the interface took multiple seconds to respond, so it was impossible to get into a flow.
Hm. While I'm not even remotely excited by Jira (or any other PM software), I've never noticed it being that bad. Annoying? Absolutely! But not that painfully slow.
Were some extras installed? Or is this one of those tools that needs a highly performant network?
The problem with Jira (and other tools) is it inevitably gets too many customizations: extra fields, plugins, mandatory workflows, etc. Instead of becoming a tool to manage work, it starts getting in the way of real work and becomes work itself.
I've seen on perm Jira at large companies get that slow. I'm not sure if it's the plugins or just the company being stingy on hardware.
Yeah it’s probably both. Underfunded IT department, probably one or two people who aren’t allowed to say no.
I can easily believe either, but I am still curious what the failure mode(s) is (/are).
Underconfigured hardware and old installations neglected are the ones I've encountered.
Large numbers of custom workflows and rules can do it, too, but most have been the first.
> I've never noticed it being that bad. Annoying? Absolutely! But not that painfully slow.
I have only seen a few self hosted jira, but all of those were mind numbingly slow.
Jira cloud, on the other hand, now compared to 2018 is faster from what I remember, I still call it painful any time I am trying to be quick about something, most of the time though it is only annoying.
It is faster than it was back then - I've been using it for 10+ years. Hating every moment of it. But it is definitely better than it was.
At this point I think I would try to automate this pointless time sink with a script and jira API.
100%. Their API isnt even bad. I made a script to pull lots of statistics and stuff from jira.
Looking at the software development today, is as if the pioneers failed to pass on the torch onto the next generation of developers.
While I see strict safety/reliability/maintainability concerns as a net positive for the ecosystem, I also find that we are dragged down by deprecated concepts at every step of our way.
There's an ever-growing disconnect. On one side we have what hardware offers ways of achieving top performance, be it specialized instruction sets or a completely different type of a chip, such as TPUs and the like. On the other side live the denizens of the peak of software architecture, to whom all of it sounds like wizard talk. Time and time again, what is lauded as convention over configuration, ironically becomes a maintenance nightmare that it tries to solve as these conventions come with configurations for systems that do not actually exist. All the while, these conventions breed an incompetent generation of people who are not capable of understanding underlying contracts and constraints within systems, myself included. It became clear that, for example, there isn't much sense to learn a sql engine's specifics when your job forces you to use Hibernate that puts a lot of intellectual strain into following OOP, a movement characterized by deliberately departing away from performance, in favor of being more intuitive, at least in theory.
As limited as my years of experience are, i can't help but feel complacent in the status quo, as long as I don't take deliberate actions to continuously deepen my knowledge and working on my social skills to gain whatever agency and proficiency that I can get my hands on
People forget how hostile and small the old Internet felt at times.
Developers of the past weren't afraid to tell a noob (remember that term?) to go read a few books before joining the adults at the table.
Nowadays it seems like devs have swung the other way and are much friendlier to newbs (remember that distinction marking a shift?).
Stockholm syndrome