https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24194
Owen Leonard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #77 from Owen Leonard <[email protected]> --- Right now if you have the DefaultHoldExpirationdate preference set and disable holds expirations Koha will still set a default expiration date. That's probably not what we want? I see that there are other preferences which don't apply if holds expirations are disabled. Also, could have have the preference called "HoldsExpirations." Although we have plenty of preferences which use "reserve," I still think it's better to use the correct terminology for new preferences. Otherwise everything looks like it works according to the plan, although I didn't find that this was true: > 4) In yet another tab, open the staff intranet and place a reserve for a > user. Check it in and set the reserve as waiting. Notice that an > expiration date has now been generated for this reserve. I only saw an expiration date getting generated if DefaultHoldExpirationdate was set. Not sure if that's a quirk of my test system or if I'm missing something? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
