Team
Pls help on below . Thanks
My condition & requirement , some tickets , we have waiting for support and that ticket needs to remind to our IT agent working on 3 different shift and timing ,
If waiting for support ticket, region mentioned as APJ, then it remind to IT agent, send mail xxxx, 6 am to 2 pm
If waiting for support ticket, region mentioned as EMEA then it remind to IT agent send mail xxx 2 pm to 10 pm
If waiting for support ticket, region mentioned as AMR then it remind to IT agent send mail xxx 10 pm to 6 pm
Hi, @Sampath
You can make it, by creating 3 rules for Jira Automation, with sheduled run.
Set it to run once a day, each of them - in period, acccording to your requirements.
Select required tickets, and send emails with list of tickets, and escalation text (if needed).
In Schedule trigger you can set time, when rule is triggered, with CRON scheduler.
In my example I used 0 0 12 ? * * - it means, that job will run every day, at 12 AM.
You can find more examples of CRON expressions in documentation:
https://support.atlassian.com/jira-software-cloud/docs/manage-filters/
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.
Ok, you can use such cron chedules, for your cases:
If waiting for support ticket, region mentioned as APJ, then it remind to IT agent, send mail xxxx, 6 am to 2 pm - 0 0 6 ? * *
If waiting for support ticket, region mentioned as EMEA then it remind to IT agent send mail xxx 2 pm to 10 pm - 0 0 14 ? * *
If waiting for support ticket, region mentioned as AMR then it remind to IT agent send mail xxx 10 pm to 6 pm - 0 0 22 ? * *
Your IT agents will receive lists with issues right at beginning of their work shifts.
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.
Query looks like normal, I slightly refactored it, but previous must work too.
project = XXX AND issuetype in (Incident, "Service Request", Sub-task) AND status = "Waiting for support" AND Assignee in (XXXXXXX) AND "Support Level" = "XXXX" AND updated < -1d AND Region = AMR
It selects issues in Region AMR
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.
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.
You must make 3 rules, each with different cron schedule (time to run), and different query
Queries will look like:
project = XXX AND issuetype in (Incident, "Service Request", Sub-task) AND status = "Waiting for support" AND Assignee in (XXXXXXX) AND "Support Level" = "XXXX" AND updated < -1d AND Region = AMR
project = XXX AND issuetype in (Incident, "Service Request", Sub-task) AND status = "Waiting for support" AND Assignee in (XXXXXXX) AND "Support Level" = "XXXX" AND updated < -1d AND Region = APJ
project = XXX AND issuetype in (Incident, "Service Request", Sub-task) AND status = "Waiting for support" AND Assignee in (XXXXXXX) AND "Support Level" = "XXXX" AND updated < -1d AND Region = EMEA
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.
Sorry, I'm out of ideas. Try to check, what action in rule selects all issues. According to screenshots I don't see reason for rule to act like this
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you run all of them simultaneously, they will execute and send emails for all 3 regions. I gave you 3 cron expressions, for 3 rules. Rules must be run in different times
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Evgenii
Yes i though that too but yesterday when i ran it , i receive all the region and today i am again checking EMEA done successful and turn off the rule , now i only enable AMR rule and mail not received let see it and update you . Thanks for your valuable time and support, will keep you posted thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online 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.