As in the thread here? It's reviewed periodically, but the support site is the only place that I can guarentee the team read something.
Though please, as the first post/template notes - "use an example rather than 'any' even if it occurs with multiple", a report is much more helpful when we have an example of the teams and mode you were playing.
There's some overheads with running such a program - with the closed beta process we can accept a higher threshold of known issues or crashes, while if something was public, even if opt in, there'd need to be more time in on ensuring the builds are closer to production ready. The other issue, is simply that something we can do with a closed process is deliver something experimental, but then either substantially push that back or just drop it for a full rework - that's harder in a public environment.
You could maintain two separate tracks, but that again increases the amount of time internally spent on producing things other than the release product, which at times can be quite valuable, but it has to be planned for ahead of time - so something we would really have to be going into a game knowing that was the plan and optimising things around th
