The case used in the status column of the line item display is misleading

Bug #1774070 reported by Jane Sandberg
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Low
Unassigned

Bug Description

If a line item is order-ready, it is written capitalized as Order-Ready within the Status column. However, if you try to search for line items with State=Order-Ready, you don't get any results. You have to use the lower case version, order-ready.

This is mainly a problem because the acquisitions search is case-sensitive. However, it seems weird to call this status one thing in the Line Item interface, but expect users to search for it in a different way.

This is also the case for Selector-Ready/selector-ready

I've attached a screenshot

Tags: acq
Revision history for this message
Jane Sandberg (sandbergja) wrote :
Revision history for this message
Jane Sandberg (sandbergja) wrote :
Changed in evergreen:
status: New → Confirmed
Revision history for this message
Tiffany Little (tslittle) wrote :

It seems best that the search would just not be case-sensitive. Since the term is the same, that seems like it would solve the issue fairly handily.

Confirmed on 3.2-beta.

Revision history for this message
Galen Charlton (gmc) wrote :

This is addressed in the Angular rewrite of the search interface (bug 1850547), which uses auto-completing dropdowns to allow the user to select the status they want to search for or filter the grid results on.

Andrea Neiman (aneiman)
Changed in evergreen:
status: Confirmed → Won't Fix
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.