Fuck Jira

Fuck people who can't set it up correctly and report on it!

On one hand, there are people who think "Why make it all easy and nice when you can create jobs for people ?" Then there are those actively working on stuff that eliminates jobs. @Ikaroz

@C0D4 regardless, JIRA has its own problems. I had to profile Jira recently just to find out that logging time on a ticket causes it to go crazy. Each time you create a history item on a ticket, like logging time, jira, for some reason, fetches all that ticket's history items and reindexes them programmatically (i.e. in-app, not in-db). Not a problem usually, but then there are tickets like VACATION, SICK-DAYS and others, which have tens of thousands of history items created every year, and now it takes >40 seconds to log a single history item in those tickets.

Imagine what's happening at the EOM, when everyone in the company tries to log their timesheets.

@netikras Jira board at my work place went straight to hell. Won't load nothing

jira is actually great...

...

...

...if you don't have to use it.

seriously, gitlab issues are basically better in every aspect.

The only time Jira was useful was when a manager called to complain about a still pending issue.
“Please tell me the ticket number on Jira so I can check why it was not solved”
“… I told this to employee X the other week!”
“It is not her responsibility to create tickets for you as you have to provide a description of the problem”
“But…”
“This is the policy”

@C0D4 nah man! Jira is a piece of shit software overcomplicating everything.

At every company, every team, every project that was using Jira it was an overcomplicated mess and nobody knows how to use or configure it correctly or if it’s even possible.

And on top of that it has some serious and obvious bugs that are not fixed for years. And many awkward UX things that don’t matter that much individually but sum up to a crappy experience in total.

At my old job, Jira was our main ticketing system for the first couple of years I was there. I goddamned loved it. Not for its UX or pageloads-- which were both bad, very bad --but because it was so easy to automate ticket management through its API. It was well documented, and though there were lots of modules for lots of languages to talk to it, its endpoints were so simple it was easy to just do normal web requests in your code against the normal endpoints.

Because after that, my company implemented ServiceNow, and deployed it as an absolute black box. No API access for anyone, and fucking sales/management types were making decisions about API access. They decided that API access, "caused security problems," and just never allowed anyone to use it.

Compared to that, Jira was a godsend.

@-red That creating jobs is regarded as a positive thing is among the most retarded artifacts of caitalism. The appropriate response to automation is taxation so that the redundant workers can receive a fraction of their former salary in the form of social benefits while they are retraining for another job. Since this sum is much smaller than the original expense of the salaries employers and customers are still saving on automation. The whole tension is also a lot more moderate if things like healthcare aren't dependent on a steady income, but the key part is generous limited time unemployment benefits and subsidized training programmes.

@lbfalvy couldn’t agree more.

I read this and imagined columns called “In Fanny” and “out Fanny” with a ticket which has the title “penis” and someone dragging that ticket between the columns

Is this here a upvote farm ?

It's a micromanagement tool. FUck it.

And Jira fucked you right back