Support for Lost and Paid Status

Bug #1198475 reported by Jason Stephenson on 2013-07-06
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

A Lost & Paid Status should be applied when a patron has fully paid for an item.



Ben Shum (bshum) on 2013-07-25
Changed in evergreen:
assignee: nobody → Jason Stephenson (jstephenson)
status: New → In Progress
Jason Stephenson (jstephenson) wrote :

Branch is here: working/user/dyrcona/lp1198475_Lost_and_Paid_Status

Pull request will wait for some internal review. Others can feel free to look at it in the mean time.

Changed in evergreen:
milestone: none →
Changed in evergreen:
assignee: Jason Stephenson (jstephenson) → nobody
status: In Progress → Confirmed
Kathy Lussier (klussier) wrote :

I tested this code with the setting enabled at different levels in the org tree. Paying off a lost transaction bill in one transaction and in multiple transactions successfully changed the status to Lost and Paid.

I added a release notes entry and signed off on Jason's code at;a=shortlog;h=refs/heads/user/kmlussier/lp1198475_Lost_and_Paid_Status_signoff.

Thank you Jason!

tags: added: pullrequest
Kathy Lussier (klussier) on 2014-06-06
tags: added: signedoff
Rogan Hamby (rogan-hamby) wrote :

I tested as well and it looks good to me. Many thanks, this has aggravated me and everyone who works circ routinely.


Changed in evergreen:
status: Confirmed → Fix Committed
milestone: → 2.7.0-alpha1
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