https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25711
--- Comment #14 from Joonas Kylmälä <[email protected]> --- (In reply to Joonas Kylmälä from comment #12) > (In reply to Katrin Fischer from comment #11) > > (In reply to Joonas Kylmälä from comment #10) > > > I think we should completely remove ExpireReservesMaxPickUpDelayCharge > > > syspref now and move it's value with a DB upgrade to the default circ > > > rule. > > > > For existing installations that will cause no disruption, but for the next > > person introducing this to their collection it might cause a lot of extra > > work - even more values to enter and make sure nothing has been missed. I've > > been wondering about this with other "moves" to the rules as well. > > Can you clarify how this would cause more work? I don't understand. I think I might understand, so if you have in the default rules multiple different rule lines I think you mean we would have to define the charge for each of those. Hmm, so I wonder if we can allow the value to be undefined and then add a one rule in the end for common rules, or we could maybe make this bug depend on bug 15522 which should make defining the rules a lot simpler. -- 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/
