Good example. The replies to this one clearly show the impact this is having:
Still going:
Some report closures are self-explanatory. I’m linking the ones where it’s hard to understand why they were closed (the one above is a warning being printed in the Studio console—how could this not be a bug?).
1 Like
Hey,
I’d appreciate if you could review the above replies, and see the amount of times this bug filer has needed correction from either other bug filers or engineers who have so kindly stepped in to provide more info when he hasn’t.
I just came across this report, where he closed it as a duplicate and linked an internal Jira ticket as the original…
2 Likes
There’s literally no way… he gets notified every time you link one of his posts, how does stuff like this even happen???
1 Like
Hey everyone!!! Thx for the heads up on all this, we’re taking action, shouldn’t happen anymore 
3 Likes
Hey,
Once again thanks a lot. Maybe said changes haven’t taken effect yet, but I wanted to note that a few hours after this reply, this is still happening:
1 Like
These should all be open again - let us know if you find any more, we’ll open them back up.
1 Like