Hey,
I want to send a single email through automation. The scenario is like, I have multiple issues, and they are overdue at a same time. for this instead of getting single email for each issue, I want to get a single email to the assignee which comprise of all issues which are overdue. I want to try in cloud and data center version so please let me know it both the cases if it is feasible or not
Please see this article from Atlassian describing an automation rule to do that. For your case, update the JQL used in the Lookup Issues action to meet your needs:
Kind regards,
Bill
Wow Thank you @Bill Sheboy .. didnt know that this was possible..
@mohit jangid , check this.. i would accept this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Bill Sheboy, It's working perfectly and one thing more i would like know is "can we do the same automation in Jira Data Center Version"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, you should be able to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am glad to learn that is working, and...
Data Center automation rules do not support the Advanced Branch over smart values yet and so this technique is not possible: https://jira.atlassian.com/browse/JIRAAUTOSERVER-749
A more complicated approach for Data Center would be to use two rules: the scheduled trigger one and a recursive rule, triggered on Incoming Webhook. That would be passed the list of assignees and it would process one user, remove it from the list, and if there are any remaining, call itself again using the Send Webhook action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mohit,
Set up a filter for the issues you want with assignee = currentUser() in the filter. Then you you can do a Filter Subscription and send it when you like. But be sure to click off the box to send the email even if the filter is empty.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why are you trying to make it complicated? The Subscription with that filter will give you an email to each Assignee with the issues for that Assignee.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hy @John Funk In filter subscription in there any way to customize the email content in jira data center version?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It will send the fields that you identify in the filter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Instead of automation, use the filter subscription for this use case.
Refer to https://support.atlassian.com/jira-software-cloud/docs/manage-filters/#Subscribe-to-a-filter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thankyou, I want to understand it thoroughly like how can i restrict individual assignee to get the mail only when there is no overdue issue. and is there any way we can do this via automation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Filter -> assignee = currentUser() and duedate > now()
If you use the filter subscription approach as suggested in my answer, users subscribed will get a daily email (or as per your schedule set) with the list of issues which are overdue and assigned to them.
If there are no issues matching the filter that day for that assignee, no email will be triggered.
This is a recommended approach to this use case instead of using automation. May i know why you would like to handle this in automation instead?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The subscription part is pretty much clear to me but I want to create an automation for this to understand the other side as well and then i can conclude which one i go with.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@mohit jangid , I think you misunderstood the branching statement as 'For each assignee'. It would actually interpret as 'For each issues, assignee variable = smart value'.
I do not see a way how you can achieve a single email for each assignee on all their due issues through automation.
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.