to whoever is marking all the bug reports as “There have been no reproductions of this report since 3.13.1 went Live. ” on perfectly valid bugs , we cant update bug reports, we cant even edit them . unless the bug is massively in peoples faces those people reporting are the only people who bother to report .people will not bother with the smaller bugs because they dont have time or cant be arsed .Forcing the people who could be arsed to report it all again ,wasting their time
that the bugs where getting reported ,confirmed and then just thrown out without any testing
For context, knowing the latest version a given issue was encountered in is absolutely critical in such a dynamic environment, where we see issues come and go even between internal versions. It’s even possible to see an issue consistently on public versions, but struggle to reproduce internally. That information itself could help isolate the underlying cause. As someone who administrates the IC, it is one of the most common requests for information from developers.
The second part of the message recommends creating or contributing to a report that is updated to the latest version if the issue persists. Oftentimes, the closure of a report does not mean the end of the tracking for a given issue. We do keep internal reports open if there is internal information on them, but want to encourage up-to-date IC reports.
I can appreciate the frustration caused by this workaround to a current limitation of the Issue Council. There are lots of considerations to juggle, and after all, the primary goal is to provide the information required to development to get issues fixed! We are actively investigating ways to handle this in a more convenient manner for testers in the future. We’ll continue to adjust based on feedback and as features come online.