Cash reports "user payments" should use workstation org, not staff user home org

Bug #1991544 reported by Jane Sandberg
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

open-ils.circ.money.org_unit.user_payments currently filters based on the home org of the staff user who took the payment. It should instead filter by the staff member's workstation's org unit.

Breaking this bug off from Terran's comment (https://bugs.launchpad.net/evergreen/+bug/1859701/comments/23):

"[U]ser payments were tied to the home library of the staff user, so my initial testing of forgive/work/goods didn't show up as I expected. I feel very strongly that they should be tied to the workstation's branch, particularly because library staff members may work at more than one branch, or may have a home library that is unrelated to the branch where they work. However, that's an issue that is separate from this work. See also: https://bugs.launchpad.net/evergreen/+bug/1354482"

Tags: admin-pages
Changed in evergreen:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Lindsay Stratton (lstratton) wrote :

I'm copying my comment from bug #1859701 -

Lindsay Stratton (lstratton) wrote on 2020-02-18: #4
I don't understand why a) non-monetary payments are handled via a completely separate table, and b) why non-monetary payments are associated with the staff user account rather than the "payment" accepting workstation.

That user payments are recorded by the staff username is a HUGE problem when staff work at multiple libraries. User payments appear on the cash report of the library that is the "home" or first registered library of the staff person REGARDLESS of what library actually processed the transaction.

This is a common and frustrating problem for our libraries in Westchester.

Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Confirmed this continues to be an issue in the new angular cash reports interface in 3.11

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.