Created attachment 1681033 [details] compare the Name filter across Search and Pod pages Description of problem: The Chip Group "Name" will always display ahead of the other Chip Group, but Search page orders normally. Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-04-21-103613 How reproducible: Always Steps to Reproduce: 1. User go to resource list page, such as Pods or Deployment. 2. Add some filters by Status or Labels, then add a Name filter 3. (Compare to the correct page) Go to Search page, repeat the step2 and check Actual results: 2. Name filter is always display ahead of the others, which is incorrect. (refer to the screenshot) Expected results: 2. The last added filter should append in the end of Chip Groups filters. Additional info: There is another inconsistent issue for "Name": Search page does not have Close button for Chip Group "Name" but all the other resources pages have Close button for "Name"
Reassigning to Bipul as he worked on the original implementations.
If you look into the search page. The "Resource" chip will always come first even if you type "Name" first. We can remove the close button from the "Name" chip in the list page to make it more aligned with the Search Page. But AFAIK natural selection order preservation is not present in the "Search" page as well.
Sorry I was looking at a 4.4 Cluster. Apparently it maintains order in 4.5.
moving to upcoming sprint: the bugfix is in code review. will be merged in for upcoming sprint
Created attachment 1687991 [details] Verification screenshot
Search page and other pages are same now: 1) filter items ordered by user's selection. 2) Name removed the duplicated Close button on the group chip card. Refer to the verification screenshot. Verified on 4.5.0-0.nightly-2020-05-13-043728
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409