https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41416
--- Comment #5 from Nick Clemens (kidclamp) <[email protected]> --- (In reply to Jan Kissig from comment #4) > I wanted to take a look at this one and followed the test plan. In my case > the changing of the priority did not work as expected neither before nor > after applying the patch so it should not be related to this patch. > > I used a slightly modified version of your randhold.pl > (https://gitlab.com/-/snippets/4923530) in order to have only readable > patron names and only used a short amount of holds: > > - perl randhold.pl -b 262 -n 5 > - the behavior is a bit obscure but take f.e. one patron and move its prio > step by step down and check if the prio changes as expected and then move it > up. I alway get stuck with one patron that would not get a higher prio. > > Maybe someone can confirm this. > > Again, this behavior does also occur before applying the patch and therefore > should not interfere with it. Can you confirm the 'stuck' holds aren't marked as 'lowestPriority'? These will always get sorted to the bottom before and after -- 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/
