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:
Currently, CV verion with filtered contents only are exported and imported(as expected and without creating same filters in importing org), but the actual filters are not imported.

Can we add support to export and import CV version with filters? 

Version-Release number of selected component (if applicable):
Satellite 6.5.0 snap 3

How reproducible:


Steps to Reproduce:
1. Create CV with filter and publish.
2. Export CV version published above.
3. Attempt to import the CV version from another satellite/org.

Actual results:
The CV with filter version is exported and imported with filtered contents, but the actual filter is not exported/imported.

Expected results:
The CV with filter version is exported and imported with filtered contents along with filter.

Additional info:

Filters are not associated to a content view version, they are associated with the content view itself. The filters for a given version are not saved in the database. Thus, a content view has filters that could have changed since a version was published. If we were exporting content view definitions we could export the most recent filters but they may not be relevant to an exported version.