Also, thanks for bringing this up. I’ve filed a bug report on it with our developers; I can’t say when they’ll be able to roll out a fix, but hopefully they’ll be able to add it to a future sprint.
Is there anything else we can help with on this or should we mark this as Solved (pending future release)?