...hmm, isn't it fixed in PR1.2? if not then at least as far as I can see the fix is in PR1.3 code....
Yes that's correct, I strongly urged the release manager, multiple times, to put the fix into 1.2 but it didn't make it in. I've also done the same for the next release, including more requests this week, but unfortunately the fix is still not in that yet either. As best I can tell release management doesn't understand/believe that it's important that this bug should be fixed and that fixing this issue should be considered high priority. It can't hurt if customers continue to request this bug be fixed, in comments and by voting for this bug.