I mean, Issues is not really a full-featured issue tracker. It could have been, and maybe would have become one when you were still there, but right now, it's not. And if you do need something more, and you have some resources within the organization, you're not going to stew over Issues...you're just going to use something else. Jira...Pivotal...whatever.
I'm sure GitHub doesn't feel that Issues is where they make their money. And/or that developing Issues further either won't make them anymore money, or not enough to matter. People don't choose to use GitHub for its issue tracker, and even if they had a great one, people still probably wouldn't choose to use GitHub because of it. And so Issues languishes in its current state.
But Julian Dunn has a point to make--maybe this press burns enough for GitHub make changes after all.