Hacker News Reader

The problem is once you connect Jira to Confluence to Team Calendars to Crowd to BitBucket Server you're very deep into the lock-in.

Nobody has either the time or the will to switch because, while all the software kind of sucks, it doesn't suck enough to the point where someone is going to stop working on their product and/or service to jettison Atlassian from their org.

View on HN

I was actually surprised how shallow and poorly functioning the integrations between JIRA / BitBucket / Bamboo and so on are. It all seems very basic compared to the default in OSS. In retrospect it's obvious that all of Atlassians products have been developed by separate teams / bought up and someone spent the bare minimum making each of them talk to each other.

Not so much. If the company is large enough then some teams will have enough clout to break away. Our company is mostly Jira / Confluence / Bitbucket, but our team uses GitHub SCM/Issues/Actions now. Since we've led the charge other teams are starting to migrate as well.

I have a lot of awful things to say about GitHub Actions but it's probably the best fit for our team.

Reply on news.ycombinator.com