Almost everyone in this comment section is getting the article wrong. > JIRA1 is all too often used in a way which makes it, inadvertently, an industry-wide “a

Almost everyone in this comment section is getting the article wrong. > JIRA1 is all too often used in a way which makes it, inadvertently, an industry-wide “antipattern," Key phrase here is "all too often". > That antipattern is not JIRA’s fault … exactly. But JIRA’s structure contributes to it. > It’s very good when you’re at the point where breaking things down into small pieces and finishing them sequentially does make sense. And, unsurprisingly given its history, it’s exceedingly good at issue tracking. These quotes seem to be missed by folks here. This article isn't about JIRA, really, it's about JIRAs use across many companies. These comments are so transparently defensive, I'm actually surprised by how poorly understood this article is.