JIRA as a generic issue tracking system is fine - and to the extent that it's used as a generic issue tracking system in cases where you actually need a generic

JIRA as a generic issue tracking system is fine - and to the extent that it's used as a generic issue tracking system in cases where you actually need a generic issue tracking system, it's acceptable (bugzilla was just fine, too, though). It is very useful, when somebody identifies and reports an issue, to have an "issue #" to associate with it so that if somebody wants to know whatever happened to issue #34, they can just go take a look and see that it was never assigned to anybody, or it's already been fixed, etc. The problem is when "scrum masters" start trying to apply Taylorism (the only thing they know) to software development on top of JIRA. That's when you get JIRA tickets with vague descriptions like "simplify login flow" or "reduce memory usage" and some self-important jerk insisting that you either assign a "point value" to it and finish it in two weeks or "break it down into smaller chunks that you can estimate".