11 ms·
I feel like hating on Jira is the pastime that is now passed down from each generation of programmers to the next. I'm going to stick up for Jira. I certainly
by hn_throwaway_99 4y ago
I feel like hating on Jira is the pastime that is now passed down from each generation of programmers to the next.
I'm going to stick up for Jira. I certainly don't "love" Jira, though I do think they've made significant improvements with "new Jira" (I think they call them team-managed projects now).
The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for the extreme difficulty of the organization-wide problem Jira is trying to solve. It's always taken on from the position of "well, it didn't make my specific use case easy", but never with an appreciation with some of the complexity that Jira needs to solve for other users at your company, never mind other companies.
Obviously some of the complaints (speed, stability) are very valid, but here's a question I think is just as valid: why don't you think some other company has come along and toppled the Jira crown? Certainly tons of them have tried, and while many have their supporters, they are almost equally likely to have their detractors.
The fact is, building a generic project management and tracking tool is a really difficult, hard problem. In my old age as a programmer I feel like Jira is kind of like our form of government: "Jira is the worst project management tool, except for all the others".
- asah 4y ago+1 to all this. Plus, Jira *scales* - all the cutesy drag-and-drop tools are good for 100 tickets/issues/etc and then fall over. JQL and bulk edit are just warming up at 1,000 tickets.
- sidlls 4y agoYou must have been using some alternate-universe Jira. The Jira installations I've had to suffer with fall over bulk editing a handful of issues. I've never seen a "bulk edit" like feature implemented as poorly as it is in Jira. It shouldn't take 15 seconds to complete a simple bulk edit of a handful (single-digits) of issues.
- blowski 4y agoI totally disagree with you, but I upvoted you for making me think about it differently.
- zwischenzug 4y agoI couldn't agree with this more. What people hate is not Jira but the organisational thinking that it facilitates. I've used jira in other contexts and it's been mostly a joy because the processes it modelled were happily simple.
- shagie 4y ago> why don't you think some other company has come along and toppled the Jira crown? I really wish Jetbrains Spaces was around when the organization I work for was doing the "everyone under one umbrella" migration. Prior to Jira, we had one team using GitLab issues, one team using Redmine, one team using Borland Star (with a tight limit on licenses), and one team using Excel. I personally would have gone with Redmine over Jira... however that also would have tied me to doing a lot more setup work, upgrades, and care and feeding of the system compared to the relatively turn key setup of Jira.
- cogman10 4y ago> why don't you think some other company has come along and toppled the Jira crown? Because it's really hard to kill off the market leader when the market leader is embedded into the core of how a company works. I don't buy that it's a matter of competitors not being better. It is more about inertia. The argument you have here could equally be applied to C++ or Cobol "Why is new code being written in these languages? Why is C++ so popular even when there are many other competitors? Certainly tons of languages have tried." I currently work in a field that is disrupting existing products that were, no joke, written in the 90s in VB6. It can be super hard to sell our product to a lot of people, not because our product isn't better, but because they've been using our VB6 competitor since the 90s.
- hn_throwaway_99 4y agoI disagree with this. Absolutely, once Jira (or any particular project management tool) gets it's "tentacles" into a sizable enterprise, it's very difficult to dislodge. But I've seen tons of other examples in my career of companies making larger, more difficult transitions because they clearly felt the risk/benefit was worth it: moving from CVS/Subversion to git, moving from on-prem to the cloud, moving from Windows to Mac, moving from hipchat to Slack, moving from Oracle to postgres, yada yada yada. I'm certainly not saying it's easy, but I fully believe that if a project management solution came along and all stakeholders went "holy shit, this is so much better than Jira", that many companies would make the switch. This hasn't happened, and honestly if you hear people complain about Fogbugz or Asana or whatever that it's probably an equal "per-capita" bitch rate.
- kelnos 4y agoI think it's maybe a bit of both? I worked at an org that was using Trac for most things. It's probably fine for a small, engineering-driven company, but it's not very full-featured and isn't great for PMs and other business types. So once the company got large enough, management wanted to switch. Many of us essentially said, "ok, that's fine, but please please please not Jira". And yet, they went and hired some consultants who were like "oh, Jira is the industry standard for your line of work, you'd be taking on a huge risk not using it, blah blah blah". Management bought it, and they've been on Jira ever since.
- steve918 4y agoI feel like a lot of great programming talent has been wasted by very smart engineers who felt the pain of their current ticketing system and spent years building countless startups only to end up with something occasionally marginally better than Trac (2004).
- oneplane 4y agoBack in 2008-ish a lot of projects I came across tried to use Redmine because their company had a sucky JIRA or sometimes even Mantis implementation. Redmine turned out to be highly unsuitable in a matter of a few months and after trying out a few options that are mostly just tickets+kanban boards, it turned out that the simplest 'fix' was just setting up an individual JIRA just for the team so it could be used properly instead of some heavy handed top-down "use this tool in this specific way" approach. Once more teams started to do it, the 'company-wide' JIRA essentially just contained managers and a few product owners and it got deleted in a year or so. Afterwards, all the 'team JIRAs' got merged into a normal JIRA again, but this time everyone had full control over their own projects and boards, problem, solved.
- djur 4y agoWhat necessary features did Jira give you that Redmine and/or "tickets + kanban boards" didn't?
- chillingeffect 4y ago>why don't you think some other company has come along and toppled the Jira crown? Why haven't cowboys found a different way besides horses to get around? They're not interested in what those under their asses think or feel.
- stack_framer 4y ago> "Jira is the worst project management tool, except for all the others" I came here to say precisely this. In addition to Jira, I've used Clubhouse, Trello, monday.com, and GitHub Issues. Jira sucks slightly less than the alternatives I've used.
- CSMastermind 4y ago> I do think they've made significant improvements with "new Jira" (I think they call them team-managed projects now). I feel totally the opposite. If you've ever had to administer Jira at a large company than team-managed projects are the bane of your existence. If you think, there's even a small chance that your company will grow to 300+ engineers any time in the next several years then do yourself a favor and turn off team managed projects entirely or else you'll face a painful migration away from them. Though I will generally defend Jira as a product for many of the reasons you said.
- hn_throwaway_99 4y agoI upvoted your comment because I believe it's a perfect example of what I was trying to point out: it is impossible to please everyone with a company-wide project management tool, but the fact remains that it is a necessity. For all the people bitching about how Jira makes it hard to work like they want to work, their are folks like you who will complain that Jira makes it to easy to get around a company-wide standard. To emphasize, I'm not saying either side is right or wrong, I'm just saying it's impossible to build a project management tool where large subsets of people won't complain about the exact same set of features that another subset of stakeholders likes.
- marcosdumay 4y ago> but the fact remains that it is a necessity I am interested on why people think that. It doesn't look like a necessity to me. Ok, in a medium company, with dozens or maybe a hundred or two people, centralizing all the workflow is probably cheaper and more productive than siloing teams. But in a large company the inverse can very easily be true.
- thfuran 4y agoWhat fails to scale?
- halostatue 4y agoWe added a team-managed project a while back, and built a really good workflow around it that satisfied the needs of everyone who works in that project. We can’t easily replicate that workflow anywhere else. This isn’t the end of the world, but I should be able to create a new team-managed project based on another team-managed project and then modify its workflow separately. So far, I can’t figure out how to do that. I’d love to take the team-managed workflow and promote it to a company-managed workflow now that we’ve experimented with it. So far, I can’t figure out how to do that. Don’t get me wrong, I really hate JIRA. I’ve written my own bug tracking system. I’ve tried lots of other tracking systems. JIRA is wrong on so many levels, but eventually you hit something in one of the other tools that you cannot address with those tools, but is possible (but painful to configure, and it might cost you extra money) in JIRA. The only other tracking system I really like is GitHub issues, but it also has problems and limitations. And then you have things on GitHub that actively make things much worse (the autoclose bots; forms like the ones that Vue puts up, etc.). I’ve never seen any organization need the level of complexity that they end up using in JIRA (especially the access permissions, which consistently get borked sideways), but most organizations eventually need something better than Bugzilla, Trac, or Github Issues. The other difficulty is that switching bug tracking systems is tough. I want to really try Tara, or ClickUp, or Monday or a few different ones, but adding another tool is literally adding another tool. This is the same reason we’re using Confluence, even though it’s objectively the worst wiki in existence. I hate Atlassian products with a passion. There’s nothing better, and the cost of switching is too high.
- DRW_ 4y agoI'm on the same page as you, I don't love Jira either, it's not something I think about in the conversation of "software/services I enjoy using" - but I think it's _fine_. Jira cloud in our organisation is also reasonably fast, the front end can be a bit janky sometimes, but overall considering the complexity of the application, it's not too bad.
- vosper 4y agoYeah I've been defended Jira here in the past, too. My opinion is that Jira reflects the organisation that manages it. It's basically a whole lot of customizable UI and permissions hanging off a user-defined state machine. You can set it up so that individual teams can fully administer their own projects, or you can go all the way in the other direction and have centralized, locked-down management where you beg some internal specialist Jira admin(s) to make your changes. Also, in the last couple of years it's got a lot better. It's faster, there are options for simpler configuration, and more stuff out-of-the-box (assuming you're on Cloud, but isn't everyone these days?). In detraction: configuring it can be a huge PITA. So many screens, concepts, and so much clicking. But when it's done it works, and I think most of the hassle is just inherent complexity from such a configurable tool (if you haven't Admined Jira: you can change almost anything).
- colechristensen 4y agoJira doesn't just reflect, it drives convoluted unhelpful bureaucracy. The tool drives the organization to look like the tool wants it to, which is disorganized half broken "organization" with silly overcomplicated rules that give people something to discuss enthusiastically instead of the actual work that needs doing. Jira is organization poison, not just a reflection of what an organization is.
- oneplane 4y agoNo, it isn't. We have plenty of setups in multiple organisations where even within the org only the administrative settings of the server are locked down and everyone else is free to do whatever they need. Lots of teams just use it as a kanban board, while others setup a state machine-based funnel to process user/business input into usable tickets. JIRA in its default configuration essentially lets you create anything, anywhere in any state. Anything beyond that is just bad product configuration. Now, there are plenty of products out there that suck no matter how you configure it (looking at you, ServiceNow). Especially the comments about "I would rather use trello" seem extremely uninformed as you pretty much *are* trello when you just stick to one kanban board and one project.
- colechristensen 4y ago>The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for the extreme difficulty of the organization-wide problem Jira is trying to solve. I think the core problem with Jira is organizations trying to use it to solve complex organization-wide problems. It is an enormous time sink, and using Jira to rule the workdays of employees is the problem. Anything much more complicated than a checklist is wrong. Jira is an attractor for middle management growth that gives people who don't need to be doing anything something to do, and adding complexity gives more opportunities for more people to not do very much and generally get in the way of execution. It is also a way to give people who aren't very necessary or very good at understanding the big picture something that they can do to do. Take away Jira and tools that you can order other people to use and you end up with middle management that literally doesn't know what to do because they couldn't organize or ease productivity to save their lives. Jira becomes the thing being managed instead of whatever is actually to be done.
- synu 4y agoAgreed, it’s like a big flashing neon sign that promises middle management a stage on which to act out all their worst impulses. It’s the exact opposite of “keep it simple and communicate with each other like humans.”
- bamboozled 4y ago100% agree, in my current role it’s used this, if what you’re working on doesn’t have an issue, you’re a naughty person.
- oneplane 4y agoIf a company is trying to use JIRA for more than state communication they are doing it wrong IMO. Planning goes into calendars, ephemeral stuff goes into chats and calls, and code and code-level issues goes into repositories. I have seen plenty of attempts to make a product like JIRA the 'interface' between some management person and 'the subordinates' and it never works, simply because trying to place an 'interface' there in itself doesn't work.
- throwk8s 4y ago> It's always taken on from the position of "well, it didn't make my specific use case easy" For customers, their own specific use cases are the only ones they should care about. I don't know why there isn't a good solution to the problems Jira attempts to tackle, but that's no reason to get philosophical. It's OK to hate every existing option.
- bityard 4y ago> The fact is, building a generic project management and tracking tool is a really difficult, hard problem. This is pretty much the core of it. I use Jira daily, but my exposure to it is the tip of the iceberg in terms of what it can do. I think what most people forget is that this Jira is basically an ERM but for development-focused organizations. (Where the resources are time and people instead of processes and inventory.) If you've ever seen the complexity (or price tag!) of a real ERM, Jira actually looks very reasonable. That said, smaller companies and teams should definitely use simpler tools that are more appropriate for their scale. Hire a Jira consultant and make the switch only when you're big enough to justify it.
- ziolko 4y agoI get paid for developing plugins for Jira since 2014. One can complain about UX and speed of this software, but I saw it being the hearth of businesses of all kinds and sizes. Just like you won't get fired for using React in your project, you won't get fired for using Jira. It will support whatever your workflow is (and I don't mean only software development, but things like hiring or office management). If the built-in features are not enough, you will find a plugin that meets your needs. I think long-term it's important to use a tool that give you this flexibility.
- polotics 4y agoDoes Linus use JIRA on that little project called the Linux kernel? Why is git with good readmes and clear pull requests not enough project management? If you're not doing PR's you are just LARPing software development. I don't hate JIRA, I hate "IT" employees that can't program.
- jsiepkes 4y agoNo Linus uses Bugzilla [1]. Have you ever used it? You'll be begging for Jira once you've used Bugzilla. Also Linux doesn't use pull requests. GIT doesn't even know the concept of a PR. You are supposed to generate a patch with 'git format-patch' and submit it to a mailinglist. [1] https://bugzilla.kernel.org/ https://bugzilla.kernel.org/
- polotics 4y agogit doesn't know the concept of a Pull Request? https://git-scm.com/docs/git-request-pull https://git-scm.com/docs/git-request-pull Bugzilla is for bugs and that's the point, right? A project is not a set of bugs...
- jsiepkes 4y agoA GIT "request-pull" generates a (mail) text with a patch which is to be send to a mailinglist. It's just the automated version of 'git format-patch' which also generates the e-mail message text. It is nothing like a Github PR.
- djur 4y agoWhat's wrong with Bugzilla?
- mr_toad 4y agoThe Kernel isn’t managed solely through patches and README files. There is often a lot of up-front communication and documentation. My takeaway is that the planning and the issue/bug-tracking and the patch submissions are three seperate somewhat independent processes. There are no managers trying to group all the tickets into patches and patches into projects in some sort of neat (but illusionary) hierarchy.
- lamontcg 4y ago> I rarely feel that bitchers have a true understanding for the extreme difficulty of the organization-wide problem Jira is trying to solve. I think the problem is that Jira is optimized for productivity theater and top-down management. When an organization deploys Jira it is usually because upper management thinks that it needs a deluge of task tracking so that everyone can stay perfectly "aligned" all the time. This creates an annoying amount of make-work on the part of Engineers and their immediate managers, slows down velocity and the vast majority of the time spent on inputting data into Jira never results in anything actionable. Jira is just a symptom of the disease though.
- serial_dev 4y ago> Jira is optimized for productivity theater and top-down management Hit the nail on the head. I don't hate Jira. I hate working for companies and with "micromanagers" that prioritize bs metrics over improving customer satisfaction, and busywork over impactful projects. And these kinds of people / companies always use Jira.
- travisgriggs 4y agoI don't use Jira. I'm aware of what it basically is. We're small, we use a pin board, 3x5 cards, and a drawer. Do open source projects of any size use Jira? If not, do they use a basic knock off? The few not-so-big ones I've contributed to seem to get by without it, but maybe I just don't have enough exposure with these. If the open source world can be semi-productive without Jira, I think that's telling. The interested student can decide the details of what it's telling.
- rightbyte 4y agoJenkins uses Jira. Only one I know of.
- antod 4y agoMariaDB does too, I have a feeling I've noticed others at some point, but that was one that came to mind.
- jamesfinlayson 4y agoGroovy does - I assume all Apache products do too, and I assume they get a good deal because they're doing open source stuff.
- BlargMcLarg 4y ago>The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for the extreme difficulty of the organization-wide problem Jira is trying to solve. This is a lot of hearsay which tends to devolve into a debate of "we absolute need this!" vs "no you don't, see X". >Obviously some of the complaints (speed, stability) are very valid I don't think people defending it fully grasp just how important speed and stability are, or at least live in a corporation where Jira was optimized better than the average corporation does. Given not everything is the fault of Jira, but when Jira is expected to be the place you go to all the time and it is that slow, it becomes very impactful to morale. >"Jira is the worst project management tool, except for all the others". This doesn't work until big corps actually try something different, but pretty much all of them push back on the mere idea of trying alternatives. If you can't invest a few months trying a different system, you can't judge it. And since those few months are seen as a "great risk", no manager is going to push the issue any further, even if Jira's costs per developer could easily run into the hundreds (or thousands, for 6-figures) a year on morale loss and time loss alone. And this is the crux of the matter. Management likes concrete numbers. Management likes mimicking what other successful companies do. Management does not like fairly abstract things with great risks. Management does not like big risks with abstract rewards.
- tomohawk 4y agoThe problem with Jira is that it is checkbox software, designed to sail through the checkbox procurement processes that large organizations have. "It checks all the boxes!" Because of this, it is basically jello. It is everything, and it is nothing. It makes nothing simple, and encourages people to overachieve with the tool. If you overachieve with the tool, you will underachieve on what it is you're really trying to do. This is why much simpler tools are better. They are usually free, or at least a lot less expensive, and they come with constraints that you have to live within. Usually those constraints prevent you from going tool crazy, and guide you to actually focus on getting work done instead of doing performance art with Jira.
- Ensorceled 4y ago> The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for the extreme difficulty of the organization-wide problem Jira is trying to solve. No, I have a really good understanding of that. My problem is that Jira, in actual implementation, tends to be how some parts of the organization (often Product) tries to exert fine grained control over other parts of the organization (design, qa, development, operations, etc.) by micromanaging the process. Also, sometimes your organization is just not that complicated. I've been in startups using Jira with dozens of states, with complicated transitions and approval steps, that would have been over kill in medical companies I've worked at.
- jayd16 4y agoYour point is admirable but its also short sighted. You're right that building a one size fits all tool is a large task and it's easy to complain about something hard. But the flaw is in assuming it's a problem that should be solved in a one size fits all way. In my experience the pain points come from top down process that's at odds with the reality of the work.
- babypuncher 4y agoPeople who hate Jira need to spend a year working in VersionOne
- pjmlp 4y agoSame here, I really don't get the cargo cult hate against Jira. Before I got to use Jira for the first time around 2006, everything I used before was crap, either in-house solutions out of CGI scripts or crap like ClearQuest. Stuff like Trello just seems too basic for typical enterprise workflows that overlap sprint planning, with project roadmap, milestones and change requests, mapping of tickets to source code, pull requests, documentation,... If I have decision power, I will always pick the Atlassian product suit versus the competition.
- cotillion 4y agoI think those of us who have had to suffer through ClearQuest, Lotus notes etc have an entirely different scale on how bad things can be compared to those who appear to really really hate Jira today. I'm not a fan of Jira but atleast it loads, eventually.
- bamboozled 4y agoThose things were like 20 years ago ? JIRA is working years old. We’ve developed better more simple issue trackers since, such as GitHub issues and projects. Much simpler.
- pjmlp 4y agoIt is like Google Docs vs Office. Good for casual users, while at the enterprise level everyone wants a different set of 90% Jira features. It is no accident that Microsoft is turning GitHub into an ecosystem that combines Azure DevOps with GitHub.
- timmytokyo 4y ago>Same here, I really don't get the cargo cult hate against Jira. That's funny, because I've always thought of Jira's most ardent defenders as a cargo cult. As this comment section indicates, Jira can do no wrong. It can only be done wrong. Cult.
- 4y ago
- zild3d 4y agoJira is Salesforce
- CRConrad 4y agoAnd SAP, and Oracle, and every other over-complicated thing that causes more harm than good. OK, many other such things may be even worse; but it's definitely in that category.
- matwood 4y agoI agree. I routinely explore JIRA replacements b/c of various JIRA annoyances, but none of the ones I find will hook into our process as neatly as JIRA. JIRA is a lot like agile though where everyone is using a different version ranging from this works fine, to this is a dumpster fire.
- tshaddox 4y agoI’m not sure what “the usual complaint” about Jira is. It sounds like you perceive the usual complaint to be about feature bloat. You only briefly mention speed, which is the only complaint I had about using Jira as an IC developer. From the perspective of an IC I think all these systems are incredibly similar. Jira is the only one that was, very simply, ridiculously slow. As in 5-10 seconds to load any page.
- randomdata 4y agoI'm not sure that is quite the right take. When someone says "Jira" they are referring to the style of product management that Jira enables, not the specific tool. Like how "Google" is used to refer to web search, even if one actually uses Bing. Jira, the software, is far from perfect, but when one talks about hating Jira, they are really talking about the people who use Jira. The same people moving over to a competing product that offers the same feature set perfectly implemented would still leave people hating it. The software itself doesn't matter that much here. It's a people problem. So, why do people cling to a project management style that everyone hates? There is a lot of friction. Nobody wants to be the guy who pushed for an alternative that turns out to be just as bad. "Nobody ever got fired for buying IBM", as they say. You know that IBM will deliver a failure, so everyone is ready when it does fail. If you hired Mom and Pop, you are doing so expecting them to be better than IBM, so when they fail equally there is a buildup of blame to go around. That's not a comfortable position to be in. I would suggest that winds of change are in the air, but it is indeed a slow process to find a critical mass willing to take new risks.
- tootie 4y agoJIRA is the medium that cranky devs interact with disinterested managers. It's just a vessel for data and metadata. And as far as I'm concerned it's one of the best at doing what it does. There's no tool I prefer to JIRA. Asana is a joke by comparison. TFS is just Bad JIRA. Issue trackers like Trello or GitHub issues are fine for creating a dumping ground for ideas but not for organizing. If you can get away with less structure than JIRA affords then congratulations for not having a budget or timeline but the rest of us need some deniability. Every other problem in the world of software projects is human and can't be solved with tickets.
- mr_toad 4y ago> Issue trackers like Trello or GitHub issues are fine for creating a dumping ground for ideas but not for organizing. There’s an argument that you should use an issue tracking system for tracking issues and not planning. Features and stories don’t necessarily neatly subdivide into tasks and issues. Issues don’t always neatly fit into a story or feature.
- hammock 4y ago>It's always taken on from the position of "well, it didn't make my specific use case easy", but never with an appreciation with some of the complexity that Jira needs to solve for other users Your insight is the same reason why people hate boarding selection for planes, or McDonalds breakfast ending at 10:30am or fill in the blank.
- throwawaymaths 4y ago> the organization-wide problem Jira is trying to solve Yeah that problem is that in many places management sucks and can't trust their developers to get shit done, so you have to put metrics on it to bring down anxiety brought about by incompetence. There are large open source projects that don't use jira; the extreme complexity of managing a distributed team with all sorts of interests -geneally even more complex than what a company has to deal with- is empirically doable without jira. When an organization pivots to using jira it is a sign that their managers are no longer capable of respecting the programmers that work for them. If an organization starts out using jira, that means they never were. To be charitable I'm sure there are a few corner cases where a manager came up through the ranks and "only knew jira" but that really means they don't understand open source IC, especially in the era of GitHub and gitlab issues. (Btw GitHub issues is absolutely the thing that is slowly replacing jira)
- TameAntelope 4y agoJumping on the "Jira isn't the problem" bandwagon, 99% of what people hate about Jira now is that the people who manage it make Jira hard to deal with. I'm at an early startup and we use Jira; it's great because I'm an admin and I can make Jira reflect whatever I need it to reflect. It's also highly compatible with compliance nonsense -- if you can say, "Every change to code is tracked in Jira" (the decision process not the literal diff) the auditor's eyes glaze over and they just move on.
- wpietri 4y ago> building a generic project management and tracking tool is a really difficult, hard problem I would say building a good one is an impossible problem, because of conflicting needs both across and within companies. The primary job of Jira isn't to help work get done. It's to give managers and executives feelings of knowledge and control even when that makes everything worse. You don't need fancy planning systems to get good work done. Indeed, I think it's the opposite. I've done many years of work with only index cards. E.g.: https://williampietri.com/writing/2015/the-big-board/ https://williampietri.com/writing/2015/the-big-board/ As Poppendieck has talked about, we live in a "Tyrrany of the Plan" age, but that's not necessary and it often makes things worse: https://chrisgagne.com/1255/mary-poppendiecks-the-tyranny-of-the-plan/ https://chrisgagne.com/1255/mary-poppendiecks-the-tyranny-of... I think this has happened because of the rise of managerialism, where management becomes a self-justifying caste. : https://en.wikipedia.org/wiki/Managerialism https://en.wikipedia.org/wiki/Managerialism
- NikolaNovak 4y ago>>"You don't need fancy planning systems to get good work done" I mean, as a single individual, in some circumstances, sure. If we think a bridge or railroad or spaceship get built without fancy planning, we've taken our software engineering paradigm to new level of delusion. Why does engineer or constructor worker understand that you need planning to align thousands of people over many years to build a great big thing, but we feel in software we are just too darn special of snowflakes to need or agree to that? Sorry if I got your comment way out of context or scope, but it just struck me as a very circumstantial statement, but one that is bandied a lot as a generically applicable one - which it isn't. For many things you need very fancy planning indeed.
- BlargMcLarg 4y agoI'll ask you the reverse. What proof is there we absolutely need all this to function? If people are so sure of this, surely they can substantiate it with more than just rationality. If the similarities are fine, just pull that information from the other disciplines you insist know better than the "special snowflakes". >Why does engineer or constructor worker understand that you need planning to align thousands of people over many years to build a great big thing You're conflating "needing to align thousands of people" with "needing a fancy system which pulls everyone in its web to deal with multiple times a day". If anything, construction shows just how little ICs need to know to function. You don't boggle your construction workers with bureaucracy, you take it away and let architects, managers and foremen deal with it.
- josephcsible 4y ago> why don't you think some other company has come along and toppled the Jira crown? Because the people who get to decide whether or not to use JIRA aren't the people who it causes the most suffering for.
- deleted 4y ago[deleted]
- ulkesh 4y agoFor the most part, I agree. But... If the UX wasn't garbage I'd defend it, too. It has a lot of nice features and integrations. But the UX changes they have made in the recent past (few years-ish), made it worse, for me. And, in my opinion, the reason some other company hasn't come along and toppled it: critical mass. It's the same reason Epic is king in the hospital IT world. The UI/UX can be garbage (and it's so much worse with Epic than with JIRA), but organizations will still stick with it, because it's what they know.
- thefaux 4y agoIt's not that I think is a particularly good or bad implementation of project management software (though I think as others have pointed out, in its effort to be all things to all people, I think it has converged on a lowest common denominator solution). I reject the concept of general purpose project management software. I think that at best these tools are primarily surveillance tools for middle management. They disempower workers and make them fungible. The workers are evaluated on tool points rather than the actual value they create (sometimes these may be alignment, but often they are not). At worst, I think they actually lower product quality because of the poor incentives that are inherent in a system that rewards closing issues and creating "features". I believe the best workers (at both the management and IC level) are not going to want to waste a significant chunk of their professional lives in Jira world and the worst workers just want to keep their paycheck coming every month so they will just submit to it and keep cashing their checks. The organization will thus rot and converge on the lowest common denominator employee, which is indeed what the tool kind of promised: fungible, low skill workers with predictable (low) output.
- NonNefarious 4y agoYou need SOME kind of tool to provide a repository of issues and assignments, and Jira could probably be fine. But the simplest things are baffling in Jira. Any issue-tracking system that requires the users to learn some obscure syntax (or even to use SQL to refer to its internal data structures is a failure.
- markshead 4y ago> "Jira is the worst project management tool, except for all the others" This is key. The problem with Jira is less about Jira as a tool and more about how we approach project management. I've seen some teams thrive with Jira. I wouldn't say they "loved" Jira but they had a light weight project management structure that let them get work done and enough control over Jira to set it up to stay out of their way. They didn't give Jira credit for their ease of working because it was their processes that were good. Jira just gave them a way to not have to write everything down on paper. I've seen other organizations create a horrible project management structure and then use Jira to "enforce" those structures in ways that magnify all the worst aspects of what they are doing. In those situations it is usually more politically palatable to blame Jira rather than the management processes. Those type of organizations usually blame the tool while hoping that a different tool will force the organizational changes that are needed to make life better.
- ZainRiz 4y ago> why don't you think some other company has come along and toppled the Jira crown? Jira is the way it is because Jira ISN'T built for developers. Devs may have to use Jira, but they're not the ones who have to pay for it. I wrote about this a while back: "Who is Jira’s target customer? It’s certainly not the poor developer who struggles to add a link to his bug report. (I’m still mad at them) Take a look at Jira’s site and see what they emphasize: Those pages glamorize having an overview of what work your employees are doing. It’s a tool made for managers. Especially higher level ones. The VP won’t be filing work items, but they’ll be very interested in the insights those dashboards offer. Jira spends all their software cycles building new features for that VP, ignoring what you and I might consider critical user bugs." Source: https://www.zainrizvi.io/blog/never-focus-on-the-user#jira-s-justification https://www.zainrizvi.io/blog/never-focus-on-the-user#jira-s...
- ratww 4y agoYep. We often talk about enterprise software, and how it's often bad and, has superfluous features and almost no UX design because it is made for buyers rather than for the real users. Well, guess what. We're the users now.
- ZainRiz 4y agoExactly. I wonder what Jira engineers think of Jira
- bamboozled 4y agoWhich is funny because 99% of what project managers seem to be about is making sure work gets done. So the first thing they do is deploy a hurdle to this by ensuring they use a tool which is time consuming and confusing for the people who do the work (usually developers to use) and enforce it's usage. JIRA is so slow and the UI so clunky the project managers where I work use some type of spreadsheet upload mechanism with XML spreadsheets to automate the cruft creation. It's fun to watch.
- ZainRiz 4y ago
- thedougd 4y agoI was asked during a merger, which work management tool do you think we should keep/use? I replied, don't ask me, I'll hate it anyways. It's not because I hate Agile, Scrum, or even Waterfall (although I do hate SAFe). I just know these tools all suffer from similar drawbacks, and somebody will ultimately codify all our organizational problems into the tool. Then, rather than spend an hour a week of their own time, they'll create a new mandatory field and ask thousands of people to spend an hour a week each populating that field.
- lmm 4y agoSounds like a strong argument for using a tool that doesn't have custom mandatory fields. They do exist.
- sanderjd 4y agoI think the answer to your question is that it's because the complaints aren't actually mostly about the tool, but about the processes the tool targets. Jira competes both with different tools and with different processes that use neither Jira nor its competitors.
- atoav 4y agoI worked at a company once (not programming, more like an online shop) which did everything via email. And I mean everything. Tickets, issues, orders, repair requsts, refunds, you name it. It worked flawlessly — in fact I haven't been at a place that was as well organized since. And it all came down to one thing: everybody understood that there is only email and that if it isn't an email it will be forgotten and fall in some crack, so you better make it an email, that has a propper subject, is searchable, etc. That meant everybody was writing emails with nearly military rigour, while the asynchronous nature of the electronic letter always reminded you, that you just needed your emails done and then you were fine. Depending on your position you had multiple (shared) inboxes that corresponded to the tasks. Of course there were some old emails, that were more of a "if anybody finds the time and will" type and sometimes emails from the guy from the day before had to be done etc. But all in all it was surprisingly pleasant to work just with email. The point of the story is: You can turn any tool to shit if people use it in a bad way. And you can make anything work if people use it in the right way. Most problems with communications are people-problems, not tool-problems. Sure certain tools may lend themselves to certain behavior more than to others but ultimately a team can decide how they wanna communicate effectively and which behavior produces chaos and problems.
- urthor 4y agoWhat was the size of the company? Generally speaking any organisation, given enough time, can establish processes that are better than JIRA with a certain amount of luck. However, that's the best case scenario. It's a standard distribution. Sometimes a 100 person project gets by fine with email. Sometimes it all goes to shit. A tool like JIRA is, on average, a lot better than doing it via email only.
- atoav 4y agoSmall, 20 people maybe, but a lot of remote people that had their own small "domains" within the project. Sometimes one "domain" had multiple shifts (e.g. shipping). Communication between shifts was just done by writing yourself an email. Granted, such a thing would not scale up to infinity, but for that size it was perfect and extremely hackable (just email + SMTP after all).
- lmm 4y ago> Obviously some of the complaints (speed, stability) are very valid, but here's a question I think is just as valid: why don't you think some other company has come along and toppled the Jira crown? Certainly tons of them have tried, and while many have their supporters, they are almost equally likely to have their detractors. Trello was a much better solution to the problem, that's why Atlassian made sure to buy it and is now hard at work ruining it.
- TheMagicHorsey 4y agoI think the issue is that because Jira offers the hope of a tractable customizable management process, it invites management to put in more process to improve their visibility of a project. This should not result in micromanagement, but it usually does. From a programmer's vantage point this is lose-lose, because your day to day tasks are weighted down by Jira-related bureaucracy, and your mastery of your schedule is continuously threatened by managers peering down from above to ask questions about this and that individual item on your work list. I suppose its a necessary evil for an organization of a certain scale, but for whatever reason, I've chosen to work in teams that are small enough that we can dispense with JIRA all together.
- rib3ye 4y agoTotally agree with this argument, INCLUDING almost making the same Churchill quotation joke at the end.
- ketzo 4y agoAdditionally, people's associations with Jira are not strictly related to the software itself. Jira is often the domain of PMs, management, and other leadership; if you have bad people / product leaders, you're used to Jira being a source of great stress.
- enjoiful 4y agoHonestly, the app called Shortcut is the Jira killer. It really is that good.
- snapetom 4y agoI really, really love Shortcut. Unfortunately our org is looking for a traditional Gantt chart, and Shortcut is a bit lacking in that. However, up to this point in our company, it's been great. It's very deliverable-centered. Stories are the deliverables and are the centerpiece of the flow. Tasks just make up a to-do checklist for a story - there's no endless wrangling about that is a task, there's no credit for doing a task (shitty devs can't game the system). Shortcut feels like it hits a nice spot between the monster that is Jira and too-basic tools like Trello. Shortcut is made for developers.
- coldtea 4y ago>The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for the extreme difficulty of the organization-wide problem Jira is trying to solve. The problem being: "how to create BS data and metrics to satisfy a bureucracy"?
- pmoriarty 4y ago"I rarely feel that bitchers have a true understanding for the extreme difficulty of the organization-wide problem Jira is trying to solve." What is that problem exactly?
- alxndr 4y agoMaybe they are trying to solve too many problems with one piece of software.
- nradov 4y agoFor really large, complex enterprises managing a complex portfolio of products with dependencies between them I have found Rally to be a little better than Jira. It isn't any simpler or faster than Jira, but it's better at tying the whole enterprise effort together. https://www.broadcom.com/products/software/value-stream-management/rally https://www.broadcom.com/products/software/value-stream-mana...
- urthor 4y agoThe developer facing UI of Jira's competitors is MILES ahead of Jira. Trello etc. Jira's "director level" UI is miles ahead of its competitors.
- drewcoo 4y agoThere is the saying that a poor workman blames his tools. (Sorry for the sexism, but let's assume were all guys for this.) I claim something more specific. A totally powerless workman who's afraid of his bosses blames his tools. An individual in the face of indomitable authority blames anything else. Jira is a wonderful proxy for all the bureaucracy and *managers you hate. So hate Jira, because you're powerless to change anything that matters.
- pvinis 4y agothe funniest thing to me is that you used a throwaway to defend Jira . But yea, I agree, they are trying to solve a huge problem. And good on them for it. I still dislike the results though, and that's ok. We still use it.
- likortera 4y agoA few years ago I worked for a company that used https://shortcut.com/ https://shortcut.com/ (at that point, it was named clubhouse I think). I loved it. I think that tool can do everything Jira does in a much better and saner way. It looks a lot more organised, more flexible, more polished, more performant and it doesn't look like it will force you into full SCRUM if you don't want to. You even get to use the same syntax (markdown!) everywhere. Last time I had to use Jira I needed to keep in mind the syntax for writing links in the issue description was different than the syntax for writing links in comments. Tell me that's not some top level suckery. Jira sucks big time, and there are better tools now. The reason no one "toppled the Jira crown" is just inertia, specially management inertia who are the ones deciding what tool to use. For the same reason we're still mostly using petrol for cars, not because there aren't better options, it is because it is not easy to change.