Bug 1312081 - [RFE] Add the ability to specify a rolling date range in a content view filter
Summary: [RFE] Add the ability to specify a rolling date range in a content view filter
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: Unspecified
Hardware: Unspecified
OS: Linux
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-25 17:00 UTC by Chuck Mattern
Modified: 2018-09-04 19:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 19:11:38 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Chuck Mattern 2016-02-25 17:00:30 UTC
Description of problem: As a user of Satellite 6, our patching policy is a rolling policy of 'stay within 30 days of currently released errata. As such, I would like the ability to set a relative range. When creating a content view filter dates are static. It would be very useful to allow a relative range such as "today minus 30 days" so that content could automatically evolve at a customer defined pace which allows me to 'fast-forward' the content view when publishing.

Version-Release number of selected component (if applicable): >=6.1


How reproducible: Consistently

Comment 1 Bryan Kearney 2016-07-26 19:03:23 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 2 Bryan Kearney 2018-09-04 18:59:39 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 3 Bryan Kearney 2018-09-04 19:11:38 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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