Automation Rule for more than one due date per month

Hi @Gor Greyan ,

That is exactly what we did:

Due Date Issue 1: {{now.lastOfTheMonth(1).jiraDate}}

Due Date Issue 2: {{now.plusMonths(1).ofTheMonth(2,1).jiraDate}}

And it's not working. Nothing happend at the 01.09.

Hi @Troth_ Stefanie

Your scheduled trigger is currently configured to run on Tuesday, but your conditions are checking whether {{now}} is the second or last Monday.
When the rule executes on Tuesday, those comparisons will always be false. I would simplify the rule and schedule it to run daily.

Then use the two conditions --  Second Monday: {{now.jiraDate}} equals {{now.ofTheMonth(2,1).jiraDate}}
Last Monday -- {{now.jiraDate}} equals {{now.lastOfTheMonth(1).jiraDate}}

For the work item created on Monday, you can set its Due date directly to {{now.jiraDate}} If the requirement is that the next work item is created one day after that Monday, add another condition for Tuesday, rather than using plusDays(1) only for the Due date.
I would also add a Log action temporarily to output {{now.jiraDate}}, {{now.ofTheMonth(2,1).jiraDate}}, and {{now.lastOfTheMonth(1).jiraDate}}. This will make it very easy to verify what Jira is calculating.

Regards,
Gor

Hi @Gor Greyan Thanks for your reply. The work items have to be created on TUE, one day after the due dates (the 2nd and the last monday of a month) of the previous work item. 

When you say, the conditions refer to "Monday", should I change them to:

Second Monday: {{now.jiraDate}} equals {{now.ofTheMonth(2,2).jiraDate}}
Last Monday: {{now.jiraDate}} equals {{now.lastOfTheMonth(2).jiraDate}}

?

Hi @Troth_ Stefanie

Thanks for the clarification.
In that case, keeping the rule scheduled for Tuesday is correct. You should not change (2,1) to (2,2). Instead, check whether today is one day after the required Monday.
Tuesday after the second Monday is the following -->
{{now.jiraDate}} equals {{now.ofTheMonth(2,1).plusDays(1).jiraDate}}
Tuesday after the last Monday --> {{now.jiraDate}} equals {{now.lastOfTheMonth(1).plusDays(1).jiraDate}}

Then create the work item under each condition.

Regards,
Gor

Hi @Gor Greyan Thanks for your suggestion, but this is exactly the setting, we tried at the beginning without success. I guess ".plusDays(1)" is the problem.

We changed the setting now as I said before. If the work item is still not generated, we'll simply  clone them in the future. It's much more secure, as having an automation, which doesn't work.

Hi @Troth_ Stefanie

On Tuesday, 1 September, {{now.lastOfTheMonth(1)}} calculates the last Monday of September, while the Monday you actually want to check is 31 August.

A safer approach I think is to evaluate yesterday and check whether yesterday was the second or last Monday of its own month.

Tuesday after second Monday {{now.minusDays(1).jiraDate}} equals {{now.minusDays(1).ofTheMonth(2,1).jiraDate}}

Tuesday after last Monday {{now.minusDays(1).jiraDate}} equals {{now.minusDays(1).lastOfTheMonth(1).jiraDate}}

This also handles cases where the last Monday is on the final day of the previous month, such as 31 August → 1 September.

So your Tuesday schedule can stay as it is; I would just change the conditions to check yesterday rather than adding one day to a Monday calculated from now.

Regards,

Gor

We want to keep one rule per task. Descriptions etc change from time to time and we don't want to adjust more than one rule every time.

We set the trigger for the relevant day, but the conditions if/else/when.... don't generate any issues at the expected days.

Perhaps you could copy-paste your rule here so that it seems clearer what you try to do. The problem may also be elsewere. If an otherwise correct rule does not create an issue, that might also be because in the user rights, the role 'atlassian-addons-project-access' has no right to create issues. You might want to check the user rights scheme associated with the space.

Rules with one due date per months are working fine, so the rights are not the problem. 

That's the rule

Due Date Issue 1: {{now.lastOfTheMonth(1).jiraDate}}

Due Date Issue 2: {{now.plusMonths(1).ofTheMonth(2,1).jiraDate}}

I was rather thinking of a JQL condition directly in the trigger itself, without all the different if/then/else conditions. You can add that at the bottom of the trigger's properties.

I've found it. And how should this JQL condition looks like? I have no idea.... Can you give me the condition, so that we can try that instead of if/then/else?

I would have to look it up myself so I have to bail out on that, sorry.

That's fine. Thanks for your help.

You could also trigger the rule and use if / then / else to

1. ask with smart values or JQL whether this is a Monday, comparing the value of {{now.dayOfWeekName}} with the local name string for Monday (perhaps "MON"?), and whether the current day of month is between 1 to 7 or between 15 to 21.
2. And in the "else" part, you can do the same, now checking for this being a Tuesday and having a date of month between 16 and 22.

Yes, it's gone. We should use the automation rules instead. There is a trigger type "scheduled" but we haven't been able to find out, how they work. To be honest, they are quite complicated, especially with more than one due date per month.

@Troth_ Stefanie the functionality stays the same as the previous one. You have two sections:

• Determine WHEN the trigger will start
• Determine WHEN the trigger will occur (once a day, once a way, twice a month),etc.

We tried, but it is not working. 

Requirement: Jira issues must be created automatically. For example, an issue must be due on the second and last Monday of each month. The next issue must be created one day after the previous issue’s due date, regardless of the previous issue’s status.

From August to September we had a switch to another month. Whatever we tried, nothing happend.