Covering both of the issues listed above, we are actively working on dislodging ourselves from the Tracker system. It is clearly disliked by a vast majority of our customers, to the extent that they mostly only put in bugs begrudgingly, as they know the system will crash, or not update them when the bugs are fixed or many other issues. We are looking at moving to another tool which is used currently across Adobe on all of the CC and Doc Services platforms, and has also been used for some of the Alpha/Beta programs we've engaged in over the years. We are working on making sure this system will cover our needs, but as its one I'm somewhat familiar with, I can say I think it will end up being approved and we will hopefully begin the migration later this year. There's a LOT of work to do to move this. We will need to migrate all of our tickets over, update websites, relink JIRA, etc. So please be patient. This has been one of my pet peeves since I started and my voice (and yours) is being heard, but it is a colossal task. Thanks all.

@Mark Takata (Adobe) I actually think the current bug tracker could be much more livable with just a little bit of attention improving the rough areas and making it easier to use. I'm surprised Adobe is considering a herculean effort of migration to a totally different software, when they've let the existing bug tracker sit with no improvements for years. Why not just spend a fraction of the time improving the problems in the existing tracker.