Comment by subscribed

6 hours ago

But they (CC team) confirmed this is the case and intended behaviour, and closed the issue as not planned.

0 comments