yeah sure, happy teams start with jira but they end up as angry and sad teams
Programmer Humor
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
Yeah, we were also once happy.
And then we started using Jira.
RIP
Issue resolved
No defect
Will not fix
At least you’re not using Azure Devops boards, Service Now or Basecamp. Those are all worse in my opinion. I miss Jira.
For those complaining about Jira... I used to be one of you. After changing jobs and using several alternatives, I am begging to be back on Jira. Manage Engine is currently the bane of my existence.
That might very well be the case, however, why are all of these apps so incredibly bad?
Jira especially seems like the definition of feature creep. It's more bloated than a lactose intolerant child after a tub of ice cream.
Because having more ticked boxes than the competition sells. Doesn't matter if it's of any relevance.
That's the company's fault for using all the features
I also wonder if people complaining about Jira are still on Jira Server. Jira Cloud is a much nicer experience. Certainly not perfect, but I've yet to see an actual viable alternative (once worked someplace that tried to move all project management to Gitlab... 🤮).
Cloud is way worse than server in my experience. Server was only bad because it was usually configured poorly and IT would never give admins to anyone who actually needed it. Cloud is bad because it's slow as hell and can't be configured correctly because the ability to configure it correctly has been sitting in "Gathering Interest" on Atlassian's issue tracker for two years despite thousands of votes and comments.
Honestly 95% of Jira complaints are because people have crap workflows configured. Out of the box Jira is pretty terrible but it's very customisable and you need to adjust it to suit your needs - and they have to be your needs and workflows.
That being said, there's that last 5% that Jira just gets in the way. If anyone has ever had multiple teams working on a single product, Jira is very prescribed about how you're supposed to structure that and If you don't, it's a pain.
I'd suggest that 95% of Jira complaints are actually about corporate culture which is felt most keenly through asshole PMs trying to micromanage you through a ticketing system. It's mostly a fine piece of software - if you have a certified wizard to configure it it can be great... if you have a dummy it's going to be barely usable - but you can say the same thing about github issue tracking.
The unfortunate thing is that the teams most likely to use Jira are also the teams I most likely never want to work on.
I can type out the entire 10 word long name of my sprint into the searchbar, and it Jira will pull up 22 pages of things that are not even CLOSE to what I searched. It's a nightmare to try and find my current sprint among the 65 other team's sprints every month.
ClickUp is A LOT worse than Jira.
The issue is more that all of these planning tools enable bad managers to implement bad management practices and workflows without any actual tracking for what constitutes bad management. Almost without fail, every manager I've worked with who is very attached to these products ends up using them for the sake of using them. And then when that produces shit results it's all about "engineering buy in" and "process learning curves" and they end up doing real damage to products before someone notices that Jira actions are not correlated with protective management.
The biggest issue is that good, effective management tools actually end up being a double edged sword because of how they shield bad managers the illusion of legitimacy.
All my homies hate agile, Jira, scrum, kanban, etc.
In truth none of these items are inherently wrong - what's wrong is leadership picking up new tools and adopting management structures expecting them to solve fundamental organizational issues.
Instead they only serve to magnify the outcomes of your existing corporate culture.
It's funny that "Individuals and interactions over processes and tools" is the first of the tenets of agile and the most ignored. I think most people's frustrations with agile are from people worrying too much about processes and tools.
“Atlassian - for when you want make your security team really work”
I use Teams and Jira, and I can't even imagine the amount of wasted time when I click anything in either of them and nothing happens for a good while, just waiting around.
If you press F12 and look at the network calls you can see the insane amount of analytics they are sending for every twitch of the mouse
Jira is a masterpiece compared to the dumpster fire that is Teams.
Maybe the old, discontinued on-premise version. The cloud version of JIRA is a huge step back.
With that said, Teams is not a good product either.
I beg to differ.
I've not had a real issue with teams since the early 'new teams' release. Nor have I had issues prior.
Using Jira is actually something I dread every day.
Knowing I have to go through the list of tasks and projects, where each click means another few seconds of staring blankly at the screen as it loads.
In an age where I'm used to every interaction having a near instant reaction, using Jira feels like peeling potatoes with a butter knife.
Maybe you just don't have a reasonable comparison. We just switched from Slack and Zoom to Teams and it has significantly impacted our ability to collaborate and communicate. It's constantly dropping calls, video quality is awful, annotation is awful, the layout is wasteful with tons of wasted space, audio is terrible, there's no closed captioning visible while screen sharing, there are too many problems to list. It's the type of product I'd expect from a high school programming class, not a trillion dollar company.
Don’t worry teamsters we added 6 new ticket statuses so they can get auto-sorted straight to the abyss.
I absolutely love how this implies that the team is happy before going to Jira.
so not only can Atlassian not write software, they can't develop a usable product, and they can't even market it without insinuating how shitty it is.
I read "happy ___ starts with ___" as stating that happiness was the eventual result of a process that started with ___.
With Jira everything is an issue
Want issues?
Start with Jira
jira made me quit software dev (not by its own, but a significant factor)
I hate jira because it slots your work stupidly by the management, or so I feel it.
A manager usually works with time slots, say 8 a day (or whatever), they are all mostly disconnected, like do meeting with A, go to standup of team B, PMD for dev C etc etc. Dev isn't like that but everyone seems to start thinking it is: how many "items" was finalised last "sprint" etc and other stupid metrics.
Am I alone here or is there even worse things with jira in your opinions?
Where happy teams go to die.
They have a predatory business model. "Hey we're cheaper than the competition". Once you're soaking in it and need features, they have options but it'll cost you. I reckon they have slick sales people who know how to pander to the egos of middle management as well. You know ... The people who don't actually have to use the tool but sure like to feel like they somehow matter.
Friends don't let friends use JIRA
"I'm not your friend. By the way, if you don't use Jira you're fired." -Middle Managment
"I hate Jira too. you're fired"- Senior management.
Seriously though - JIRA isn't always a massive pain in the ass. It's just the way it's used that sucks. Workflow restrictions so devs can't move tickets from testing back to in progress, dozens of mandatory fields, etc.
When your tools start dictating your workflow rather than the other way around then it's time to switch tools.
Yeah, when you start Jira you're probably still a happy team
Not for long...
Idk man, better than a post it Kanban... which is where I came from.
If Jira is shit, it's not Jira, it's your Manager. It takes some effort to learn and use, but when it's set up and maintained, it helps a lot, especially for Virtual Teams.
Edit: But their Ai is shit. They gave it for free and now want to charge money for it. Nah bro, not for that retard.
Yeah, jira is going alright for us at work, but there are a lot of supporting people maintaining it and prioritizing things in meetings that we engineers don’t have to attend.
Everybody gangs up on hating Teams instead!
Here's my Jira experience. MS shop, have a programming department, but I'm not in programming and programming isn't our core product.
Need something that requires a Jira request. I use MS Edge because that's what IT recommends and it's not my computer. The only putative upside is that it knows who I'm logged in as. I click on the link for Jira, it asks me if I want to sign in with my account, which I assume is the MS one since it has the right email/user for it. It tells me that's the wrong one. Would I like to use my Atlassian account? Sure, let's use the same email. Whoops, you don't have an Atlassian account, but there's an MS account for your company. Do you want to use that, or something from the usual list of places that will log you in (Google, Facebook, MS)? Note that the MS option is only included in the list of third-party logins even though it knows my company has MS logins setup. So I click the MS option, and it may or may not ask for my password, because I'm already logged in via Edge, but it will certainly do my 2FA. And now I'm finally able to tell IT what is bothering me, and they wonder why people always seem frustrated.
So, now that I've gone through that once, I can save a single click by not choosing the Atlassian account option and go directly to signing in with a third party. I can only assume this is supposed to be the streamlined process.
JIRA is fine as long as you forego using fucking align. Goddamn fucking align is a the biggest waste of upsell that they catch product managers in ever.
Just do a lightweigt process in a few docs and Excel, and meet in person often enough that you know what folks are doing. That's SOOOO much better and more natural for getting real work done. Great ideas die in JIRA among endless planning meetings and premature decomposition and estimates.
We've been using Linear in my latest company and it is actually quite good. No bullshit fast UI, boards, issues linking with Git, a support that can take a feature request that is often implemented in a week or two after asking it.