Bug 1786777 - [RFE]: Content view versions should have an icon next to the version number to denote if the version was published with a content view filter
Summary: [RFE]: Content view versions should have an icon next to the version number t...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.6.0
Hardware: x86_64
OS: Linux
low
low with 1 vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-27 22:54 UTC by Taft Sanders
Modified: 2023-03-24 16:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-09 17:02:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Taft Sanders 2019-12-27 22:54:03 UTC
Description of problem:
There is no apparent way to determine if a previous version of a content view was published with a filter and what the settings on that filter were at the time.

Version-Release number of selected component (if applicable):
Satellite 6.6

How reproducible:
n/a

Steps to Reproduce:
1.
2.
3.

Actual results:
Content view versions are listed with package/errata counts. Nothing notes if the version included a content view filter and what the settings were for that filter

Expected results:
An icon or something to that effect should be present next to the version number on the WebUI. This would note that this version of the content view was published with a content view filter.
Furthermore, it would be nice to have this as a hyperlink to bring up a list of the content view filters included on this version.

Additional info:

Comment 3 Mike McCune 2021-07-09 17:02:24 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.


Note You need to log in before you can comment on or make changes to this bug.