There are a lot of duplicates and "non-bug" bug reports as well. FDEV should do a cleanup action to merge the duplicates and remove the "non-bug" reports. That makes the issue tracking process a lot easier and more clear going forwards. As someone who inherited the issue database used by a former group of mine (before it became my former group), which contained a serious amount of Change Requests, I always made sure that we would resolve or remove the Problem Reports as soon as possible (removed if they could not be recreated at our site as solving bugs that can't be recreated is an impossible task). But we could have really done with a cleanup of the parked CR's as well. Because let's face it: Change Requests that will never be implemented might just as well be reported back to their submitters as such and then removed. There is no use to keep those clogging up your issue tracker.Well - Issue Tracker was released over a month ago. At this moment out of 1654 reported bugs 26 is acknowledged by FDev, 14 were fixed in previous update, none of them have "by design" or "invalid" status. Either they dont have time to go through all those reports or just waiting for something (maybe some functionality of Issue Tracker is still at work - like merging duplicated bugs etc).