The fix will be available in our official release Q1 2016.
what is the status of this issue? it occurs in our product and many customers are not happy with that. can you speed up this bugfix a little bit?