When checking out materials if you specify a due date but don't check the 'remember for session' box, Koha remembers the date anyway. It should only remember with that box checked. This is so in 3.10.x, 3.12 and master.
What i had found when doing this is that without the box checked it held the custom date for all the transactions for that patron. It I checked the box to remember the custom date, it held the dat for all the following patrons.
Hi Nicole, I think you are right and I would say that it works like it should. Remember for session remembers the due date until you close your browser - for the whole session. So even if you open another patron account, it will still be the due date you picked. When you don't check the checkbox it will only remember it until you unset it or leave the circulation page. If we changed that behaviour and you have a couple of books for one patron to check out with a special date, you will have to use 'remember for session' to do that without having to reselect the date all the time. But having it remembered for the session requires you to explicitly remember to remove it before checking out to the next patron. So that seems more dangerous.
We have a workflow issue with the 'Remember for session' button. When using remember for session a checkout is required to allow the date to be cleared. Current behavior is: 1 - Set date and check remember for session 2 - Checkout to all patrons as needed 3 - Load next patron 4 - press clear 5 - checkout an item expeceted/desired behavior would be: 1 - Set date and check remember for session 2 - Checkout to all patrons as needed 3 - Press clear 4 - load next patron and date remains cleared
*** Bug 11289 has been marked as a duplicate of this bug. ***
Nick, not sure what you described is a bug. If the form is not submitted I would not expect the value to be modified. I am lowering severity here.
Hi all, I'm closing this bug. Seems like Nicole and Nick both expected different behavior from what Koha does. But the current behavior seems to be what was intended by the code and also is very well established. If anyone's interested in an enhancement to give the option to make this work differently, let's file a new enhancement for that.