Hi everyone!
I'm currently attempting to create a global automation for a service project and a business project that reminds assignees that they have subtasks/tasks due in 5 days from the due date.
I currently have the following JQL:
but am getting the attached error:
I'm fairly new to Jira so any assistance would be really appreciated :) Thank you!
Hi @LJ
Yes, and...to the other answers posted:
You do not show the details of your scheduled trigger, so I am assuming it does not have JQL as you are also using Lookup Issues.
But, your Send Email action references {{issue}} fields, which do not exist. When you use Lookup Issues, you instead reference the {{lookupIssues}} smart value, either as a set or individually by iterating over them. Please look here for more information about using Lookup Issues: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues
Kind regards,
Bill
Hi @LJ
We have recently added a template that could help you solve this issue: https://www.atlassian.com/software/jira/automation-template-library#/rule/9918938
Hope it helps and please let us know if it worked for you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @LJ,
It might be a simpler approach to use a filter subscription for this instead of an automation.
To do so, just navigate to Filters > Advanced issue search and update your filter to:
Project in (DLOG, DIG) AND issuetype = sub-task AND duedate >= startOfDay(5d)
AND duedate <= endOfDay (5d) AND assignee = currentUser()
Save the filter and create a subscription to a group of users that includes your assignees. They will receive a list of their assigned issues if there are any.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @LJ and welcome to the community,
If you click on "validate query" on your lookupIssues component, what does it return? If the answer is 0, then you have to place most likely and IF statement before sending the email and check that {{lookupIssues.size}} > 0.
In this case the email will be sent out, only if the lookupIssues yields at least one issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alex Koxaras _Relational_ , Thank you! :)
I am getting 1 issue found when I validate - would this option still apply? Thank you!
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.
Yes, it is assigned to me, however it is a subtask. The child issue and epic it sits under do not have assignees - do these need assignees in order for the email to send? We use epics as our 'Projects' and will only add assignees to subtasks and sometimes child issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can't notify assignees that are not there!
I think you need to revise the selection criteria if the issues are not assigned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just like Nic said, you can't send an email to an unassigned issue. So if the parent has an assignee, then it's best to add a branch for the parent and send an email to the assignee of the parent issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For this particular one to work, yes, because you've said "send to assignee". No assignee, no mail can be sent to them.
You could modify it to send to someone else other than the assignee.
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.