The community member says communication about known bugs and how Issue Council tickets are prioritized seems broken. They point to the 10-day TTL on new tickets, critical tickets left unresolved for years, and bugs that persist and are replicated in newer ships, and asks for better handling.asked by to-the-valhalla

Issue Council is an incredibly valuable tool for us, and while I agree that we need to improve the communication around the status of certain prevalent issues, the impact that IC has on the day-to-day process is significant.

We receive daily reports from our QA team that include top-reported IC issues, surging issues, but also issues the team feels have flown under the radar and are being under-reported. These reports get reviewed daily by key folks in the project's leadership team and inform the priorities for a lot of staff.

And while yes, there is a high volume of reports, our Player Experience and QA teams are working really hard to make your voice heard. They curate it in a way that makes it clear, actionable and easy to triage. This saves additional round-trips between Dev and QA.

Reproductions and regressions between release versions can have many causes. A frequent one I see is that we're implementing a temp fix we're not intending to keep in one release, and while the true fix is still in progress, players have reproduced it in a later release's PTU cycle. A recent example of that are issues concerning QT travel that reappeared in 4.2.0, after a temp fix was implemented in 4.1.1, iirc. There are of course other factors, but this year in particular, we've invested a lot more time and effort into regression testing internally to avoid the previous example altogether.

I hope this provides some insight into how crucial IC is, but more importantly, that our QA and Player Experience teams are raising critical issues directly to key people in development to get them fixed. What's getting in the way of one particular issue not getting prioritized is usually other priorities.