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.

Description of problem:
The content view filters in  6.7 does not have an option to include all the module streams with no errata. This means customers who want to get the bare minimum RHEL 8 and keep incrementing the errata on a periodic basis will have to run through some hoops. 
To simulate the module streams with no errata. They would need to do something like create an errata excludes filter which excludes all errata after issued start date of May 07, 2019. Alternatively include all errata before the end date of May 07, 2019.

The more ideal fix would be either
1) Create a new checkbox in the module stream filter page similar to what we have for package filters
OR
2) Assume that if the user checks "include all rpms with no errata" they want the same behaviour for module stream.

2 I think will be the more common case.

*** This bug has been marked as a duplicate of bug 1853280 ***