Hello,
I have an automation triggered by a new comment. After the trigger occurs, I use custom JQL to gather a list of issues and send an email using the lookup smart values. The JQL returns 3 issues but instead of getting one email with all 3 issues, I get 3 duplicate emails with all 3 issues in the body.
What is working: The JQL returns the issues I need and the email is populated with the list of issues
What is not working: I receive 3 emails instead of 1
Is there something missing in my automation? Do I need to place the lookup/email actions in a Branch?
Thank you!
Hi @sarai.makni
For Jira Cloud automation, Lookup Issues is one way to send the batch in one email, versus branch/scheduled rule to send multiple emails. Perhaps like this:
{{#lookupIssues}}
* {{key}}
{{/}}
Please post an image of your rule and the community will have better context to help you.
Best regards,
Bill
Hello! The steps you described are my current steps but I am still receiving multiple emails....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information. Perhaps you could explain your use case further...
When an issue is commented, the rule is triggered, and you send an email for a list of issues found by JQL.
Thanks any clarity you can add!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill!
Here are the start to finish steps:
Automation 1:
Automation 2 (screenshot above) triggered by Automation 1:
Reason for running 2 automations instead of just using one "Version Released" trigger. Our teams format their versions as "TeamName - Date of Release". Jira Cloud does not allow "~" on the fixVersion field so I could not write custom JQL to say "When the fixVersion ~ "TeamName" then Lookup issues and email list." The way I found around it, is to put the fixVersion name in a field where I can use the "~". Then, since I cannot have multiple triggers in a single automation, I created the second automation and checked the box for it to be triggered by the action of the first automation. Thus, narrowing down the issues to the Team's specific release and emailing only that team's released Issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that explanation, and here are more exploratory questions. :^)
Thanks in advance for your answers!
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.
Thanks, @sarai.makni
Given what you describe, I suggest you could do this with one rule if you have a known set of teams. For example:
What do you think?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I originally tried this but hit a roadblock at the "contains". I cannot type in a custom value...I have to choose from the list of fixVersions which defeats the contains because there are multiple versions. I want to narrow down to only released versions that start with the specific team name value, otherwise, it is going to return to me every single issue with a released version that looks like the version I selected...
Does that concern make sense? It is extremely possible that I am incorrectly interpreting how the contains in that component works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, I am confused...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I understand...but I cannot "Search" in the If-Then block. I only have the option to add every single fix version value for the team (which is quite a lot) and it will return the issues having the entire fix version value name of at least one of the values I select. Per the blue highlighted area, it states, "The field (fixVersion) can contain of these values." It does not say contain any of the string in the value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please try the advanced compare condition I noted above, rather than the simple field condition. You may then check the smart value from the trigger {{version.name}} to find the relevant team name.
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.