The Recent Cargo elevator incident is a clear sign that the communication between community and dev team regarding existing game issues is broken of not sufficient. - The way some bugs getting prioritization over the others is completely unclear. - 10 day TTL for new tickets leads to situations when even critical bugs do not get enough recognition. Sometimes that is caused by lack of players initiative, sometimes due to the limited amount of owners of certain ships. - Even tickets marked as "Critical" can be forgotten for years, even if they affect gameplay seriously. - Bug replication in newer versions and ships mean there are quality control issues in the development process. Here is a good example of a bug that lives through many game versions and not only gets unrecognized by the dev team but also gets replicated in newer ships. https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-176937 https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-175773 https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-170011 https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-162321 https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-35935 etc - This is an issue that significantly affects ship usage for several gameplay loops - The fact that it is replicated in the newest ship shows that the ship didn't pass simplest test - open storage multiple times. Similar situation happened to the elevator issues. There were dozens of IC tickets related to multiple cargo elevator bugs, but they were ignored for a long time, which led to the current event drama. Of course, I understand that players creating hundreds of tickets per day, and it is hard to handle all these issues. However, there are clear signs that current development and quality assurance workflows do not effectively utilize such a major tool for communication with your player community.