The problem is that a lot of people will reach for Gitlab to replace Jira, or MediaWiki/Dokuwiki (or again, Gitlab) to replace Confluence. But for businesses that have adapted business processes to use them, Gitlab/MediaWiki/Dokuwiki simply don't cut the mustard. We have an extensively customized Jira installation that's used for tracking budget requests, cage access tickets, and system change requests--none of those fit into a "bug/task/defect" tracker like Redmine or Github Issues. And for anyone who's gotten a manager using Confluence's editor, moving to writing wiki source in Dokuwiki is a big step backwards.

The thing Atlassian had going for them is that we could get our non-technical people to use their stuff, understand it, and even customize it themselves to meet their needs. I'm not looking forward to trying to bend some other issue-tracking system to do it, so I'm guessing we'll pony up for the DC-class charges (for the few years they continue offering that option) and see if a competitor emerges.