https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23445
--- Comment #5 from Katrin Fischer <[email protected]> --- (In reply to Marcel de Rooy from comment #4) > This might be just a theoretical thing: But I would rather not introduce > Undefined here. Just as in the code of Circulation, I would go for if ==days > then days else hours or even better if ==hours then hours else days (since > days is the default). I think that would be hiding possible problems in the database from the GUI. I and probably other tend to edit the issuingrules in SQL, especially for loading them the first time. If you have a typo or other issue there, you'd hide it. It's only in the GUI. We can also imagine that at some point minutes will be introduced (there is already a bug report) and that makes the logic there obsolete. Note: Undefined doesn't appear in the pull down! -- 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/
