copy location order context fails

[Jim Frey]

Working as administrator, the list of copy locations does not change when another library/org_unit is selected. Also, the editor only displays a list of locations for the site associated with the workstation login. I was able to add copy locations to the table for two libraries before this error: on the third try, I may have hit 'Apply changes' before the entire list was loaded/displayed. The progress bar froze at 92%. Only a partial list of copy locations for the library was added to the table. I deleted these assuming it would resolve the problem, but it did not. (Version 2.2.0)

[Jim Frey (jfrey)]

Attempted to use the stat-client's copy_location_order editor after all records were removed from asset.copy_location_order. The editor displayed a library shortname and a list of about 60 copy locations. I 'applied' the changes without changing the order of the list. The editor saved the records to copy_location_order. I used PgAdmin to compare the list in copy_location_order with the records in asset.copy_location and found that the data in copy_location_order was incorrect. It had taken copy locations assigned to the target library (CAN/805) and applied them to another library (ONT/789). See the attached screen shot.

[Jim Frey (jfrey)]

Also, ONT was the first target library in my earlier go-round with the editor. I did not select it during this session.

[Kathy Lussier (klussier)]

I have also seen this in 2.2.1 and in master.

From the copy location order interface, I change the order for the copy locations for BR1. I apply changes. This new order is saved correctly in asset.copy_location_order.

If I change the context org unit to SYS1, BR2, CONS, etc., I continue to see the copy location order for BR1.

If I log out of the staff client an login again with my workstation location set to BR2, I will see the correct order listed for BR2. However, if I then change the context org unit to BR1, it continues to display the order that is set for BR2.

[Terran McCanna (tmccanna)]

Marking this one Won't Fix, but pointing to issues with the current Angular version here:

https://bugs.launchpad.net/evergreen/+bug/1861526