I just updated a 3.00 db to a 3.03.00.003, and discovered that the renewal rules were not translated correctly into the new rule structure.
Renewal rules (Itemtypes) pre-upgrade: http://screencast.com/t/kBEy1R79t8
Issuing rules pre-upgrade: http://screencast.com/t/Gw6Y0l9hvl6
Issuing rules post-upgrade: http://screencast.com/t/8AplaPge
Item Types post-upgrade: http://screencast.com/t/P0x3jB27w
It seems to me that the upgrade script should have created rules such as:
default:<itemtype> <everything the same as default> <number of renewals for that itype>
The only case where it wouldn't need to bother to create rules would be if all of the item types pre-upgrade had the same renewal limit
This bug was likely introduced with DB revision 3.01.00.065 (thanks gmcharlt)
and it's a little extra bad, since the previously set itype renewal limits are lost in the shuffle.
As this is related to 3.0.x - should it be WONTFIX?
Has it been resolved on another bug?
I haven't seen this behavior - going to close it.