Earlier quoted context omitted.
The closer you are to agile the more basic your ticketing system needs and vice versa. You could probably do without one at all even.
^ You nailed it. The only issue tracker you need today comes with your source code repo. Both github and gitlab are not only more than sufficient, they are arguably better because the stripped down natures keeps people from doing silly things like all the jira anti-patterns.
A client of mine decided to ditch Jira last year. Now what they do is use a much simpler system but with a ton of manual wrangling going on constantly. Lots of duplication across boards, most tickets are in the wrong state, nobody knows who's supposed to be handling any given task. I'm mostly trying to stay away from it.
Your theory works if there are only developers, and they are all competent. Throw the usual mix non-dev staff into the mix along with the and it's a mess.