I'm unable to replicate this on the community demo server running 3.1.4. I can try upgrading it to 3.1.5 later this week to see if something was added during this time period to make it break.
We did see this issue in early testing on bug 1712854 that was fixed here - http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=4b4e283e30c332f6dca9dea997e58d0e935f0808. However, there is no reason that this bug should have made its way into the 3.1. series.
I'm unable to replicate this on the community demo server running 3.1.4. I can try upgrading it to 3.1.5 later this week to see if something was added during this time period to make it break.
We did see this issue in early testing on bug 1712854 that was fixed here - http:// git.evergreen- ils.org/ ?p=Evergreen. git;a=commit; h=4b4e283e30c33 2f6dca9dea997e5 8d0e935f0808. However, there is no reason that this bug should have made its way into the 3.1. series.