[FOLIO-1416] Sort order for Locations is not consistent between Apps Created: 16/Aug/18  Updated: 12/Nov/18  Resolved: 28/Aug/18

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P2
Reporter: Ann-Marie Breaux (Inactive) Assignee: Aditya matukumalli
Resolution: Done Votes: 0
Labels: sprint45
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: File LocationSortOrder.mp4    
Sprint:

 Description   

Overview: Optional high-level description of problem

Steps to Reproduce:

  1. Log into FOLIO-snapshot-stable as diku_admin
  2. Go to Settings/Organizations/Locations
  3. Create a mix of locations, some starting with Uppercase letters, some starting with Lowercase letters
  4. Review the sort order that the Locations display in
  5. Then go to Inventory, find an instance, and begin to create a new holdings or new item
  6. Click the Permanent or Temporary Location field and review the sort order that the Locations display in

Expected Results: The Location sort order should be consistent between Settings and Holdings/Item, preferably with upper and lower-case values interfiled. CB: confirmed, let's use the same sort order for Settings as we are using within the menu in Inventory (i.e. case insensitive).

Actual Results: In Settings, the Location sort order alphabetizes the upper-case values first, then restarts the alphabet with the lower-case. In Holdings/Items, the Location sort order is one alphabetical list, regardless of case.

Additional Information: See attached video



 Comments   
Comment by Cate Boerema (Inactive) [ 21/Aug/18 ]

Nice catch, Ann-Marie. Bumping to P2.

Comment by Aditya matukumalli [ 24/Aug/18 ]

Ann-Marie Breaux Just added in the fix for this. Looks like this issue is present across Staffslips and service points as well. Sort order in all of those should be fixed now.

Comment by Ann-Marie Breaux (Inactive) [ 28/Aug/18 ]

Looks good - thanks, Aditya matukumalli!

Generated at Thu Feb 08 23:13:11 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.