Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Current Content rpm / errata filter display does not indicate the number of packages/errata affected by the filter (include or exclude). Providing this feedback and a listing would reduce user effort and cycles should the filter scope be too narrow or too broad.
Version-Release number of selected component (if applicable): 6.2.x
How reproducible: always
Steps to Reproduce:
1. New Feature
2.
3.
Actual results:
Expected results:
When a user creates a new filter, on the filter specification page, the interface should provide for a facility to allow the user to preview the filter results before applying/saving the filter. Providing the list of included or excluded packages/errata for verification.
Additional info:
Closing this bugzilla as a duplicate of bug 1148490. If there are any concerns, please do let us know.
*** This bug has been marked as a duplicate of bug 1148490 ***