Description of problem: 1. Proposed title of this feature request. To introduce an option in Satellite to select recurring execution for a particular day of the Month. 2. What is the nature and description of the request? Modification of the code which allows to setup a recurring job that should run on a particular day of the month as described in the below example. For Example: If we want to set up a recurring execution of a particular job that should run on every second Tuesday of the month or third Wednesday of the month then there is no option available to do that and even complex cron does not work in Satellite. 3. Why does the customer need this? (List the business requirements here) Current Behaviour: As of now, there is no option to select a particular day of the month for scheduling the remote execution. If we try to use the complex cron that also does not work in Satellite GUI. 4. How would the customer like to achieve this? (List the functional requirements here) When going to schedule the remote execution job such as Satellite WebUI --> Monitor --> Jobs --> Run a Job --> Schedule --> Set up recurring execution here an option should be present to select the week like the first, second, third, or fourth week, and then an option to select Day i.e. Mon, Tues, etc. 5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. We should be able to Set up a recurring execution of a particular job that should run on every second Tuesday of the month or third Wednesday of the month and complex cron should work in Satellite GUI. 6. Is there already an existing RFE upstream or in Red Hat Bugzilla? No. 7. Does the customer have any specific timeline dependencies and which release would they like to target? As soon as possible. 8. Is the sales team involved in this request and do they have any additional input? No. 9. Would the customer be able to assist in testing this functionality if implemented? Yes.
*** This bug has been marked as a duplicate of bug 1967030 ***