JIRA is not a drop-in replacement for good ol’ fashioned software design and documentation, and no one ever said it was. The author mentions things like common

JIRA is not a drop-in replacement for good ol’ fashioned software design and documentation, and no one ever said it was. The author mentions things like common models and complex cross-application components. Who ever said JIRA was supposed to somehow capture those things? It’s not! If you’re using JIRA for things like that, you’re doing it wrong. I think the danger is that JIRA IS being used more and more as a design and documentation tool while we ngleglect using some of the more well-established practices of years past, such as use-case diagrams, class diagrams, requirements documents, wireframes, etc. We try to capture too much design in the various types of tickets, but that in my opinion is wrong because JIRA was not originally designed for that. In that way, JIRA itself is not a anti-pattern, but how we use it certainly can be.