https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29194
Nick Clemens (kidclamp) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off --- Comment #7 from Nick Clemens (kidclamp) <[email protected]> --- (In reply to Marcel de Rooy from comment #6) > (In reply to Nick Clemens (kidclamp) from comment #0) > > Bug 28153 comment 3 suggests the preferences should be ordered > > > > Alphabetical could differ in different languages, and I think that would be > > confusing > > Not sure why. A staff user will normally use one particular language, I > suppose. I think assuming there are bilingual staff in some libraries is not a stretch. The point was really that it won't be a logical grouping if alphabetical > (In reply to Sam Lau from comment #3) > > 4) Ensure they are now sorted in teh following fashion: > > 'Hold_Filled' => 1, > > 'Hold_Reminder' => 2, > > 'Recall_Requested' => 3, > > 'Recall_Waiting' => 4, > > 'Ill_ready' => 5, > > 'Ill_unavailable' => 6, > > 'Ill_update' => 7, > > 'Item_Checkout' => 8, > > 'Auto_Renewals' => 9, > > 'Advance_Notice' => 10, > > 'Item_Due' => 11, > > 'Item_Check_in' => 12 > > This creates maintenance. For each new notice we need to edit this list. > While just sorting by name is simple and effective here imo. We will sort any new ones to the bottom if not specified here: sort { ( $messaging_order{ $a->{message_name} } // 999 ) <=> ( $messaging_order{ $b->{message_name} } // 999 ) } It is 'maintenance' to force specifying an order here, but I think it is worth it for having a sensical order -- 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/
