Weekly sub-tasks scheduled each month

Mattia Battan

hello everyone,
I am trying to create an automation that creates every 1st of the month, sub-tasks of all Wednesdays (for example) of the month where the field ""recurrent re-opening[Dropdown]" = Weekly" is selected.
This creation must depend on a variable date field called "Final Solution Date." (If for example a Monday is entered, the next month must create the sub.tasks of all the Mondays of that month etc.).

Now my problem, by putting in the "final solution date" of my main task on April 12 (which is a Friday for example), I would like it to create on the first day of the next month the sub-tasks of the remaining Fridays, and thus: the 12th, the 19th and the 26th (total 3 sub-tasks).
If I then change the date and put May 1, it should create 5 of them (being 5 Wednesdays in that month).

How can this be done?

Thanks

Kalyan Sattaluri_iinm1n

Hello @Mattia Battan 

I am not understanding the trigger of your requirement..

I gather that based on  what "Final Solution date" is entered, you want to create sub-tasks, but What if this field  is changed again same month? Wont you end up with multiple sub-tasks everytime? So your requirement is confusing.

But assuming this field change is the trigger and it will be changed only once..

Probably many ways to do this, I guess I am proposing a brute force check.. Looking forward to other options as well...

My suggestion:

Below smart values gives you number of wednesdays in a month:

{{#=}}CEILING({{Final Solution date.firstOfTheMonth(3).diff(Final Solution date.lastOfTheMonth(3)).days}}/7 + 1){{/}}

Where, 

• "Final Solution date" is the field, change it / match it accordingly.
• firstOfTheMonth(3) gives the date of the first wednesday, 
• lastOfTheMonth(3) gives the last wednesday,
• We do a difference, divide by 7 and add +1 to include all occurrences.
• and CEILING will round up to the nearest integer incase the date time stamp diff does not give a whole number.

 

Again, assuming your trigger is field change to "Final Solution date" field. You can do a refetch action after the trigger and then do the If/Else condition check and create sub-tasks accordingly.

Now, We know a month can only have either 4 or 5 wednesdays, So before you start creating sub-tasks, put an if/else condition -> smart value condition and check if above smart value equals 4, if so create 4 sub-tasks, else create 5.

 

Like below screenshot: (Its a DC screenshot but cloud has similar logic)

To test this.. what ever your trigger,  use your field, Final Solution date and below  smart value for checks:

{{#=}}CEILING({{issue.Final Solution date.firstOfTheMonth(3).diff(issue.Final Solution date.lastOfTheMonth(3)).days}}/7 + 1){{/}}

But dont create sub-tasks yet, just log like I did to make sure you are entering the correct If condition.. Only after verifying that, I suggest you create sub-tasks to avoid unnecessary issues.