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.
DescriptionJulio Entrena Perez
2022-03-17 10:08:54 UTC
1. Proposed title of this feature request
Ability to consult filters used to create versions of content views
3. What is the nature and description of the request?
Currently filters can be added, modified and removed from content views, but once a version of a content view has been published, no details about the filters that were in place in the content view when the version was published are available.
User can add/remove/modify the filters in the content view which removes any traceability about the filters used for each published version.
Customer requires being able to consult the filters that were in place at the time that a content view was published.
4. Why does the customer need this? (List the business requirements here)
Customers need to know what filters were used (what filters were in place) to publish a version of a content view, reasons vary from replicating the same filtering approach onto other content views to auditing and traceability.
5. How would the customer like to achieve this? (List the functional requirements here)
Customer requires being able to inspect the filters used to publish a content view version (that is, to inspect the filters that were in place when the content view version was published).
Ideally this would be implemented to display the filters used in a tabulated way, but adding the information to the Description of the version would work as well if that would lead to a faster implementation and delivery of the functionality being requested.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Customer can inspect the details of all filters that were in place when the content view version was published.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Most certainly, this functionality has been requested multiple times already by multiple customers:
https://bugzilla.redhat.com/show_bug.cgi?id=1300427https://bugzilla.redhat.com/show_bug.cgi?id=1313966https://bugzilla.redhat.com/show_bug.cgi?id=1786777https://bugzilla.redhat.com/show_bug.cgi?id=1793692https://bugzilla.redhat.com/show_bug.cgi?id=1922972
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
No, as soon as possible.
9. Is the sales team involved in this request and do they have any additional input?
No.
10. List any affected packages or components.
Unknown.
11. Would the customer be able to assist in testing this functionality if implemented?
Yes.