http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12086

Jonathan Druart <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #27428|0                           |1
        is obsolete|                            |
  Attachment #28482|0                           |1
        is obsolete|                            |
  Attachment #28873|0                           |1
        is obsolete|                            |

--- Comment #22 from Jonathan Druart <[email protected]> ---
Created attachment 29162
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=29162&action=edit
Bug 12086 - Hold priorities incorrect, when waiting status was reversed

1) Test record has 1 single item, checked out to patron X
2) Place 3 holds for patrons A, B and C, all title level hold this time
   A, B, C, item branches and staff branch are the same.
3) Return item, confirm hold
4) Confirm item is now waiting for patron A
   Priorities are: A = Waiting, B = 1, C = 2
5) Open patron account of user B, checkout book
   Koha asks: Item X has been waiting for patron A... Revert
   waiting status
   Confirm.
6) Check priorities:
   Hold list shows: A = 1, C = 1
   Database says: A = 1, C = 3
7) Apply this patch
8) Repeat steps 1-6
9) Note the priorities are correct

Signed-off-by: Owen Leonard <[email protected]>

Test plan correctly predicts the error and the correction made by the
patch.

Signed-off-by: Jonathan Druart <[email protected]>
Amended patch: I squashed the 3 patches for a better readability.
A file was created in the first patch and deleted later.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
http://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/

Reply via email to