Please don't tell me that Jira is about to get even worse... I don't understand the AI layoffs; there's always an infinite supply of new work that could be done. Instead of firing 1600 people, why not have all of them use AI to produce more stuff and outrun their competitors. Presumably all their competitors also know about Claude as well, and a lot of these 1600 people will go work for them and use Claude. Unless th…
If everyone else is downsizing and using AI as an excuse, it's both a pretty good cover for any firing you might have wanted to do for a while, and you can reasonably assume you can hire back in the future because everyone else is firing too. Maybe you can even depress their wages a little?
Atlassian to cut roughly 1,600 jobs in pivot to AI
311–320 of 320 posts
Re: Atlassian to cut roughly 1,600 jobs in pivot to AI
#312Atlassian is cutting jobs because no new sane company wants to use their products. Confluence was once innovative but now has gone stale. Jira is a nightmare and is most ripe for the AI based replacement. Bitbucket is a neglected product that has lost ground to GitHub and GitLab. The writing has been on the wall for Atlassian for years.
Re: Atlassian to cut roughly 1,600 jobs in pivot to AI
#313Re: Atlassian to cut roughly 1,600 jobs in pivot to AI
#314Earlier quoted context omitted.
Redmine comes to mind? Or if you use jira for helpdesk then Request tracker
Also possibly OpenProject, which is an "open core" fork of Redmine
Re: Atlassian to cut roughly 1,600 jobs in pivot to AI
#315Earlier quoted context omitted.
Atlassian Rovo is considered utterly dangerous on my team (as we are still encouraged to use it…), the first time I did it erased a whole page - it couldn’t get the most basic instruction correct, would leave out 80% of what I input, respond to corrections with the same problem. It’s just a liability.
Rovo dev cli is pretty good though. Though that may just be because it talks to claude or openai in the backend.
Re: Atlassian to cut roughly 1,600 jobs in pivot to AI
#316Does Atlassian still have the tech debt that lead to extended outages? https://newsletter.pragmaticengineer.com/p/scoop-atlassian
Re: Atlassian to cut roughly 1,600 jobs in pivot to AI
#317Earlier quoted context omitted.
I'd argue the opposite. The thing is so bloated and the simplest of things seem to be so hard. Import markdown in confluence? Nope not natively. Add an issue to the board? better go to the one workflow to do it and not in the actual ticket.
Confluence supports markdown natively. Even its MCP uses markdown. I don’t know exactly what the other issue is referring to.
Re: Atlassian to cut roughly 1,600 jobs in pivot to AI
#318Earlier quoted context omitted.
Also possibly OpenProject, which is an "open core" fork of Redmine
Thanks for the mention. Just to clarify: OpenProject is a fork of Redmine and fully open source, so not open core.
I'm not complaining, as the free tier seems feature rich by itself. Just wanted others to know, especially if this has a chance of changing over time once people have committed to using it.
Re: Atlassian to cut roughly 1,600 jobs in pivot to AI
#319Does Atlassian still have the tech debt that lead to extended outages? https://newsletter.pragmaticengineer.com/p/scoop-atlassian
No, there was a big internal project (which they communicated publicly about - search for the blogs relating to it) to address it that involved roughly a year of effort from a big chunk of the developers.
Re: Atlassian to cut roughly 1,600 jobs in pivot to AI
#320I don't get the atlassian backlash on HN JIRA is just fine, gets the job done. Its not slow like the on-prem. Jira cloud version is fine.
I haven't looked at it recently but always felt that tools like Jira encourage poor management. Effective teams are small teams, and small teams should be communicating and working together across issues freely and frequently. It's generally harmful to have a manager assigning tasks outside of the actual day-to-day discussion without having to speak to someone directly or preferably in an open chat or thread where pe…