Jira Integration (via Microsoft Flow)


About This Integration

IntegrationIntroduction

You can integrate third-party systems with Product name - ev itsm.png in many ways. The method you select will depend on business requirements, architectural and security constraints as well as the characteristics specific to each third-party application or service.

This document describes an integration process that has already been implemented in a customer context. 

To find out more about this integration (e.g. scripts to be used), please contact the Logo - EasyVista.png Consulting & Professional Services team, the Logo - EasyVista.png Support team, or your service provider and integrator.
 

Overview of the integration

Jira is a software developed by Atlassian that enables bug and incident tracking and agile project management.
This integration enables you to create Jira tickets from tickets created in Service Manager via Microsoft Flow. An MS Flow workflow is created in Microsoft Azure Logic Apps using the EasyVista Service Manager connector.

  • Microsoft Flow is used to automate recurrent tasks by building workflows via Web applications using Microsoft Azure Logic Apps-based connectors. It is used to interface with any termination point via HTTP/HTTPS protocol.
       Open url.png See Microsoft Flow integration.
     
Integration Data Feed (direction) Authentication Type Integration Connector Options

Logo - EV Service Manager.png

Down arrow.png

Logo - Microsoft Flow.png

Down arrow.png

Logo - Jira Software.png

  • Depending on the third-party service used (authentication managed by Logic Apps)
  • Basic Authentication for the Service Manager REST API
  • Service Manager:

    EV Integration connector icon - Workflow.png    Workflows

    EV Integration connector icon - Business rule.png    Business rules

  • MS Flow:

    EV Integration connector icon - Receive.png    Connector: When a HTTP request is received

    (Trigger Service Manager => Logic Apps)

Service Manager SaaS

Service Manager On-premise

Check icon.png

Check icon.png

SaaS Version of Third-Party Product

On-Premise Version of Third-Party Product

Check icon.png

N/A

Data feed

         Data feed diagram - EN.png

Step-by-Step Integration Process

You can create a Service Manager ticket in Jira via Microsoft Flow in two steps:

Prerequisites

MS Flow flow creation in Microsoft Azure Logic Apps

Description of the workflow

         Azure flow description.png

Step 1: Create the step that will trigger the flow.

1. Log in to the Azure portal using your Azure account login.

2. Create a When a HTTP request is received step to trigger the flow.

         Action Azure - When a http request is received.png

3. Specify the information on the trigger.

  • Body: Copy and paste the JSON schema below.

    Display the JSON schema

    {
       "$id": "http://example.com/example.json",
       "type": "object",
       "definitions": {},
       "$schema": "http://json-schema.org/draft-07/schema#",
       "properties": {
           "Description": {
               "$id": "/properties/Description",
               "type": "string",
               "title": "Description",
               "default": "",
               "examples": [
                   "{Description}"
                ]
            },
           "id": {
               "$id": "/properties/id",
               "type": "string",
               "title": "Id",
               "default": "",
               "examples": [
                   "{id}"
                ]
            },
           "Host": {
               "$id": "/properties/Host",
               "type": "string",
               "title": "Host",
               "default": "",
               "examples": [
                   "{Host}"
                ]
          
     },
           "URL": {
               "$id": "/properties/URL",
               "type": "string",
               "title": "URL",
               "default": "",
               "examples": [
                   "{URL}"
                ]
            },
           "Account": {
               "$id": "/properties/Account",
               "type": "string",
               "title": "Account",
               "default": "",
               "examples": [
                   "{Account}"
                ]
            }
        }
    }
  • Method: POST.

4. Save the trigger.

  The following information will be retrieved from Service Manager:

  • Ticket description
  • Ticket ID
  • Host
  • URL
  • Account

5. Click Copy icon.png to copy the URL displayed in the HTTP POST URL field and paste it in your text editor in order to store it temporarily. You will be asked for the URL when defining the configuration in Service Manager (step 2).

Step 2: Retrieve the Service Manager ticket information.

1. Search for the EasyVista Service Manager connector.

2. Select the View Request – Incident action associated with this connector.

Best Practice icon.png  Use the search field to find the connector and action you want quickly.

         Action Azure - EV SM View request – Incident (1).png

         Action Azure - EV SM View request – Incident (2).png

3. Specify the information for the Service Manager account and ticket.

  • Account: Account on the Service Manager platform.
  • ID: Ticket ID in Service Manager.

4. Select the connection to your environment.

         Action Azure - EV SM View request – Incident (3).png

Step 3: Retrieve the ticket description in Service Manager.

1. Search for the EasyVista Service Manager connector.

2. Select the View Request – Incident Comment action associated with this connector.

         Action Azure - EV SM View request – Incident Comment.png

3. Specify the information for the Service Manager account and ticket.

  • Account: Account on the Service Manager platform.
  • ID: Ticket ID in Service Manager.

