Bug 1213819 - Content -> Errata : type and severity search filters are case sensitive
Summary: Content -> Errata : type and severity search filters are case sensitive
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: sthirugn@redhat.com
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-21 11:20 UTC by Brad Buckingham
Modified: 2017-02-23 20:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-12 18:22:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10800 0 None None None 2016-04-22 15:39:53 UTC

Description Brad Buckingham 2015-04-21 11:20:45 UTC
Description of problem:

I have noticed that the values for the search filter are case sensitive. 

Eg:
 type = enhancement shows list of errata but type = Enhancement returns nothing.    
 severity = Critical shows list of errata but severity = critical returns nothing.

If the values are case sensitive then we should provide dropdown list for those options.

Version-Release number of selected component (if applicable):
ruby193-rubygem-katello-2.2.0.35-1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. go to Content -> Errata

in the search filter, 
2. enter "type = enhancement" : returns list of errata
3. enter "type = Enhancement" : returns nothing

4. enter "severity = Critical" : returns list of errata
5. enter "severity = critical" : returns nothing

Actual results:
Inconsistent results across options.

Expected results:
Consistent results across options.  If the values are to be case sensitive, then we should provide dropdown list for those options.

Additional info:
Issues raised by AshishH during April 15th test day

Comment 1 RHEL Program Management 2015-04-21 11:43:24 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Walden Raines 2015-06-12 16:00:06 UTC
Created redmine issue http://projects.theforeman.org/issues/10800 from this bug

Comment 4 Walden Raines 2015-06-12 18:22:39 UTC
After looking into this further I have realized this is how this search is supposed to work.  The "=" operator literally means equals and not similar to.  If you want to search for "Bugfix" instead of "bugfix" you need to use the "~" operator.  I think that this is the expected behavior and you'd only run into this issue by purposefully capitalizing the severity or type since we have autocomplete for this search.

Note also that if you search just for "Bugfix"(i.e. without using the = operator) you will get the correct results.

Comment 5 sthirugn@redhat.com 2015-06-16 20:43:03 UTC
Agreed with Comment 4. The following searches shows identical results.

type = bugfix
type ~ Bugfix


Note You need to log in before you can comment on or make changes to this bug.