Mark Item Damaged from patron account doesn't refresh

[Terran McCanna]

In 3.6.1: Using the Mark Item Damaged action from the patron's Items Out screen does not refresh the window so staff cannot tell if the process worked or not until they manually refresh the screen.

(It works properly from Item Status.)

[Elaine Hardy (ehardy)]

Mark item damaged redisplays in item status detail view but not in list view.

[Michele Morgan (mmorgan)]

Master circa 3.7

On a stock test system, when marking an item damaged from the patron's Items out screen, the screen does refresh, and the item disappears from Items out, as it has been checked in as part of the Mark Damaged process, so I don't see a problem there.

If the library setting "Charge item price when marked damaged" is set to TRUE, however, the item disappears from the patron's Items out screen as above, but no evidence of the billing appears on the screen until the patron record is refreshed.

Marking Confirmed for the case where the library setting "Charge item price when marked damaged" is set to TRUE.

[Jennifer Pringle (jpringle-u)]

Confirming above issues still present in 3.9

- Item Status screen does not refresh when marking an item damaged
- Items Checked Out tab (in Patron Account) does refresh when marking an item damaged but Billing does not automatically refresh to show the money owed (when "Charge item price when marked damaged" is set to TRUE.)

[Britta Dorsey (bdorsey-isl)]

Seems to be working on the Demo server running 3.9.1:

1. Accessed patron 2023-001 account
2. Went to the Items Out tab and selected barcode 42424
3. Selected Actions and clicked on Mark Damaged
4. Confirmed I wanted to mark it damaged by clicking Submit
5. Item disappeared from Items Out.
Status showed 42424 as Damaged in the Item Status screen.

Note that Charge Item Price when marked damaged was NOT set. Ran a quick test to see if changing the library setting to TRUE changed anything - it did not. I was also able to select No Charge when confirming the status change.

[Susan Morrison (smorrison425)]

Confirmed behavior in comment #3 is still occurring in 3.12.