3. Select the connection to your environment.

Step 4: Create the ticket in Jira.

1. Search for the Jira connector.

2. Select the Create a new issue action associated with this connector.

         Action Azure - JIRA - Create a new issue (1).png

3. Enter the login information.
Note: This information is required only when a connector is first created in Jira.
         Action Azure - JIRA - Create a new issue (2).png

4. Click Save.

5. Complete the information on the Jira ticket.

         Action Azure - JIRA - Create a new issue (3).png

  • Project: The list contains all Jira projects associated with your accounts.
  • Issue Type ID: Select the type of ticket, e.g. bug, subtask, etc.
  • Summary: Summary of the ticket.

    example  Ticket no. #RFC_NUMBER (information from the results of the EasyVista Service Manager > View Request – Incident action)

  • Description: Ticket description.

    example  Comment (information from the results of the EasyVista Service Manager > View Request – Incident Comment action)

6. Select the connection to your environment.

Step 5 (optional): Modify the ticket in Service Manager.

1. Search for the EasyVista Service Manager connector.

2. Select the Update request – Incident action associated with this connector.

         Action Azure - EV SM Update request – Incident (1).png

3. Save the Jira task number in Service Manager.

4. Complete the information on the Jira ticket.

         Action Azure - EV SM Update request – Incident (2).png

  • Account: Account on the Service Manager platform.
  • ID: Ticket ID in Service Manager.
  • Available_Field_6: ID of the Jira ticket (information from the results of the Jira > Create a new issue action: step 4).

5. Select the connection to your environment.

REST action creation in a process in Service Manager

Step 1: Manage rights for using the Service Manager REST API.

    Open url.png See the description of profiles.

1. Select Administration > Access Management > User Profiles in the menu.

2. Select a user profile authorized to use the REST API.

3. Tick the REST API box.
Your modifications will automatically be saved.

4. Repeat the procedure for all authorized profiles.

Step 2: Create a resource associated with a Microsoft Flow service.

       Open url.png See How to define a new resource and associate it with a REST action.

1. Select Administration > REST > Services in the menu.

2. Create a new service.
         Service Manager - Microsoft Flow Service.png

  • Service Name: Microsoft Flow.
  • Authentication Method: None.
  • Service URL: URL for accessing the new Microsoft Flow service.
    • Copy and paste the URL you stored in your text editor in step 1 when creating the MS Flow flow in Logic Apps.
    • You should keep only the text displayed in yellow below.

      https://prod-55.westeurope.logic.azure.com:443/workflows/a903f9140a874277be8b9dd39b5c4305/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=R-FJw5q_MEn-I-98MNF794bVtN91QIWFt8gixg-8

    • Replace prod-55.westeurope with {subdomain}.
       

3. Create a connection to the Microsoft Flow service.
         Service Manager - Microsoft Flow Connection.png

  • Connection Name: Jira.
  • Authentication Method: None.
  • Service Name: The Microsoft Flow service you created earlier.
    The URL of the Microsoft Flow service will automatically appear.
  • subdomain: Copy and paste the prod-55.westeurope value of the URL you stored in your text editor.
     

4. Create a resource associated with the Microsoft Flow service.
         Service Manager - Microsoft Flow Resource.png

  • Label: Name of the resource.
  • Resource URI: ID of the new resource.
    • Copy and paste the URL you stored in your text editor in step 1 when creating the MS Flow flow in Logic Apps.
    • You should keep only the text displayed in red below.

      https://prod-55.westeurope.logic.azure.com:443/workflows/a903f9140a874277be8b9dd39b5c4305/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=R-FJw5q_MEn-I-98MNF794bVtN91QIWFt8gixg-8

  • Content: Body of the request containing the data to be updated. Copy and paste the text below without inserting any spaces or line breaks.

    Note: If you paste a JSON schema copied from a third-party editor such as Microsoft Word, Notepad++, etc., invisible characters may be inserted. This will create an error in the processing of the REST step using the resource.

    {"mail": "{mail}","creation": "{date_creation}","id":"{id}","schedulestart": "{schedulestart}","scheduleend": "{scheduleend}","actionid":"{actionid}"}

Step 3: Add the resource to a REST step in a process.

       Open url.png See How to define a new resource and associate it with a REST action.

1. Open the workflow or the business rule-related process you want.

  • Workflow: References > Other references > Workflow (Operation / Transition)
  • Business rule: Administration > Business Rules > Related Processes

2. Click and drag the new resource from the REST Actions category to the graphic editor of the process.
A new step will be added to the process.

3. Double-click to define the properties of the new step.

Tags:
Last modified by Unknown User on 2020/04/02 18:51
Created by Administrator XWiki on 2020/03/24 12:25

Shortcuts

Recent changes
•  Service Manager
•  Service Apps
•  Self Help

Glossary

Powered by XWiki ©, EasyVista 2020