I am on the Jira Server / Enterprise edition.
I need to send an email reminder to reporters of issues they have created but are missing certain fields.
Also,
- I dont want to create filter subscriptions for this because the reporters are many.
- Similarily, I dont want to hard code reporters in JQL as well.
- I dont want to send 1 email per issue.
My requirement is: Automation with ,1 email with their set of issues, per reporter.
I have been searching the forums and all I have found is solution which is on Cloud Instance utilizing variable to hold the current "reporter" and modifying the JQL after branching.
But since Server instance does not have variables concept, can this be acheived in some other way?
Few of the links which discuss cloud version of automation for such scenario:
https://community.atlassian.com/t5/Jira-Software-questions/How-to-create-Automation-email-only-showing-Assignee-issues/qaq-p/2274061
https://community.atlassian.com/t5/Jira-Core-Server-questions/How-can-I-use-Advanced-Branching-in-Automation-for-unique/qaq-p/1909075
@Bill Sheboy in one of the threads has shared steps in the ticket which I am copying here for recap.. (bolded the parts I need help with cause I dont have "variables" option in my jira instance.)
- Trigger: scheduled with no JQL
- action: lookup issues, with the JQL, to find the issues of note
- advanced compare condition: to check for issues with {{lookupIssues.size|0}} is greater than 0
- advanced branch: over the possible assignees. The key is using distinct to walk the users/people who have assigned issues.
- variable: varAssigneeAccountId
- smart value: {{lookupIssues.assignee.accountId.distinct}}
- action: lookup issues again with the JQL, adding on assignee = {{varAssigneeAccountId}}
- action: send your email to the specific person/user
But need help to implement the same in Server instance.. please.
