Live data from Hacker News

Atlassian prepares to abandon on-prem server products

theregister.com

71–80 of 205 posts

Re: Atlassian prepares to abandon on-prem server products

#71

Why would they continue with on-prem? It has to be a support nightmare.

It doesn’t make them as much money (and on-premise continues for data center licenses so they wanna milk that, too).

Atlassian support has been decent to good and I’ve rarely had to even contact them, you could almost always find what you needed on the support site or via a search.

Re: Atlassian prepares to abandon on-prem server products

#72
post #27

no amount of complaints from... everyone about jira/confluence being absurdly slow or horrible to use had any effect on my employer (large multinational) but their decision to abandon on-prem has resulted in the company migrating away from all atlassian products the best thing atlassian have ever done!

But they're not abandoning on-premise, though one could get that impression from the tone of the article. They are only dropping the small-business targeted Server tier, they are keeping the enterprise targeted Datacenter tier. It's pretty much a drop-in replacement, with extra capabilities. And annual payment instead of initial+upgrades payment.

I think the underlying issue is that too many “big enterprises” were running server licenses and Atlassian wants more money and annual contracts.

Re: Atlassian prepares to abandon on-prem server products

#73

Why would they continue with on-prem? It has to be a support nightmare.

They will continue with on-prem, or as they call it “Data Center”.

They charge a lot for it, but the option is there.

Why? They probable have a bunch of large customers who will never accept going to a public cloud.

Re: Atlassian prepares to abandon on-prem server products

#74
post #29

Reading this news makes me happy because I know someone somewhere is likely going to be have the chance to argue that it's time to migrate away from JIRA and Confluence. I personally they haveheld back nearly every organization I've worked for in some way or another over the last 15 years. These Atlassian products are the destroyers of enjoyment, satisfaction, project management and productivity. Issues I've encounte…

JIRA is like Salesforce or any large enterprise “customizable” software package - by default all it does is expose all the organizational chaos and insanity.

Re: Atlassian prepares to abandon on-prem server products

#75
post #66
post #60

Earlier quoted context omitted.

We're in the same boat. I brought Confluence into our org almost a decade ago — it was the best collaborative wiki tool at the time. Over time the price has increased while the quality of the tool has not kept pace with other options. This seems to be the trend as software companies grow into large "enterprise" providers. Looking at our Confluence usage over the years, I noticed that we use it primarily as a knowledg…

Could you share what markdown/git tooling you've identified?

Not speaking for the GP. I use MkDocs and keep my personal notes. The only weak spot for me is that I haven't fully grokked search and as my notes grow, it can be harder to find things. I alternate between figuring out how search and how to bolt on some other search utility.

MkDocs includes a utility to publish to Github pages but I keep my notes on a self hosted Gitea server and serve using "python -m http".

Re: Atlassian prepares to abandon on-prem server products

#76
post #33

Earlier quoted context omitted.

While Jira does many many things right, it is also horrible in so many ways. What options are you evaluating?

Despite the "Azure" name, Azure DevOps Server (formerly Team Foundation Server), is still a rock-solid on-prem system for git repo hosting, issues/stories/projects, build automation, and the rest - though I feel it has stagnated somewhat, and git integration still feels half-baked compared to TFS's previous SVN-clone, but is still my first-choice for on-prem installs (granted, I'm still wedded to the MSFT stack).

ADO is the death knell to collaborative modern teams. Who the f wants to waste their day with that UX and feature set?

Re: Atlassian prepares to abandon on-prem server products

#77

Last year I was second guessing myself if migration to Gitlab EE from Jira, Bitbucket and Jenkins would be worth it, as it was a massive shift for my org. Maybe purchasing a DC version of Atlassian products would be a better alternative, but after short look into invoices and licensing it was decided to go forward with Gitlab. Still not a big fan of how stiff Yaml pipelines feel in Gitlab CI and that tickets for what…

Are you using the docker executor, or Kubernetes? For Kubernetes, we found that GitLab has a tool that automatically does that: https://gitlab.com/gitlab-org/ci-cd/gitlab-runner-pod-cleanu...

It was just an example of a number of small things and issues, that we were not expecting to be an issue by the 15th major release, but in general it's ok. We implemented a workaround.

Re: Atlassian prepares to abandon on-prem server products

#78
post #34
post #30

Earlier quoted context omitted.

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…

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.

Jira and Confluence were both developed in-house. Trello was acquired.

Re: Atlassian prepares to abandon on-prem server products

#79
post #33

Earlier quoted context omitted.

While Jira does many many things right, it is also horrible in so many ways. What options are you evaluating?

Not OP, but we moved to Gitlab Issues. Project Managers are missing some features, but the devs (including me) like it a lot more due to integrating so well with PRs/commits.

One of the challenges of Gitlab is that the pricing does not work well in organizations where a significant portion of accounts would need to be non-developer roles.

With devs and a premium tier, this isn't bad... but the "ok, we need to double the user count and move from premium to ultimate, even though most people are only looking for multi-level epics and the reporter role." That represents a significant cost increase.

Taking all the devs from $29 to $99 and doubling the accounts is a lot more than $15 per account (devs, ba/pm/mgr, business).

Post reply on HN