That site is annoying. Popups. Fake "notifications". As a bug tracker, JIRA seems to be OK. As a development system, not clear.
Sorry! We know the bot sucks and we just turned it off. Lame marketing people.
Jira Is a Microcosm of What’s Broken in Software Development
71–80 of 182 posts
Re: Jira Is a Microcosm of What’s Broken in Software Development
#72Sorry everyone on the bot. Just yelled at our marketing people to turn it off.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#73Earlier quoted context omitted.
If you’re going to make judgements so easily you’re going to miss out on a lot of good ideas that people put out there.
I would say 90% of tech ideas that area floated out there are awful and I'm being pretty generous with that number.
I also tripped on this sentence. But the article is not bad if you charitably read "spreadsheet" as "spreadsheets for bug/project tracking."
Re: Jira Is a Microcosm of What’s Broken in Software Development
#74Does anyone else find it pretty obnoxious that this site changes the window title back and forth between "Jira is a microcosm of what’s broken in software development" and "(1) New Message!"? Is this a bug? Who thought this was a good idea?
That website is "a microcosm of what's broken" with websites. Here is that content without that: https://beta.trimread.com/articles/32605
I know. The bot sucks!!! Sorry... it's my fault. My boss, Dan the author, just yelled at me and I turned it off :-)
Re: Jira Is a Microcosm of What’s Broken in Software Development
#75I briefly used Jira, but I couldn't handle the extreme slowness. You click something. Then you wait. And wait. And wait.
Cloud or Server? It seems a lot of companies’ reputation were broken by clients installing their software on 2GB/1.5GHz servers with HDD, and Cloud will help at least getting a consistent measurable experience of the same product for everyone.
In what universe is a few billion instructions per second not enough to respond to a single click?
Re: Jira Is a Microcosm of What’s Broken in Software Development
#76JIRA is just a tool. A pretty reasonable one. It integrates with every dev tool under the sun at this point. It’s as lightweight, or invasive, as you want it to be. Sometimes there’s people or workflow problems that get blasted as jira (or rally/ac) problems because that’s the interface you see those people or workflow problems through.
Nah, generally the point 1 stands. JIRA has potent top down customization tools that are easy to misuse, e.g. adding required fields, task types priorities or defining task flow.
Just that information overload can make working with it a real pain.
These can easily break its own features e.g. scrum or kanban boards or backlogs, which are configured separately.
And the dev or project lead typically does not have access to directly customize it, because JIRA ACLs are way too broad or company has a top down policy on it.
On top of that, it has rather weak support for default values...
Email notifications are also not exactly customizable by the user. It's worse at that front than bugzilla even.
One thing that was sort of customizable are the frontend report views. Shows for whom the app is made - beancounters.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#77Usually Jira sucks because it's not setup correctly to support teams' workflows, instead it's used to impose workflows on teams. Jira can be as heavy or lightweight as you make it, but most of the suffering I see is because the way teams work isn't being supported by the Jira owners/admins.
exactly. if the process is broken, jira makes an easy scapegoat but that's misplaced. i've joined several teams (as PM) that hated jira until we were able to talk through the preferred workflow, and then reconfigure jira to support that workflow. then it was embraced, especially with automations that advanced tickets through the process where possible.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#78Earlier quoted context omitted.
> performance By Atlassian’s ToS, you are not allowed to « comment on the performance of the products ». I know no-one thinks this would be enforced here, but I just want to highlight that it doesn’t help a company to improve if they know they can just lawyer-up a problem away and avoid benchmarks and being compared on that topic.
Wow, that sounds like the most communist thing I've ever read in a ToS
Probably because you have absolutely no idea about what communism is.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#79Learning Jira and accepting Jira both classic and NG has made me so much money, as a team leader, architect and program manager. Jira is the user plane for interacting with project items, however like others here said, everything else must be solved with clear communication, frequent ACKs with team members and so on. Yes, Jira Next Gen is nicer. But classic works fine too! Also Jira can be a lot of other things. It's…
But at what expense? Does Jira ever frustrate you? Imagine how it frustrates developers that hate working with overly complex time-sink software. I can change my email client. I can change my text editor to my liking. I can change nearly any other tool I use, but when a company uses Jira, I'm trapped using something that mostly gets in my way.
I don't have the choice. I am just a cog in the wheels and it helps us do our job.
It's not really in the way, if that's the case it sounds like your processes or workflows are messed up.
I've had days where I don't want to see it, but that's because I'm tired of working. In those times it quick to blame Jira.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#80The JS-heavy web interface of Jira can be infuriatingly slow, so perhaps the frustrations start from there.
Jira, the project management tool, can actually be great, if you configure it properly. The issue lifecycles, what fields are visible, how the board is showing things etc. can be designed to be as simple or as complex as you want it to be. In addition to that, the integration with Bitbucket and Confluence is also fantastic for referencing issues and features across the code and documentation.
Misuse of a tool does not make it a bad tool.
Disclaimer: have worked on developing a Jira plugin, so my understanding of Jira might be a bit more advanced than that of a novice user (but not by much).