You must log in or register to comment.
Want issues?
Start with Jira
Yeah, we were also once happy.
And then we started using Jira.
RIP
Issue resolved
yeah sure, happy teams start with jira but they end up as angry and sad teams
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 ___.
Yes, like most normal people do.
There’s a lot of discussion when you’re a software dev about the best way to do things, and a lot more is spent on this debate than on actually writing code. One could wonder if there is so much discussion because there are so many good ideas that it’s difficult to choose the one that is optimal for the situation.
But then you read one of these posts on lemmy and you are reminded that someone with internet access and thumbs could spare the short time they have to take a shit to egregiously misunderstand a simple fucking slogan, smugly post about their shit take on the internet, and then return to their job where they will then spend hours misunderstanding the simplest of fucking concepts, slowing down everyone else along with them.
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.
Scrum/Agile has 2 advantages over waterfall.
-
things that don’t work get stopped early, without stigma.
-
the team works together towards an overall goal, it is not individuals working on individual tasks.
The “agile” tools themselves rarely encourage either of these practices.
Jira
- assigns tasks to individuals.
- treats closed and cancelled differently.
-
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
Only ever used Redmine.
We used to use Redmine and it was a fantastic piece of software.
I use both Redmine and Jira at work. I don’t know if we’re using an older version but Redmine feels like something from 2001. Even the API for it is unpleasant.
That’s the point, it’s not flashy but everything loads instantly and you get work done in no time. 2000s style.
I find it an active hindrance to my work. To the point where I have written tools to read data from it via the API rather than use its infuriating interface.
I’m glad it works for you but to me it’s a bit too minimalist. Its user interface is comparable to the forums I was using in 2002. I’d rather something more akin to the ones I was using in 2006.
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.
