7 ms·
I am not in the least bit shocked. Atlassian products are some of the worst glued-together garbage in the industry. The entire product surface area is probably
by echelon 5y ago
I am not in the least bit shocked.
Atlassian products are some of the worst glued-together garbage in the industry. The entire product surface area is probably rife with exploits.
Using Confluence or Jira will show you just how much Atlassian cares about its own products.
I'd love for this to be the straw that breaks the camel's back and makes IT/infosec orgs move away from this bilge.
- m_eiman 5y agoAny suggestions on what to use instead of Confluence? Need to run on-prem, it's mostly the wiki-like features I'm interested in.
- winkelwagen 5y agoWhat target group? Devs? Po? General org?
- mrweasel 5y agoI'll just go with "Yes" because we use the same Confluence installation our entire organisation. Spaces might be configured differently, but we can have all our documentation in one system and link across space. There really isn't that many alternatives, SharePoint maybe, but then you're just suggestion something worse.
- nix23 5y agoI migrated every confluence instance over to XWiki, since the Australian backdoor law[1]. http://www.xwiki.org/xwiki/bin/view/Main/WebHome http://www.xwiki.org/xwiki/bin/view/Main/WebHome https://xwiki.com/en/try-xwiki/ https://xwiki.com/en/try-xwiki/ [1] https://www.wired.com/story/australia-encryption-law-global-impact/ https://www.wired.com/story/australia-encryption-law-global-...
- skinkestek 5y ago> Need to run on-prem, it's mostly the wiki-like features I'm interested in. Since you are looking mostly for the wiki part there is Dokuwiki which is magnitudes better at being a wiki. Remember, wiki is derived from the Hawaiian word for quick or something to that effect and whatever Confluence is it isn't quick. Don't know how well it will hold up under scrutiny if black hats gets a reason to swarm over it, but unlike Confluence you can hire someone to patch the guts of it if necessary. Edit: I have no reason to believe it is worse than anything else, I'm just pointing out it probably hasn't had so much exposure to help it harden.
- bbarnett 5y agoThe downvotes make no sense to me. Maybe mentioning the value of open source, as you did, is disliked? Dunno. Weird.
- philpem 5y agoI get the sense that there are a few Atlassian employees on HN this morning... Jira and Confluence are "okay" at what they do, but they're horribly inefficient. I wonder how much energy would be saved if all the JIRA and Confluence server farms were replaced with single servers or redundant setups running something more efficient. Atlassian seems to be one of the subjects of the 2000's versions of the old line: "nobody got fired for buying IBM". Anyway the discussion in this thread is interesting to me - just to hear about the alternatives.
- detaro 5y agoFor a non-technical user group you likely want something more WYSIWYG than Dokuwiki.
- skinkestek 5y agoMaybe. But I have a hunch that we are severely underestimating huge parts of the workforce. I mean: ux discussions often feels like they assume users are a separate species somewhere between ordinary humans and chimps when it comes to intelligence. I have some experience with training users and I have only given up once.
- detaro 5y agoI fully agree that you can train users for a lot. But the question is if it's worth doing so in the specific case. And wikis often already have trouble with people not using them enough, making them seemingly hard to use doesn't help.
- skinkestek 5y agoDon't forget that in many ways some real wikis like Dokuwiki are simpler and more user-friendly than Confluence: - you can edit a paragraph without locking or creating conflicts for the whole page - it is much faster, and as far as I can see the observe–orient–decide–act loop is a real thing and should be taken into account - much better wiki syntax (compared to old Confluence) - trivially extensible so you can create forms and other helpers to make it simpler for users to do the right thing - if one absolutely need it I think there exist at least one wysiwyg extension for Dokuwiki
- polote 5y agoBiased but I'm actually building a competitor (V1 is almost ready) to Confluence for medium to big organizations. But I don't understand your requirement for on-prem. That's clearly not an advantage from the security point of view. Apart from Quip, Sharepoint and Confluence (soon stopped) I'm not sure there is any commercial knowledge base tool that are available on-prem. The only thing that you can hope for, is "bring your bucket" in which static resources can be uploaded in your S3/Google/Azure bucket and some managed instance (like Atlassion Cloud) for the app. But on prem is going to be something from the past honestly
- nix23 5y ago>I'm not sure there is any commercial knowledge base tool that are available on-prem. XWiki?
- polote 5y agoI personally do not categorize them to equivalent to Confluence, Sharepoint, Notion, Quip, ... but if you do, yeah there are few wiki software which are available on premise.
- nix23 5y agoWhat can confluence do what XWiki cannot? But i understand that you try to promote your cloud offering ;)
- polote 5y agoI'm not trying to promote my cloud offering. I would like to be able to offer self hosting, but we still haven't found a way to do it. This is too much hassle for everyone. There is a tradeoff between ease of use of a software and the security process. A collaboration tool which is difficult to update and thus will not evolve quickly is an issue for its adoption and for its benefits. Well first its interface, if a non technical user can't user the tool that's going to be a big problem. Confluence has not the best interface but still better than Xwiki. The best the interface the better the adoption as a whole in the company. And for knowledge sharing adoption is critical. That's actually why Notion has been such a success recently. Even though their product is average, people want to use it, because they like the interface. I don't have the time to do a full comparaison of other features, but wiki tools are in usage very different than collaboration tools. Can you have the list of last consulted documents ? Can you embed external documents ? ... Kind of the same things as Slack vs IRC
- unixhero 5y agoI am considering going with Bookstack Wiki for my company. But I am not a Fortune500 company. I would say it is very darn complete, perhaps without the syntactic linking that Confluence has. The only thing missing from it, is a very solid backup and restore method from the admin panel. The authors want users to rely on database backups and file level backups, that must be handled manually. Essentially saying "not my problem".
- ssddanbrown 5y ago> The authors want users to rely on database backups and file level backups, that must be handled manually. Essentially saying "not my problem". Just a note on this, this is something I'd like to build in eventually. It's just that each layer of our own we add upon the underlying methods increase the risk of error in something fairly critical. A simple command-line based backup solution wouldn't be too difficult to add, but restore and admin-panel usage are more significant challenges once you get into it.
- js4ever 5y agoYou can try Wiki.js or bookstack, both are open source and nice
- ssddanbrown 5y agoThanks for suggesting BookStack [1]. I did initially create the project as a free open-source alternative to confluence as I didn't want financial approval being a limiter to documentation collaboration. One of the main things to consider with BookStack is the semi-fixed Shelf > Book > Chapter > Page structure (Where pages have content, chapters & shelves are optional, and Books can be within multiple shelves). For some this structure is limiting, For others it helps drive organization. [1]: https://www.bookstackapp.com/ https://www.bookstackapp.com/
- plasma 5y agoYou could put Cloudflare Access (with Tunnel) in front to shield against exposing the instance directly, I’ve used it in the past for other products that has been good.
- mch82 5y agoMediawiki has worked well. I’d be curious to hear others experiences with it. VisualEditor is an extremely good WYSIWYG interface. The wiki is able to scale well (project sites are unlikely to approach Wikipedia scale). The API is useful. Wikitext editing gives power users a lot of flexibility, though it’s not as popular as Markdown. Access control & edit-publish workflow options may be too limited for the desires of some project teams.
- neovive 5y agoMy company is currently migrating off of Confluence due to the ending of the on-premise license. We found a combination of a simple web-based knowledgebase app for public content and Office 365/Teams -- which we already license.
- marcus_holmes 5y agoI have no idea why you're being downvoted - this is true. Atlassian produce some of the worst tech on the planet. Trying to administer this crap is horrible. And don't get me started on how many project managers spend all day staring at Jira tickets instead of actually talking to their teams. Management-by-Jira is a disease, a symptom of bad organisational culture.
- jordanbeiber 5y agoBut jira is only a tool right? Blaming Atlassian for a poorly led organization seems slightly misguided. At some project size, measured either by software complexity/interoperability or user base, you will need a tool to manage issues and tasks. What you're talking about is an organization where developers are not empowered - but even empowered developers need an issue tracker or a board of some description. A "management by jira" culture will not be remediated by tooling.
- galangalalgol 5y agoA good tool cannot guarantee good results, but a bad tool can shape its user's behavior in bad ways. The same individual without that tool might have behaved differently. I have seen this in what I call design-by-ticket where all the why and how for a design decision, including design by committee meeting notes, get put in jira tickets.
- jordanbeiber 5y agoTotally agree with your first two sentences. However, the final part has nothing to do with jira IMO. You would have the same behavior in these organizations regardless of tool. The dysfunction you describe goes way beyond a single or set of tools.
- galangalalgol 5y agoIt is hard to say for sure, but this organization used configuration controlled documents for design documentation before atlassian came along. When they made the switch (and hired oodles of graduates) suddenly about half of them ignore confluence or latex for design, because "jira has markdown". Oh hurray, we have a bad typesetting language mixed in with our bug tracker, lets shove our entire design in there! It is possible this is the influence of the graduates we hired, but it felt like everyone got there together while playing with the new toy.
- gjvc 5y agoAtlassian products are garbage. So why are they so popular? Because Jira is a wet dream for mediocre micro-managers (of all levels), allowing them to manage by ticket, instead of lead by example.
- niffydroid 5y agoBitbucket recently has shockingly poor reliability. Quite often you see nothing on the status page but see other people having issues on twitter. We've nearly migrated everything to github, plus github has better features and more powerful.
- indigomm 5y agoThey've been doing a large transformation recently to put it on a new platform. Not saying that's an excuse, but it is an explanation for some of the problems they've had.
- niffydroid 5y agoEven after this we had issues. Pull requests can take quite a while, diffs not working, git slow or timing out.
- dilyevsky 5y agoYup, moved from onprem to cloud afaik. Turns out cloud hardware has trash reliability and slow (particularly disk) Big shocker here
- grumple 5y agoI once said this too. Then I tried a bunch of their competitors. Still stuck with some of them. Sadly, some of Atlassian's products - namely Confluence and Jira - are the best in the business. Those complaining below about PMs staring at JIRA all day... well, this is a problem with PMs, not JIRA, and it happens even if they are using other work management tools. We created a middleman position in our business to deal with the stuff we didn't want to - tracking work, getting requirements, etc - and we must reap what we've sown. They become obsessed with the management stuff because that's why they exist, and they will fill their time to justify their existence.