This article reminds me a bit of the Java advocates who used to pop up in every discussion comparing programming languages and remark that, well actually, Java'

This article reminds me a bit of the Java advocates who used to pop up in every discussion comparing programming languages and remark that, well actually, Java's reputation as a slow language full of boilerplate is wholly underserved and JVMs are in fact beating speed benchmarks left and right. And it's not wrong - you can write fast and concise Java if you are very disciplined, know exactly what you are doing and stay clear of most dependencies. However, that's hardly relevant in practice as both the language as well as the ecosystem and the established "best practices" want you to abandon both conciseness and efficiency in favour of some vague goal of extensibility. I think it's the same with Jira. Sure, you can use Jira as a simple Kanban board, but then, why would you buy a Jira license in the first place? There are cheaper tools for that. On the other hand, even if Jira advocates tell you that insanely complex workflows are wrong, all of the software is geared to supporting exactly those kinds of workflows. So if you're actually want to get your money's worth from a Jira license then you'll have to design complicated workflows and add numerous special fields.