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:
When a CV is published, it would be very usefull to see what filter is applied to create is. This could be easily saved with the CV, and would make knowing what is actually /in/ the CV easier. 

2 examples:
1. Date filters: we make date filters on errata. If the filter is changed & saved after publishing the CV version, we can not pinpoint the date used anymore.

2. Package filters: If a package filter is applied, the cv is created and then removed, it's not easy to reproduce the filter. One could reproduce the content of the filter if the repositories it's applied to are known, but having the actual filter available would be a lot simpler.

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