We've discussed the issue with the QA team and it seems that this bug has already been delivered to the Dev. team who has a fix in place for patch 2.2.

We're very sorry for the inconvenience this has caused.