Jira Integration (via Microsoft Power Automate)
IntegrationIntroduction
You can integrate third-party systems with Service Manager 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 do not hesitate to contact your EasyVista contact, 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 Power Automate. An MS Power Automate workflow is created in Microsoft Azure Logic Apps using the EasyVista Service Manager connector.
Preview of the tools used in this integration
IntegrationTool_MicrosoftAzureLogicApps
- Microsoft Azure Logic Apps: It enables you to create logic apps that run workflows and provide access to cloud data and services using ready-to-use connectors.
IntegrationTool_MicrosoftAzureLogicApps
- Microsoft Azure Logic Apps enables you to create logic apps that run workflows and provide access to cloud data and services using ready-to-use connectors.
IntegrationTool_MicrosoftPowerAutomate
- Microsoft Power Automate (formerly known as Microsoft Flow): It enables you to automate recurrent tasks by building workflows using Web applications. The tool relies on standard connectors based on Microsoft Azure Logic Apps for interfacing with any endpoint via HTTP/HTTPS. It can also use the Microsoft Graph gateway via the Microsoft Graph API.
| Integration Data Feed (direction) | Authentication Type | Integration Connector Options | ||
|---|---|---|---|---|
|
Service Manager
|
|
|
Connector: When a HTTP request is received| Available versions | ||
|---|---|---|
| SaaS | On Premise | |
| Service Manager |  |
|
| Third-party product | |
N/A |
Data feed
Step-by-Step integration process
You can create a Service Manager ticket in Jira via Microsoft Power Automate in two steps:
- In Microsoft Azure Logic Apps, you create an MS Power Automate flow.
- In Service Manager, you create a Jira resource that you use in a REST step in a ticket creation process.
Prerequisites
- You must have an Azure subscription. If this is not the case, you can create a free account, or you can buy an Azure Pay-As-You-Go subscription.
- You must have the relevant accounts and access rights to the services interfacing with Logic Apps.
- You must have an account authorizing access to the Service Manager platform with a profile and access rights to create and modify workflows, access the Menu Editor Administration menu and other required menus, such as Service Operation and Service Transition.
Microsoft Azure Logic Apps: MS Power Automate flow creation
Description of the workflow
Step 1: Create the step that will trigger the Power Automate when a Service Manager ticket is created.
1. Log in to the Azure portal using your Azure account login.
2. Create a new logic app, then open the Logic Apps Designer.
See Microsoft Azure Logic Apps integration for the detailled procedure.
3. Create a When a HTTP request is received step to trigger the Power Automate.
4. Specify the information on the trigger.
- Body: Copy and paste the JSON schema below.
{
"$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.
5. Save the trigger.
The following information will be retrieved from Service Manager: Ticket description, Ticket ID, Host, URL, Account.
6. Click 
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.
Use the search field to find the connector and action you want quickly.
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.
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.
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.
3. Enter the login information.
Note: This information is required only when a connector is first created in Jira.
4. Click Save.
5. Complete the information on the Jira ticket.
- 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.
3. Save the Jira task number in Service Manager.
4. Complete the information on the Jira ticket.
- 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.
Service Manager: Create a resource called Jira used in a REST step of a process
Notes:
- The Jira resource will enable direct access to Jira tickets from Service Manager.
- It is associated with a Microsoft Power Automate service.
- It is used in a Service Manager process using a REST action type.
CreateInServiceManagerRestResource_Procedure
Step 1: Manage rights for using the Service Manager REST API
1. Select Administration > Access Management > User Profiles in the menu.
2. Select a user profile authorized to use the Service Manager REST API.
3. Tick the REST API box.
Your changes will automatically be saved.
4. Repeat the procedure for all authorized profiles.
Step 2: Create a resource called Jira associated with a Microsoft Power Automate service
See the detailed procedure.
Step 2.a: Create a service called Microsoft Power Automate
1. Select Administration > REST > Services in the menu.
2. Create a new service.
3. Specify the information below.
- Service Name: Enter the label Microsoft Power Automate.
- Authentication Method: None.
- Service URL: URL for accessing the new Microsoft Power Automate service.
- Copy and paste the URL you stored in your text editor when creating the MS Power Automate flow (step that will trigger the flow).
- 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}.
Step 2.b: Create a connection to the Microsoft Power Automate service.
1. Create a new connection.
2. Specify the information below.
- Connection Name: Enter the label JIRA.
- Authentication Method: None.
- Service Name: Select the Microsoft Power Automate service you created at step 2.a.
The URL of the service will automatically appear.
- subdomain: Copy and paste the prod-55.westeurope value of the URL you stored in your text editor.
Step 2.c: Create a resource associated with the Microsoft Power Automate service
1. Create a new resource.
2. Specify the information below.
- Label: Enter the label Jira.
- Resource URI: ID of the new resource.
- Copy and paste the URL you stored in your text editor when creating the MS Power Automate flow (step that will trigger the flow).
- 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
- Contents: Body of the query containing the data to be updated. Copy and paste the text below without inserting any spaces or line breaks.
{"mail": "{mail}","creation": "{date_creation}","id":"{id}","schedulestart": "{schedulestart}","scheduleend": "{scheduleend}","actionid":"{actionid}"}
Step 3: Use the Jira resource in a REST step of a process
1. Open the workflow or the business rule-related process you want.
- Workflow: References > Other References > Workflows (Operation/Transition)
- Business rule: Administration > Business Rules > Related Processes
2. Click and drag the new Jira resource from the REST Actions category of the palette of action types 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.
4. Click Confirm Changes.