Comment by martinald

> I tried their AI stuff on the free trial, didn't work at all, tried to cancel, can't cancel the free trial online and had to write a load of support tickets (of which the support ticket contact form bugged out multiple times).

Absolutely insane that this is legal. The only reason to do this is to trick and abuse customers. It would be trivially easy to legislate away if our government cared to.

Atlassian seems like a typical entrenched big company, albeit an extreme example. They make money by selling to the bosses of their users and being the default name brand for many cases. Once a company gets to a certain size and doesn't directly compete much on quality internal corruption and incompetence can run rampant.

A result of their performance-review driven development. Every engineer, product manager and team is focused on one thing only. Get through the reviews. That means building feature after feature, projecting revenue/cost savings that may not materialize.

No one is focused on quality of the feature. It is all about speed. No one stops and thinks that may be users doesn't care about it. Data science teams are focused on cherry-picking data in a way that shows positive impact to show to the leadership that things are working. Engineers and teams are disincentivized to improve existing features, performance issues(unless it impacts revenue/some enterprise customer complains) and sometimes being punished for it. They are also steadily downsizing their support teams to cut costs.

Things are not going to improve. You should move away.

I worked there and the answer is the engineering talent isn't great, in addition to being very unfocused, and tons of pointless org churn. Bitbucket pipelines/workers was originally implemented, essentially, by two guys (I know, because I sat 2 rows of desks apart from them!) if that tells you anything. I doubt there was more than one person actively maintaining it for the past decade, if they didn't get laid off recently. That office doesn't even physically exist anymore, and the people are long gone.

Featureatis. Just keep pumping out features with no thought. Today, probably also AI-coded .

Even in mid-sized projects if you keep pushing for only new features you'll get a similar system. At least my experience in 3 or so midsized projects that I've worked on where nothing else mattered than checking of features from a huge backlog.

The search function in Jira has always been unusable. It’s perhaps the worst part of the entire platform, but nice to see they’re still focused on adding features I will never use.

Jira is buggy as hell these days. Lots of desyncing that forces me to refresh the page. I can have a ticket open on a sprint board and the modal spontaneously closes after a while, forcing me to reopen it frequently. The other week there were tickets that simply refused to show up in their respective sprint board no matter what I did; later the epic magically appeared on the board out of nowhere, then finally the individual tickets themselves reappeared.

Gotta love the value that vibe coding has added to this world.

You can add to this list: Every single input field they have in Confluence and Jira is misbehaving or broken. Apparently, we can't just have a text input widget that works well. Also apparently, this billion dollar enterprise cannot afford to write or use a proper markdown parser, and apparently we, the user lowlives, cannot be trusted with the full "pwer" of basic markdown laugh.

Jira has vim-like bindings for navigating tickets on boards and years later the feature barely works. It has bugs like pressing the j/k keys changes the URL and random fields but stays on the same ticket or doesn't render the newly navigated-to ticket, etc.

It can't be that hard to just dump/export the entire JIRA in one day and migrate it to something else like linear.app? i was already exporting HTML dumps of the entire JIRA and using it in local tool calls to ground agents as far back as last year instead of wrestling with JIRA API to get it to work. This was before linear became popular.

The migration would take 1-2 engineering man-days I suppose. But its money well spent.

Stack ranking

Here mine: you cannot link an existing branch to a jira issue. Maybe this is easier said than done but I can't find their reasoning anywhere

Umm? Is there single step Atlassian did it right? It's a cancer of software development the suits force us to swallow while real development and useful documents are outside of their service because it's so stressful to use.

Confluence is ok and has improved recently.

Jira is garbage (frontend, backend). Tough but true.

Until it starts actually affecting their bottom line, how is it a misstep?

You yourself just admitted that you still use their products often.

Sounds like every other SaaS company that was bought by investment fund to milk it dry till everyone migrates off of it.

Not surprised. Quote „…with significant institutional ownership from Vanguard, BlackRock, and others”.