Earlier quoted context omitted.
I am fascinated by how complex JIRA is. We evaluated it in 2008. It seemed fine enough. Looking at it 16 years later, and… what is this nonsense? It’s so customizable that it’s loaded with footguns.
I have a theory: Back in 1996 Bugzilla worked very well. It had been designed, and honed, by a bunch of senior developers who also wrote the bug management system. So lots of dog food eaten. iirc it was written in Perl. Then, someone I believe decided to make a "Bugzilla in Java", because they didn't like Perl (reasonable). But whoever that was didn't have the deep knowledge of how the thing was supposed to be used.…
https://confluence.atlassian.com/plugins/servlet/mobile?cont...
> We originally used Bugzilla for bug tracking and the developers in the office started calling it by the Japanese name for Godzilla, Gojira (the original black-and-white Japanese Godzilla films are also office favourites). As we developed our own bug tracker, and then it became an issue tracker, the name stuck, but the Go got dropped - hence JIRA.