We would like to set up an automation that reminds customers about their tickets in 'Waiting for Customer' status.
We would like to send a message when the is in 'Waiting for Customer' status for 1, 2 and 3 weeks.
So far, I have made 3 different automations with trigger Scheduled and added a JQL
However, the automation adds all 3 comments right away, not after 1, 2, 3 days as I would like to.
Please note that I have added days instead of weeks for now because it's still a test automation.
Thank you for your help!
Set the JQL for the scheduled triggers as follows
Status = "Waiting for customer" AND (updated <-1d OR updated = -2d)
Status = "Waiting for customer" AND (updated <-2d OR updated = -3d)
Status = "Waiting for customer" AND updated <-3d
Hi Marc,
I have set the triggers like this and it's not working somehow.
I have set the ticket to WFC on 17th June and no comment was added since :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Use these JQL clauses in the search, what are the outcomes per JQL?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Marc - Devoteam ,
It worked after I have added a comment, however, the timing is not correct. It added comments at 00:30 while the automation run is set to 12:30.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is the timing in your personal settings and what is the system time set to?
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.
I have this in my automation and it works as expected.
The trick here is I check the box "Only include issues that have changed since the last time this rule executed".
You can find more info here: https://support.atlassian.com/automation/kb/Only-include-issues-that-have-changed-since-the-last-time-this-rule-executed/
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.
Hi @Marija Aleksejeva Can you try a custom field counter? Or validate the previous comment content before sending the email?
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.
Hi @Marija Aleksejeva I think the answer suggested by @Marc - Devoteam would work. As an alternate,
Whenever an email is sent by automation, add another action to increment a custom field value, validate this to see the email counts sent to the user. You can use the Smart value {{#=}}{{issue.<Customfield_name>|0}} + 1{{/}}
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.