Hi, normally you can assign the bug to yourself if the status is still NEW and not ASSIGNED, but we are a bit lax with setting the correct status sometimes, so leaving a note on the bug that you plan to work on something is probably good. I filed bug 7413 ages ago and it would be nice to see it resolved. My guess is that Kyle is/was the default assignee for Circulation module bugs and that's why he is named as assignee. Katrin
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Holger Meissner Sent: Monday, January 20, 2014 1:17 PM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Automatic renewal feature
Galen Charlton wrote:
Yes. Here is how I suggest doing it:
- add an auto_renew flag to both issuingrules and issues - when a loan is made, issues.auto_renew is set to the value of issuingrules.auto_renew from the loan rule that was applied. - the cronjob checks issues.auto_renew -- in other words, it doesn't go back and check issuingrules again, it just goes by the value set on the loan itself.
Very well. Additionally I suppose to add norenewalbefore to issuingrules. I'm not sure what it should be called? It's about when to renew, X days or hours before due date. This would be checked by CanBookBeRenewed and could be used to control the cronjob as well as solve bug 7413. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7413
May I assign 7413 to myself, or just write a patch without assignment?
Updated the RFC: http://wiki.koha-community.org/wiki/Automatic_renewal_RFC
Regards Holger _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha- community.org/ bugs : http://bugs.koha-community.org/