On-prem will keep existing IFF you have the capacity to pay for 500+ licenses. If you're a small to medium organization that still doesn't trust Atlassian to run your business-critical services (and there are a number of reasons why one might not want to: [0] [1] [2] [3] [4] [5] ) you're SOL.
It is pricey - I will not disagree with you. It is 1-500 is the license tier and that costs $42,000 per year for the Jira data center subscription, $27,000 for Confluence, BitBucket is $2,300 for 1-25, Crowd is $5800 for 1-500, and Bamboo is $11k for up to 25 users.
I would not connect any of these services directly to the Internet.
Yes, I know and that's why I'm asking. I suspect many companies I know are on the "Server edition" and I'm curious how much more expensive it will get for them.
We went from Server -> Cloud -> GTFO. Server also had tiered pricing starting at $10 for 3 users. It went up from there in much saner increments but I don’t recall them.
We exited the ecosystem at the last cloud price hike. Their product pricing people are delusional.
Thanks! I dug bit deeper and found old pricing tables. For Jira and the 500 to 1000 user tiers I'm interested in it was roughly about twice the money going from Server to Datacenter. Interestingly the Datacenter prices per user are similar to the cloud prices, so from Atlassian's perspective it is more a price adjustment with regard to the incongruous Server pricing. From the customer perspective it's still a bummer and I guest many will go straight to the GTFO tier.
Yet I still cannot import anything like in the old editor (e.g. markdown), adding images in lists was added two years after forcing switching to the new editor and you still cannot continue numbered lists in another item line and have to start over.
Extensions exist to do this but these things should be standard in any editor.
The new editor in Jira is drives me nuts. They replaced a perfectly good, functional markdown editor with the current POS, and it causes me problems nearly every single day.
Atlassian stuggles with editors like no other company I've seen.
I don't remember the last time I had a problem with an editor except for using any Atlassian product. Not sure what the fuck they do, but they really seem to have trouble with this aspect of their products. Which is ironic because their products are essentially CRUD products with a heavy emphasis on data entry.
Like, if anything out their products needs to work well, it's the editors.
I think it's related to how atlassian develops their products - they acquire then. Jira, confluence and Trello have three different editors because they're three different products developed by three different companies.
And yet, they are trying to move Trello to the terrible rich text editor like Confluence. So far you can still opt out and send a "wtf are you doing?" feedback about the new editor, but I'm not sure how long that will last.
> I don't remember the last time I had a problem with an editor except for using any Atlassian product.
I hate jira and don't like confluence but I've had more problems in sharepoint online editor with losing serious hours of work to synchronization bugs than confluence.
All the talk about the office being a magnet, not a mandate... needs to apply to products as well. Magnets, not mandates.
Atlassian hasn't added much in the way of new features to the cloud instances, and the cloud options often take a lot longer to return queries.
And frankly, the "migrations" were never great... upgrading form some customized version of Atlassian (or just highly configured) to the cloud generally moved / changed things. Meh, sort of inevitable, but also really tedious. And don't get me started on how miserable "half-migrations" were where some teams moved and some didn't, or Jira moved but Confluence didn't. Those months in limbo with multiple logins and issues getting created in the wrong places were torture. Atlassian didn't really help customers with all this -- I was told they wouldn't even help us clone the Jira server so we could run migration tests... we had to do it live. (Something about Atlassian not offering another license without us paying for the test server as if it were a real server.)
Moving off Atlassian seems like a good call!
I pushed my org (at the time) to move to GitHub... we ran a test program, and it was successful, but I left the company before it was completed. I was so much happier with GitHub.
Never quite realized these were the same company. Mostly because they were forced on us, we basically did the bare minimum on those platforms, and they never took off.
I observe load times that remind me of the 90s sometimes using their cloud apps.
Incredible they are killing on-prem, but maybe it makes it harder to compare to the slow as molasses cloud offering that way?