I want to send an email 3 days before the due date, so I set the JQL condition like:
due date = startOfDay(+1d)
The message I received from the Validate query was as follows.
Error in the JQL Query: 'date' is a reserved JQL word. You must surround it in quotation marks to use it in a query. (line 1, character 31)
What did I do wrong?
Hi Min,
For date values in the future you don't need the +. So duedate = startOfDay(3d) would cover it. Alternatively you could use duedate = startOfDay("+3d"). For date values in the past you would use the - symbol. startOfDay("-3d") would be the start of day, three days ago).
Looking at your automation there are a few other points to keep in mind:
Hope this helps!
Els
Hi. @Els Bassant
As you said, what I have made is based on when the issue is transitioned.
What I want is to set the due date to 2 weeks later when the issue is converted, and automatically send a mail 3 days before the due date.
Could you tell me what automation I need to add to the current version to achieve this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What I want is to set the due date to 2 weeks later when the issue is converted, and automatically send a mail 3 days before the due date.
That makes sense.
In that case you will need two automations:
The trigger that you need for this is "scheduled" and then configure it to check for issues that are due in three days. My example is scheduled for every day at 8am:
The JQL I used in my example is Resolution = unresolved AND due >= startOfDay(3) AND due <= endOfDay(3).
Then you can configure the email that is sent. In my example I'm sending a reminder to the assignee that their issue is due in three days, but depending on your use case it may be something else. You can use smart values to insert information from the issue in the email.
Note: I've put the conditions after the branch rule. That way you could potentially set up multiple different reminders in the same automation. For example one for issue type A, and a different one for issue type B. But you can also make the rule specific to only one use case, whichever you prefer.
Depending in your volume of tickets this may end up sending a lot of emails, so make sure to test thoroughly!
This ended up as a very long post, but I hope it helps!
Els
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @min
You don't need the "+" within the parameters for the startOfDay function. The function will assume you mean "+" unless you explicitly insert "-".
Additionally, if you want the message sent when the due date is 3 days in the future you need to use "3" rather than "1" in the startOfDay parameter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That will not meet the requirement because it will say the issue matches if it is more than 3 days before the due date. The post is asking to match issues that are exactly 3 days before their due date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.