Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,370,031
Community Members
 
Community Events
168
Community Groups

Automation based on day of week

Our business needs to push newly created support cases into sprints, so that they can be incorporated into overall sprint views of the work to be done. Our sprints run from Monday to Sunday.

Setting up the base automation is straight forward, but for cases that are submitted on Friday, Saturday and Sunday, the cases need to be added to the next sprint, not the current sprint. I have implemented a condition as follows:

{{issue.created.withDayOfWeekShortName}} = FRI OR {{issue.created.withDayOfWeekName}} = SATURDAY OR {{issue.created.withDayOfWeek}} = 1

Screenshot 2021-02-24 at 11.08.27.png

I have used the three different DayOfWeek variants in trying to test them. None of them seem to work. I have also tested the texts with "FRI" and "Saturday", but they did not work either. 

I have consulted the following pages for guidance in the documentation:
https://support.atlassian.com/jira-software-cloud/docs/use-smart-values-to-manipulate-and-format-dates/ 

https://support.atlassian.com/jira-software-cloud/docs/smart-values-date-and-time-functions/ 

Any help would be greatly appreciated. 

1 answer

1 accepted

3 votes
Answer accepted

Hi @Ross Musselman, you cannot do comparisons in JQL like that as JQL only works on issue fields, not extracts of fields.

Also, the .withDayOfWeek functions are used for setting that portion of the date to a new value. They do not return the portion of the date.

What you need is the Advanced compare condition where you can use the date formatting function to extract the date field you need and compare it with a regular expression.

The following example will match issues created on either Friday, Saturday or Sunday respectively:

Screenshot 2021-02-24 at 09.31.42.png

Thank you, @Gareth Cantrell . That fix worked perfectly!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events