JIRA Search to Email Pattern
This pattern queries JIRA for items submitted within the last day (at the time the pipeline is run) and within the specified projects, then sends out an email. It also uses the routing trick described in Performing an Action when there is no data to send an alternate email if nothing was reported. Source: JIRA issue Target: email Snaps used: JIRA Search, Mapper, Sort, Join, Sequence, Router, Email Sender You will need accounts for JIRA and the Email Senders. Set the following pipeline parameters: emailTo: who will receive the email emailFrom: who is sending the email JIRAurl: the url for you instance of JIRA, for example “https://company.atlassian.net” projects: the JIRA projects you want to query as part of the JQL query in the JIRA Search Snap. The query is set up to search multiple projects (for example, “projects in (ABC,DEF,GHI)” ) Refer to JIRA’s Advanced Searching documentation if you wish to change this query. The information sent in the email includes: Key (sent to be a link to the issue in JIRA), Issue Type, Title, Priority, Submitter, Status, and Assignee. Download Pattern - JIRA All Recent Items.slp (17.1 KB)How to Configure an Email Sender Snap to Avoid Individual Emails per Record
If you configure an Email Sender Snap with an input view and connect it to receive data from upstream Snaps, one email will be sent for each document processed through the pipeline unless you are using HTML table as the Email type. The HTML table format will embed the data in the email body up to the Batch size limit, sending as many emails as necessary to batch through the documents. Alternatively, if you want to just send the details as an attachment to an email, do not add an input view. Instead, just place the Snap unconnected on the workspace, write the data to a file, and have the Email Sender Snap attach that file to the email.
