Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/User_Guide/index.html

Section Number and Name: table 18.2 vs. section 15.3.3

Describe the issue: The docs for granular search describe how the caret (^) sign works in granular matching for permissions. For scoped search however, the caret is not documented even though it is auto-completed and it's meaning is different from granular search. 

Suggestions for improvement: 
Please add an example in section 15.3.3 to demonstrate the use of the caret in scoped search.

Something like

    facts.architecture ^ (x86_64,i386) 

would fit nicely with the other examples. 

Additional information: 

The caret in scoped_search means 'in', like in SQL, not 'starts with' like in regular expressions. It is confusing to not have this documented.

See: https://github.com/wvanbergen/scoped_search/blob/master/lib/scoped_search/query_language/tokenizer.rb#L10

I can fix this. I've already been working in this section.