To allow for the possibility of this issue being fixed in the OLH in a future release, I have set the Fix Version to future release.
To ensure that this issue is described in the Release Notes for 3.1.2, I have added the 3_1_2-release-notes tag.
Removed the 3_1_2-release-notes tag. This issue was fixed in revision 52253, so does not need to be added to the Release Notes.
Fix committed in revision 52253.