Known Issue after Patch 3.5 (Jan. 19)

Printable View