At it's core, I believe an issue tracker is fundamentally the wrong pattern for developing software and the same pathologies crop up over and over again.
Issue trackers seek to accomplish multiple goals: They are communication mechanism between departments, they're a way of tracking the state of progress, they're a means of prioritization and they're a way of evaluating progress. Because these goals lie fundamentally in tension with each other, the same problems predictably occur with long time use of an issue tracker.
Issue trackers are like shopping lists without price tags. if you imagine an Amazon Wishlist with all the things you want to buy in life, it's not hard to imagine the same graph appearing. Somewhere mixed into all those items is a ferrari and also the washer you need to stop your tap from leaking. And, of course, the list is going to get exponentially longer as time goes on, even as you check items off. But the reason we don't get stressed about our ever expanding wants list is because price serves as an intuitive gut check over priority and, as long as we see our personal living standards improve, we don't care that we can never fulfil all our wants and we don't bother applying "won't buy" or "item does not exist in real life" tags on our list. (this is an analogy, ok. Please don't try and fight the hypothetical on this, I'm aware our economic wants are significantly more complicated than that).
One of the ideas I've been tinkering with is to treat issue tracking less like a todo list and more like a storefront. A todo list with ever increasing entries is stressful experience, a storefront with expanding inventory is not. Items would have a base cost associated with it and a "shipping cost" so that 2 day shipping costs more than USPS ground (aka: Whenever we can get to it). External clients get to create items on the storefront, set the price and the shipping costs using some kind of artificial currency and engineering gets to figure out which orders to fulfil and in what order to maximize revenue.
Of course, to paraphrase jwz, "You have a problem and you think "Oh, I know, I'll solve it with an artificial currency". Now you have two problems".
Still, I think it's worthwhile getting back to the foundations and think of what an issue tracker does in the context of software development and whether there's a better thing that could serve the same purpose.