Getting The Response Header and not Response Content from Jira Webhook
The header is a JSON file and content comes in a binary file as can be seen from the trigger task debug trace below: Tried using the pipeline below and I only get the response header also included below and can’t find a way to get the content:JIRA event capture in real time via WebHooks and triggering Snaplogic pipelines
Jira event capture in real time via WebHook and trigger Snaplogic pipeline How to Trigger Snaplogic Pipeline after an event in Jira This document shows how to setup a Jira instance to trigger a Snaplogic Pipeline (REST API) after an event in Jira and send the event information to Snaplogic pipeline. The events can be one of the following: • Issue related events • Project related events • User related events • JIRA configuration related events • JIRA Software related events Integration Scenario: Update ServiceNow ticket when an Issue is updated in Jira Steps involved in this integration are: • Create a SnapLogic pipeline and publish it as a triggered task • Create a WebHook in Jira to trigger a SnapLogic pipeline after an issue is updated in Jira Step1: Create a Snaplogic pipeline and publish it as a triggered task The diagram below is a screen shot of SnapLogic pipeline that consumes the json document sent by Jira after an event (Example: Issue update, like add comments) happens in Jira and updates corresponding ServiceNow ticket. The Binary Router Snap receives the incoming json from Jira and sends the output to two flows. In the first flow, the incoming json document in binary format is parsed and converted to document format, mapper is used to map Jira issue information to appropriate fields in Service Now and “ServiceNow Update Snap” is used to update ServiceNow ticket. In the second flow, the json received from Jira is written to an audit file. A section of the json document received is below. { “timestamp”: 1483558289780, “webhookEvent”: “comment_created”, “comment”: { “self”: “https://snaplogic.atlassian.net/rest/api/2/issue/25701/comment/21801”, “id”: “21801”, “author”: { “self”: “https://snaplogic.atlassian.net/rest/api/2/user?username=admin”, “name”: “admin”, “key”: “admin”, “created”: “2017-01-04T11:31:29.780-0800”, “updated”: “2017-01-04T11:31:29.780-0800” } } The following is a triggered task REST API created by Snaplogic for the integration scenario and we will use this to configure WebHook in Jira. https://elastic.snaplogic.com:443/api/1/rest/slsched/feed/ConnectFasterInc/Shankar%20Sanikop/ServiceNow%20Jira/Jira%20Outbound%20Trigger%20Task? Step2: Create a WebHook in Jira to trigger a Snaplogic pipeline after an issue is updated in Jira In Jira go to Applications. You will see WebHooks in Advanced Configuration Create a new WebHook to call the Snaplogic Triggered task In the URL configuration: Put the Snaplogic Triggered task, including the authorization information (bearer_token) https://elastic.snaplogic.com:443/api/1/rest/slsched/feed/ConnectFasterInc/Shankar%20Sanikop/ServiceNow%20Jira/Jira%20Outbound%20Trigger%20Task?bearer_token=FrcE0Whf6r2NjHx Configure the event related information, in this integration we are capturing the issue related events. The diagram below shows the available events of an issue that can be captured and also you can write a JQL query send events only that match certain conditions. strong text
Get JIRA Attachment Content Document in Snaplogic Pipeline
Hi all, We’re trying to get the JIRA Attachment Content document and it gives the URL of the attachment as shown below:- “content”: “https://myjira-abc.atlassian.net/secure/attachment/10000/sample.txt” We are trying to get the metadata of this content and convert it into base64 encoded data but unable to do so. Is there a way we can fetch the metadata of this content using REST GET and which REST API do we need to call? If there’s a better approach to this, please feel free to propose 🙂 Thanks.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)
Creating a ServiceNow Incident from a JIRA Issue
Contributed by @rdharnikota This pipeline gets the details of a specified JIRA issue and creates an incident in ServiceNow. Configuration The first Mapper maps the JIRA issue ID and the issue comments to the ServiceNow incident. Other fields are also manually set in the Mapper. Either update the values or map the fields that you need to carry over. Sources: JIRA issue Targets: ServiceNow incident Snaps used: JIRA Get, Mapper, Router, ServiceNow Insert, ServiceNow Update Downloads Create SNOW Incident from JIRA.slp (8.8 KB)
