You're right. I made a generalization out of multiple threads here on HN and on Twitter (another example coming to mind being this one https://twitter.com/GergelyOrosz/status/1440242068102680595), but only cherry-picked one to illustrate the post.
The point I'm to make in this post is that _regardless_ of JIRA qualities (or lack thereof), the way many companies try to use it for conflicting purposes is a recipe for failure. Using JIRA for what it is designed to do is perfectly fine :)
I wouldn't call a single tweet about an individual experience widespread rejection. Jira is a great tool in many ways and how much it sucks working with it only depends on what you force your employees to do with it.
For instance we use it to capture requirements and progress only and people are generally happy using it that way.