Our bug tracker isn’t publicly available, but you can track the release notes for the current version and the release notes category.
When we address the issue, it’ll show up there as SG-16940.
I can’t give you an ETA but the issue has been prioritized really close to the top of the pile. 