- changed status to open
Can't seem to schedule a yearly or multi-monthly schedule via the cron syntax
When I use the cron syntax to schedule an issue more than a month out (i.e. yearly) or if I do anything to specify a month in the 5th column, the result is just the cron string I put in, it isn't interpreted by the Cron Expression Summary
For example, 0 0 0 1 * ? correctly makes "The 1st day of every month at 12:00 am"
By that logic, 0 0 0 1 3 ? should make the 1st day of March at 12:00 am, but it doesn't.
Unfortunately this not working prevents me from buying this add-on, as 90% of the stuff we need to schedule are multiples of months out.
Comments (4)
-
-
Hi,
Did you check if trigger is actually not fired and new issue is not created? Because even if there is no detailed summary for your cron expression, e.g. for "0 0 0 1 * ?" you get "The 1st day of every month at 12:00 am", but for " 0 0 0 1 3 ?" there will be only "0 0 0 1 3 ?", new issue should be created because that means cron expression was parsed successfully, without errors.
Can you try to add trigger for current date ("0 0 14 7 9 ?" - it should fire the trigger and create new issue today at 14 pm) and check if new issue is still not created?
-
- changed status to invalid
cron expression works nevertheless it is not "translated" from cron expression to meaningfull sentence (It's a QUARTZ behaviour)
-
So it seems this will work in 3.2.10, but we have to run 3.1.3 due to our Jira version, and this seems to not work in that. Ok, we'll just have to wait until we upgrade. Thanks.
- Log in to comment
Hi,
Thank you for your feedback and reporting this issue. We are currently analysing source of it, and let you know when we fix it.
Best regards.