Assigning this to next milestone, because the previous one is inactive, but we actually already released the fix for this bug.
Assigning this to next milestone, because the previous one is inactive, but we actually already released the fix for this bug.