Overview:

Sorting on the item table is not working.
Steps to Reproduce:

1. Log into some FOLIO environment as User with inventory permissions

2. Open the inventory app and search for a title, containing a holding record with more then one item on a holding; example The ... annual Iowa year book of agriculture /issued by the Iowa Department of Agriculture. HRID: in1354864

3. Expand the holdings accordion.

4. Click on any of the table headers; Enumeration would be a better example

Expected Results:

 - The column header should have a chevron happened to ti and the column contents be sorted DESC.
Actual Results:

• The chevron is appended but the columns remain in the original order.
  Additional Information:
  URL: https://bugfest-orchid.int.aws.folio.org/inventory/view/4a02f5c1-85a6-4550-9d88-de61458f497d?filters=mode.363895f3-3c52-421e-8f78-9ec105ec15f1%2Cmode.fa114271-7ec8-4a83-8723-a9fc809b3d48&sort=title

When the column headers are clicked the only call made is for the chevron, there are no additional API calls made. There are not errors in the JS console and there seems to be no click event registered. All logging was enabled in the JS console at the time of testing, tests where original performed on or production env at Cornell Orchid-sp-4 and confirmed in bugfest. 

Screen shots and logs are from bugfest.

Interested parties:

ORCHID Critical service patch details

1. Describe issue impact on business: Fixes a regression that was introduced in an earlier Orchid CSP (by a different dev team) where sorting in the item record table under the holdings, in the instance detail record, stopped working. When there are large numbers of item records associated with a holdings, the lack of sorting makes it difficult for production libraries to identify specific item records that need attention.

2. What institutions are affected? (field “Affected Institutions” in Jira to be populated) - All that have large numbers of item records associated with specific items

3. What is the workaround if exists? No user workaround, other than paging through many, many pages of item records, which is very time-consuming

4. What areas will be impacted by fix (i.e. what areas need to be retested) Inventory Smoke and Critical Path automated tests

5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high).

   • Work is complete and the level of effort was minimal, though disruptive to have to attend to this unexpected regression. 

   • Use sorted records array instead of initial items prop

   • Risk to backport: Minimal

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO. Automated and manual test cases already exist and level of effort is 1/2 hour

7. What is the roll back plan in case the fix does not work? Revert to previous version