I am looking for some help with the Jira Automation, bulk send and Lookupissues features.
I've tried every suggestion in this thread (https://community.atlassian.com/t5/Jira-Software-questions/Sending-an-email-with-a-list-of-issues-using-Automation-for-Jira/qaq-p/1192501), but my list always comes up empty, even though there are 10 issues that are found when I run the audit log.
Here are screenshots of my rule--any assistance would be greatly appreciated!
Thanks!
Allison
Hi @Allison -- Welcome to the Atlassian Community!
Noticing that you are on Jira Server, the Lookup Issues action is not available there...it is a Cloud feature.
Your equivalent for Server is {{issues}} Please note the plural. The syntax will be basically the same as the recommendations to use Lookup Issues, just substitute in {{issues}}
Please look here for an example:
https://confluence.atlassian.com/automation/smart-values-993924860.html#Smartvalues-issuesissues
Best regards,
Bill
Hi @Bill Sheboy,
This worked on my requirement. Thanks much for the solution.
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 helped. And...the Atlassian team appears to be working on adding the Lookup Issues action for the Server/Data Center, so that will make this scenario easier to complete in the future. You may watch here to see their progress: https://jira.atlassian.com/browse/JIRAAUTOSERVER-53
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Allison, as it says in the answer from the https://community.atlassian.com/t5/Jira-Software-questions/Sending-an-email-with-a-list-of-issues-using-Automation-for- Jira / qaq-p / 1192501, to do something like this it is simpler and more tedious to create a filter in jira with that JQL, choose the custom fields you need and create a subscription to send the result by mail
Anyway, if you still prefer to do it with automation, the lookupissues variable will come empty unless you first use a action of type "Lookup issues"
Regards!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Juan,
Thanks for sharing this. How did you get to the lookup issues variable set up? I'm not seeing it on my end at first glance.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To answer that question - this Lookup Issues action is where you define the query that {{lookupissues}} is aware of later in the rule. When you use this action, the payload in your send-email action gets sent the data from the query.
This query can be regular JQL, or it can be a mix of JQL and {{smartvalues}} - but if you use smart values, you can't use the little "validate query" function you can see in the corner of the above screenshot.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
removing my answer - Juan's comment is correct. You'll need to add a lookupissues step first
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This btw - is designed for Slack messages - so I'm not sure if it will give you any weird results - but the formatting might help you along.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
(one more note - in the screenshots you can still clearly make out your full name and email. the paint isn't thick enough!)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline 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.