serials previous issuance copy location randomly fails to apply

Bug #1331127 reported by Bill Erickson on 2014-06-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Undecided
Unassigned
2.5
Undecided
Unassigned
2.6
Undecided
Unassigned

Bug Description

Evergreen 2.5+

The org unit setting "serial.prev_issuance_copy_location" ("Previous Issuance Copy Location") tells the system to change the copy location of the previous serial.unit (by issuance and stream) to the configured value when a new serial.item is received. However, there is an error in the code which determines what the previous serial.unit is resulting in serial.unit's which have already had their locations updated (per the the setting) being selected for update again instead of the most recent previous serial.unit.

The bug is the result of an improperly (and basically randomly) sorted list. This, of course, makes it impossible to reliably replicate or predict.

A patch is on its way.

Erica Rohlfs (erohlfs) on 2014-06-17
Changed in evergreen:
status: New → Confirmed
Bill Erickson (berick) wrote :
Changed in evergreen:
milestone: none → 2.next
assignee: Bill Erickson (erickson-esilibrary) → nobody
tags: added: pullrequest
Dan Wells (dbw2) wrote :

Looks good to me. Thanks, Bill!

Changed in evergreen:
milestone: 2.next → 2.7.0
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers