Bug 39185: Don't add select option if priority is 0

To test:
1. Place several holds on a biblio record
2. Check in items from that record and confirm some (but not all) of the
    holds
3. View the current holds on that record
4. Click on the drop-down to change the priority of a hold
--> Note that the drop-down contains one or more "0" options - one for
    each in-transit or waiting hold
5. Apply patch and refresh the page
6. Click on the drop-down again
--> The drop-down now contains the correct options
7. Use the drop-down and the "Update holds" button to change hold
    hold priorities a few times
--> Confirm that the priority is updated correctly

Signed-off-by: Phil Ringnalda <phil@chetcolibrary.org>
Signed-off-by: Baptiste Wojtkowski <baptiste.wojtkowski@biblibre.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
This commit is contained in:
Emily Lamancusa 2025-02-21 14:51:22 -05:00 committed by Katrin Fischer
parent 56fd9a7c7d
commit 6dee4899d6
No known key found for this signature in database
GPG Key ID: 0EF6E2C03357A834
1 changed files with 1 additions and 1 deletions

View File

@ -61,7 +61,7 @@
[% FOREACH priority IN all_priorities %]
[% IF priority == this_priority %]
<option value="[% priority | html %]" selected="selected">[% priority | html %]</option>
[% ELSE %]
[% ELSIF priority > 0 %]
<option value="[% priority | html %]">[% priority | html %]</option>
[% END %]
[% END %]