This is kind of hilarious since a lot of places where I've used Atlassian products seem to have more or less hated them but still put up with them for the sole reason that they are on-prem, and the competition available for the entire "suite" or whatever is pretty sparse. I'd be curious to see what kind of market share is estimated to be "on-prem, won't switch" because it sure isn't zero.
Atlassian prepares to abandon on-prem server products
141–150 of 205 posts
Re: Atlassian prepares to abandon on-prem server products
#142Earlier quoted context omitted.
YouTrack by Jetbrains is very good
Can anyone speak about YouTrack/Space's warts? The marketing blurbs makes Space + YouTrack look like a decent replacement for Jira + Confluence + Bitbucket, but I don't recall ever hearing a developer talk about it.
A decade ago when we used JIRA team-wide and not org-wide, some teams internally preferred YouTrack so they used that (until the whole org moved to JIRA). What bothered me personally was that fields were basically "unschema'd" and everything suggested every value -- everything was effectively a label field -- including typos, which are more common in a company where English is second language.
But that was a decade ago, and it could've been a misconfiguration on that team's part. It was also back when JIRA was more of a structured database with real issue types and not stories atop stories for all eternity.
Re: Atlassian prepares to abandon on-prem server products
#143One day the pendulum will swing back in the other direction. Until then, those of us who disagree with putting absolutely everything into the cloud will just have to sit back and bide our time.
> will just have to sit back and bide our time I doubt that day will ever come without a significant number of potential customers stubbornly opting to go it alone with DIY on-prem alternatives (or at least somewhat SaaS-less - e.g. turnkey-on-IaaS or similar) in the interim. Though I guess that "stubborness" might become more likely as more & more stagnation & inflexibility of cloud SaaS reveals itself to customers…
For many companies anything but on-prem is not an option.
edit: and in fact the DC edition is still an option.
Re: Atlassian prepares to abandon on-prem server products
#144Earlier quoted context omitted.
As a former Atlassian administrator, I believe the opposite. Maintaining the system on-premise was a bigger risk. The products are too complicated to be packaged nearly with a bow for sysadmins. You inevitably start having to become at Atlassian SME just to keep that shit running. I’m all for your company going with an alternative product, but for a company who would rather stick with Atlassian products, you’d be ins…
How is the product so terrible that running a 100 person instance is a pain in the ass?
Classic JIRA is very flexible into shaping a workflow, but it's sort of a very long pipeline of: schemas, fields, workflows, project templates, etc. I loved that flexibility and being able to drill down into a bug report, but it definitely took time to set up, and occasionally unravel & put back together when you needed to fix something small.
There's also the usual stuff of finding & setting up plugins, and then looking for a maintenance window that people can agree on, while side-stepping those settings you forgot needed a restart to apply (thus bringing your live maintenance to a halt because you can't bring it offline now).
Re: Atlassian prepares to abandon on-prem server products
#145Re: Atlassian prepares to abandon on-prem server products
#146Earlier quoted context omitted.
I should point out that multi-level epics are only available at Gitlab's $99 per user per month level. We wanted to use them, but it's not worth that much. Jira is a lot more flexible and cost effective in this regard.
99 per user per month is crazy expensive IMHO.
And it's not just for developers who might be using the expensive stuff (git, storage, CI minutes). Also for members of the org who only use tickets.
Re: Atlassian prepares to abandon on-prem server products
#147Earlier 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?
For something quick and easy consider https://github.com/gollum/gollum#markups which powers Github Wikis.
Note that multi-user auth is NOT supported out of the box however.
Re: Atlassian prepares to abandon on-prem server products
#148Earlier quoted context omitted.
Obsidian is a pretty good solution for this in my experience
Obsidian does not support collaboration. It's a fantastic tool but strictly singleplayer.
I used it with a team of 10 folks at my previous job. Everyone worked in a common git repo, and with some smart usage of .gitignore, we were all able to collaborate quite effortlessly, even going so far as to push videos, images, etc to the repo with git-lfs to make the documentation rich and available. It can certainly be multiplayer with a modicum of effort.
Re: Atlassian prepares to abandon on-prem server products
#149Last 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…
Plus, the cost of gitlab is getting insane. It's very hard to justify the jump, no matter how worth it is. Jira "just works" for now, and honestly it wouldn't surprise me if gitlab raises their pricing even further. (which I totally understand, they are not profitable yet and have to do a lot of work. It's just that it sucks having to be cautious about who gets access to your instance since you can't have multiple ti…
It's interesting that way, I assumed removing the silver tier and not having a real "personal pro" priced tier was just because the long tail wasn't worth it for them if they had to make a support commitment. So to hear the pricing is uncompetitive at larger scales too makes me wonder who they're pricing for
(However, to be fair the free plan includes some stuff that is only on the team plan for github, like 5gb for gitlab free vs 2gb for github teams)
Re: Atlassian prepares to abandon on-prem server products
#150Earlier quoted context omitted.
Obsidian does not support collaboration. It's a fantastic tool but strictly singleplayer.
I used it with a team of 10 folks at my previous job. Everyone worked in a common git repo, and with some smart usage of .gitignore, we were all able to collaborate quite effortlessly, even going so far as to push videos, images, etc to the repo with git-lfs to make the documentation rich and available. It can certainly be multiplayer with a modicum of effort.
Wouldn't be feasible for most of our users but nice to know...