top 96 comments

sorted by: hot top controversial new old
[–] 165 points 8 months ago* (last edited 8 months ago)

AI-washing layoffs. They will replace jack shit with AI but that's a better story than "we have to reduce costs because we don't have cheap ways to refinance our $1B debt".

Credit isn't cheap and Iran is not going to make it cheaper, investments in software have tanked, so the only story that can still be told with an almost straight face is that they still have big growth opportunities thanks to the magic of AI.

  • source
  • [–] 124 points 8 months ago (4 children)

    Of all the shitty AI products flooding the market right now, Atlassian's Rovo has got to be the most useless I've had the misfortune of using.

    They should be hiring more workers to fix their AI slop, not replacing them with even more of it.

  • source
  • hideshow 4 child comments
  • [–] 84 points 8 months ago (23 children)

    Atlassian now circling the drain.

  • source
  • hideshow 23 child comments
  • [–] 24 points 8 months ago (5 children)

    I hope they will go down the drain. No more Jira! 🙏

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 8 months ago (3 children)
  • [–] 5 points 8 months ago (1 child)

    Nothing. I really hate the agile thing anyway.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 8 months ago

    As much as this is overly simplistic, there's a sort of appeal here..

    The good news when you have proper issue management is that you don't lose any issues. The bad news is you don't lose any issues.

    In my work, the issue tracker has issues that are over 5 years old. Any time someone dares to just purge those, some one comes out of the woodwork to suddenly passionately care about this thing they have forgotten for years until the jira notification triggered them.

    Projects that have pristine issue discipline tend to suck, as they waste so much energy on things that didn't matter whether or is fixing or engaging in an argument about the value. The better projects tend to say "fine, we will hold that issue in low priority backlog and get to it if we ever run out of better stuff to do", and the submitter is placated and everyone knows we will never run out of better stuff to do.

  • source
  • parent
  • [–] 39 points 8 months ago (16 children)

    We can only hope so.

    I've suggested to my team a few times that we should start a new business developing "Atlassian, but good". They're up for it. So many of our wider business have never used "anything but Jira", and they can't see it for the steaming pile of shite that it is. Not just that it's a bad tool for developers, QE, project management or customer support, but they couldn't imagine anything that's better in any way, or how it would look if it didn't have so many issues.

  • source
  • parent
  • hideshow 16 child comments
  • [–] 6 points 8 months ago

    Problem with being a business is that Atlassian isn't so much really a software company as much as they are a marketing thing that pretends to be software.

    Agile consultants say "Atlassian", companies lap that up at the executive level and the employees roll with it because selecting Atlassian is "thought leadership". The people picking Atlassian are not the people using Atlassian. Paradoxically typical Atlassian rooted workflows are about as far from being actually agile as you can get.

  • source
  • parent
  • [–] 5 points 8 months ago (8 children)

    If you were starting a new company what would you use instead of Jira?

  • source
  • parent
  • hideshow 8 child comments
  • [–] 18 points 8 months ago* (5 children)

    Nothing, personally. Jira at our place only serves the bean counters in the programme management department. The data is a mess anyway, it just gives them the illusion of control.

    I work in a large enterprise and most of our work is just stupid red tape satisfying processes and other teams' rules, many of which just exist to keep those teams employed. There's so much unnecessary work and BS going on.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 8 points 8 months ago (4 children)

    So then how would you document changes, work, etc. as is required by SOC2, PCI, SARBOX and other auditing frameworks that businesses require?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 8 months ago (3 children)

    We don't do any of those things. We're not even developers. We just use Jira to log hours (which is basically one big fantasy obviously)

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 8 months ago (2 children)

    That’s definitely not a problem of Jira. You’re hating the product, when most likely your ire would be drawn to any application you were using for such a fucked up process.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 8 months ago (1 child)

    Considering they are talking about making a replacement service, probably just GitHub/codeberg/etc and collab edit docs and discussions at the start, and then eat your own dogfood.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 8 months ago (2 children)

    Hm. Bear with me. I've used jira on prem for a very long time and have used a multitude of other products.

    Jira was quite good in comparison.

    What am I missing?

    (aside from the whole cloud requirement and atlassian behaving AI-shitty)

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 8 months ago (1 child)

    Jira Cloud isn't just the on-prem version of Jira where you're forced to use and pay for Atlassian's hosting, it's actually a different and much shittier version of the old on-prem Jira. Same goes for other Atlassian products such as Confluence.

    It's no surprise to me that Atlassian is in trouble, as there's little reason I can see to use their products anymore, and they are just coasting on inertia at this point. Whereas 10 years ago, while it was still fun to knock their stuff, I had to admit they were actually pretty decent.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 73 points 8 months ago (11 children)

    I FUCKING hate jira with a passion. I swear to god that dumbfuck software is nothing but a miserable time sink.

    I am sorry for the people who got laid off. Also there is no way AI is replacing the CTO….

  • source
  • hideshow 11 child comments
  • [–] 16 points 8 months ago (3 children)

    I use Jira at work and I still have no idea what the fuck it is, what it's for, or why it's so needlessly complicated. It's a list of text with some dates and names. Why is that worth shit?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 8 points 8 months ago* (last edited 8 months ago)

    Companies wanna feel special and have different workflows around tickets. Making customizable workflows that connect with a ton of different systems easily is a shockingly hard problem.

    I feel like there’s a business opportunity to take 50% of Atlassians value and spin it up into something simple but getting the good 50% down is kinda hard as someone is going to miss one stupid feature that runs 40% of their workflows.

  • source
  • parent
  • load more comments (1 reply)
  • [–] 14 points 8 months ago* (last edited 8 months ago) (2 children)

    I would have more hate to send Jira's way if not for all are tickets being written like:

    "As a developer given I am working on page X Then all functionality of page X is correct"

    Then everybody gets pissy that page Y has a bug.

    "I feel like we've gotten much better with our acceptance criteria" - one of the people getting pissy about page Y

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 8 months ago (2 children)

    I've had to use it in various forms for so long now and I can't believe how unintuitive it is to use. Nothing outside of adding comments is obvious. I dared to try to see what was in a previous sprint and it basically requires a custom report. Why isn't there just a view sprint dropdown or something? I did a quick search to see if it was just me which lead to the Jira subreddit (why is that a thing?) and felt like I was getting gaslit by all the jira 'professionals' calling it a skill issue

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 8 months ago

    Prior Sprints do not Exist.

    There is your active Sprint, there is a huge pile of all tickets that ever were, unable to be sorted by any reasonable metric, and there are the interlinks between tickets. Nothing else exists.

    When your Sprint ends, say goodbye for you shall literally never see your helpful comment that you put all those details into again.

  • source
  • parent
  • [–] 56 points 8 months ago (4 children)

    Yet they can sponsor an F1 team.

  • source
  • hideshow 4 child comments
  • [–] 26 points 8 months ago (3 children)

    Good, someone has to think of the poor race car drivers, and their million dollar team.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 14 points 8 months ago (2 children)

    A million dollars is probably just the catering budget, tbh. I don't even know what this company does, I just saw that no one else had pointed this out. It sounds like I'm lucky to not use their software.

    Every company is just firing employees left and right and I'm not sure what they all expect to happen. I guess just through the magic of AI they can have less workers do more for the same pay. But damn, so many people let go all over the place.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 11 points 8 months ago

    They make jira, project management software that is so slow and annoying you're better off using a chat and shared files on Google drive.

    They also make a bunch of other shitty software but jira is the most famous.

  • source
  • parent
  • [–] 3 points 8 months ago

    I was thinking along the same lines, like they probably spend more on fuel. I remember when Honda pissed everyone off in the 1990s after inflating F1 budgets and then suddenly leaving the sport when the Japanese market crashed. At the time they had Honda factory R&D teams designing and building engines just for F1 teams; that was probably tens of millions a year that wasn't even part of a team's budget... in the 80s and 90s.

    Anyhow... F1 teams have a budget cap for several years now. For 2026, it's $215 million, and that doesn't include engines, nor driver and team manager salaries.

  • source
  • parent
  • [–] 56 points 8 months ago (7 children)

    The biggest surprise in the article is that Atlassian is not profitable. How? They pretty much have a monopoly in the Jira-like space (look , I can't even think of a generic name) and they charge a hefty sum for their products. How tf do they lose money?

  • source
  • hideshow 7 child comments
  • [–] 44 points 8 months ago*

    The article lists an insane revenue of $1.6B, yet the losses are only on the order of $42M in the last 3 months. Against that much revenue, it looks to me like they are managing the company at a slight loss on purpose. They probably could close that gap if they wanted to, but have some favorable tax implications or something by running that "slight" loss.

    (And who knows, maybe this is part of the attempt to close that gap and show a profit before the founders cash out and it all gets sold to a Shittier company)

  • source
  • parent
  • [–] 19 points 8 months ago (5 children)

    Agile project management. And ticketing. And document management.

    There are others. We are working on moving to Asana and other products.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 50 points 8 months ago (7 children)

    They will rehire for less. The AI hype is just a wage suppression scheme.

  • source
  • hideshow 7 child comments
  • [–] 31 points 8 months ago (6 children)

    My employer has been axing so many high level engineers it's not even funny. I think that's terrible for engineer morale. Why would you want to strive to improve and get promoted if it just makes you "too expensive to keep on payroll"?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 29 points 8 months ago (4 children)

    We need more tech unions and tech coops.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 21 points 8 months ago (2 children)

    Guillotines we need more guillotines

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 8 months ago*

    Add this on top of federal layoffs, inflation, tariffs, higher interest rates (I know they’re necessary sometimes), etc. The average American is getting screwed right now.

  • source
  • parent
  • [–] 46 points 8 months ago (2 children)

    About 6 months ago they spent more than half a billion acquiring The Browser Company whose only currently-being-developed product is a pretty wrapper for ChatGPT

  • source
  • hideshow 2 child comments
  • [–] 38 points 8 months ago (7 children)

    So you telling me Jira and all its related bullshit will get even worse? I hadn't thought it possible.

  • source
  • hideshow 7 child comments
  • [–] 4 points 8 months ago

    There's a chance that leaning out the team makes things better. Bloat kills dev teams.

    But... ticketing systems are a bit like fashion. We could see some new shiny system come around that does more or less the same thing, but becomes fashionable for one reason or another and eats Atlassian's lunch.

  • source
  • parent
  • [–] 2 points 8 months ago* (last edited 8 months ago)

    Pretty much all of my colleagues wasted time, because Jira stores comments locally that you haven't yet sent, but does not do that for replies on comments. Those are gone after reopening the site for some reason.

  • source
  • parent
  • [–] 36 points 8 months ago (7 children)

    I’m amazed they had 1600 employees to begin with. I guess it takes a lot of resources to make something suck as hard as JIRA

  • source
  • hideshow 7 child comments
  • [–] 9 points 8 months ago (2 children)

    They renamed "project" to "space", so that it's harder to find what you are looking for.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 8 months ago (1 child)

    They renamed "ticket" to "work item" to "issue". (We all still call it a ticket)

    Stories? Events? Kanban?

    Fuck you, I need a text box, date field and some box to tick that says I'm done.

    All this so that some VP with their thumb up their ass who spends 2/3 of the year in Florida knows I'm working!

  • source
  • parent
  • hideshow 1 child comment
  • [–] 32 points 8 months ago (14 children)

    Their products are utter garbage to begin with, this can only hasten their well-deserved demise.

  • source
  • hideshow 14 child comments
  • [–] 30 points 8 months ago (11 children)

    "Uh, we need you to clear out your desk ASAP."
    "Sure, just submit a JIRA ticket and I'll get right on it."

  • source
  • parent
  • hideshow 11 child comments
  • [–] 12 points 8 months ago (7 children)

    Somehow, HR processes are always exempt from the ticketing process.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 8 points 8 months ago* (last edited 8 months ago) (2 children)

    And yet oddly (and predictably, and likely disastrously, etc. -) some HR departments are among the very first to glibly upload their (our) everything's into constantly shifting unreliable AI "products". Not speaking hypothetically 😐

    Funny stuff, that.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 8 months ago (1 child)

    Because the people who work in HR spent their educational years avoiding anything technical.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 8 months ago* (last edited 8 months ago)

    Agreed, but we should include studying the precise wrong things, meaning conclusions drawn about how the world works - and with their own charming dedication, if describing how that time is spent.

    Mustn't forget HR typically is quite competent, just not at things we easily identify (because that's an inherent component of their competence).

  • source
  • parent
  • [–] 5 points 8 months ago (2 children)

    that's because they don't want you to know when you're getting fired.

    I used to watch the category for decoms that had keywords in the subject line. someone from HR found out somehow (loose lips probably) and they stopped making tickets entirely.

    it's a shame really. I had a really awesome script watching the same criteria for my name 🤣. nothing heinous, just some farewell messages and dirty laundry.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 8 months ago (1 child)

    It's weird, I got laid off by a west coast tech giant and they gave me two months' notice, and they were happy to have me doing nothing that whole time (and I'd had nothing to do for about six months prior to that). I was remote so I guess they felt that I couldn't fuck shit up on the way out.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 8 months ago

    Our HR critters use a case-management system, badly. They have an internal process, but never adapted the default workflows to match it. So the pendejitos are always trying to clean up self-inflicted gunshot wounds to their feet.

  • source
  • parent
  • [–] 3 points 8 months ago* (1 child)

    JIRA and Bitbucket are so bad that even Microsoft Azure DevOps (that is a reskin of the decade old Visual Studio Online, which itself is a reskin on the two decade old Microsoft TFS) is somehow better than it. And everyone loves to hate on Microsoft products.

    Are there any actually good enterprise grade Task tracker + Code repo combo that we should be suggesting the execs migrate to? Maybe the GitHub Enterprise product?

  • source
  • parent
  • hideshow 1 child comment
  • load more comments
    view more: next ›
    36 comments in c/technology@beehaw.org view that post
    17 comments in c/fuck_ai@lemmy.world view that post