Low Issue Summary
While adding Schedule Trigger from the Triggers tab from the plan configuration: The radio button for selecting the week of every month under the Days per month option(in Schedule editor) is greyed out.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Goto plan configuration of any one of the plans from Actions > Configure plan option.
- Goto Triggers tab.
- Click on Add Trigger > Select Scheduled.
- Click edit icon under Schedule option.
- Select Days per month
- The radio button for selecting the week of every month is disabled.
Expected Results
The radio button for selecting the week of every month should be in the Enabled state and be available for the screenreader to select the week to schedule the trigger.
Actual Results
The radio button for selecting the week of every month is disabled.
Please find attached screenshots for reference.
Workaround
Use a cron expression provided on the last tab of the Schedule editor.
For example, the following Quartz Cron entry will run the trigger every first Monday of the month at 10 a.m.:
0 0 10 ? * MON#1 *
And this will run the trigger at 1:30 p.m. on the last Wednesday of the month; useful if the month has 5 weeks.
0 30 13 ? * WEDL *
More examples:
[BAM-22067] Schedule Trigger: Radio button for selecting the week of every month under Days per month option(in *Schedule editor*) is greyed out
| Fix Version/s | New: 9.2.3 [ 104892 ] |
| Affects Version/s | New: 9.2.1 [ 104324 ] |
| Description |
Original:
h3. Issue Summary
While adding *Schedule Trigger* from the Triggers tab from the plan configuration: The radio button for selecting the week of every month under the Days per month option(in *Schedule editor*) is greyed out. This is reproducible on Data Center: (yes) h3. Steps to Reproduce # Goto plan configuration of any one of the plans from Actions > Configure plan option. # Goto *Triggers* tab. # Click on *Add Trigger* > Select *Scheduled*. # Click *edit icon* under *Schedule* option. # Select *Days per month* # The radio button for selecting the week of every month is disabled. h3. Expected Results The radio button for selecting the week of every month should be in the *Enabled* state and be available for the screenreader to select the week to schedule the trigger. h3. Actual Results The radio button for selecting the week of every month is disabled. Please find attached screenshots for reference. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
While adding *Schedule Trigger* from the Triggers tab from the plan configuration: The radio button for selecting the week of every month under the Days per month option(in {*}Schedule editor{*}) is greyed out. This is reproducible on Data Center: (yes) h3. Steps to Reproduce # Goto plan configuration of any one of the plans from Actions > Configure plan option. # Goto *Triggers* tab. # Click on *Add Trigger* > Select {*}Scheduled{*}. # Click *edit icon* under *Schedule* option. # Select *Days per month* # The radio button for selecting the week of every month is disabled. h3. Expected Results The radio button for selecting the week of every month should be in the *Enabled* state and be available for the screenreader to select the week to schedule the trigger. h3. Actual Results The radio button for selecting the week of every month is disabled. Please find attached screenshots for reference. h3. Workaround Use a cron expression provided on the last tab of the Schedule editor. For example, the following Quartz Cron entry will run the trigger every first Monday of the month at 10 a.m.: {noformat} 0 0 10 ? * MON#1 * {noformat} And this will run the trigger at 1:30 p.m. on the _last_ Wednesday of the month; useful if the month has 5 weeks. {noformat} 0 30 13 ? * WEDL * {noformat} More examples: * [Quartz Cron Trigger Tutorial|http://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html#crontrigger-tutorial] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| UIS | Original: 1 | New: 0 |
| Support reference count | Original: 1 | New: 2 |
| UIS | New: 1 |
| Affects Version/s | New: 9.1.1 [ 104302 ] |
| Fix Version/s | New: 9.0.3 [ 104339 ] | |
| Fix Version/s | New: 9.1.2 [ 104330 ] | |
| Fix Version/s | New: 9.3.0 [ 104112 ] |
This issue is still in release 9.2.1 only resolved in 9.1.2 and 9.3.0. My team can not upgrade to 9.3.0 yet since there are other dependent add-ons that are not yet compatible. If 9.2.1 is LTS, there should be a fix in 9.2.x