Use case : For each reporter , all the issues he has created without mandatory tags a consolidated email needs to be sent with jira links of all the issues.
Using issue.toUrl simply sends one email per issue ( ex 5 emails for 5 issues ) & #lookupIssues is sending emails with blank body. Below are the screenshots :
Hi @Kunal Kumar
To use the {{lookupIssues}} smart value, you need to first call the Lookup Issues action. Please try this change to your rule:
Kind regards,
Bill
Get it , but I am on JIRA server and lookup issue action is not available for me to use. Is there any other way I can achieve this use case ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for clarifying, as your post indicated you were using Cloud but you are actually using Server/Data Center.
The Server/Data Center version has an option for bulk-issue processing. This is a setting you select either with the Scheduled Trigger with JQL or with a Branch. After enabling the setting, you would use the {{issues}} rather than the {{lookupIssues}} smart value. https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html
You can use your original rule with JQL in the scheduled trigger, enable bulk processing, and replace {{lookupIssues}} references to {{issues}} Please note that is plural {{issues}} for bulk-issue handling.
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.
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.