Azure DevOps Integration

This example demonstrates how to use Easy Integrations to create an Azure DevOps work item when a Jira issue is created.

Prerequisites

Before you begin the configuration, ensure you have the following prerequisites in place:

Ensure you have admin privileges to your Jira instance.
Ensure you have access to your Azure DevOps organization or project and have the necessary permissions to create Personal Access Tokens (PATs).

Configuration

Follow these steps to set up the integration between Jira and Azure DevOps using Easy Integrations:

Step 1: Create an Azure DevOps PAT

Open your Azure DevOps profile.
Create a PAT with the maximum expiration date. Make sure to note the token for later use.

Step 2: Configure Jira Credentials

Navigate to Apps in the Jira top menu and select Manage your apps.
From the sidebar, navigate to Easy Integrations configuration.
Click on the Credentials app menu item.
Add a new Basic Authorization credential with the PAT information.

Step 3: Configure a Listener

In Jira, access Easy Integrations configuration.
Under Listeners, add a new Listener with the following details:

Field	Description	Example value

Field

Description

Example value

Listener name

Give a name to track

Azure DevOps Integration

Listener is enabled

Works only when enabled

Checked

Retry attempt count

When something went wrong, number of retry count

3

Events

Only one event is enough for the example

JQL can be different, this example listens only to the Bug issues.

Event field	Example value
Event kind	JQL supported
Events	Issue created
JQL	issuetype = Bug

Condition

Pre-condition of the listener.

Checked

Condition script

Let's process issues those only have description starting with Good

return lodash.startsWith(data.event.issue.fields.summary, 'Good');

Action 1

Add a new "Call a Rest API" action

Action field	Example
Action name	Create an Azure DevOps Ticket
Condition	Unchecked
Action parameters	`var parameters = {};` `parameters['issue key'] = data.event.issue.key;` `parameters['issue summary'] = data.event.issue.fields.summary;` `parameters['issue status'] = data.event.issue.fields.status.name;` `return parameters;`
URL	https://dev.azure.com/{organization}/{project}/_apis/wit/workitems/$task?api-version=6.0
Method	POST
Headers	Accept=/ Cache-Control=no-cache Content-Type=application/json-patch+json
Authorization type	Basic
Credential	Select the Credential that is created on second step
Request body	`[` `{` `"op": "add",` `"path": "/fields/System.Title",` `"from": null,` `"value": "{{issue summary}}"` `},` `{` `"op": "add",` `"path": "/fields/System.Description",` `"from": null,` `"value": "Jira issue is {{issue key}} and status is {{issue status}}."` `}` `]`

Action 2

Add a new "Update a Jira issue" action

Action field

Example

Action name

Add Azure DevOps work-item link to Jira issue

Condition

Unchecked

Custom issue key

Unchecked

Notify users

Checked

Issue fields

We will save work item link to a text custom field


Field	Select a text Custom Field
Field script	`return data.apiData.api1.responseBody._links.html.href`
Custom shape for field	Unchecked

Click Save and then Submit to save your configuration.

Step 4: Create a Jira Bug Issue

Create a Jira bug issue. If everything is configured correctly, a new Azure DevOps work item should be automatically created, and all operations will be logged in the Execution Logs.

Step 5 (Extra): Audit Log

The audit log will display the created Listener configuration logs, and any future updates to the integration will be logged as well.

Azure DevOps Integration

Prerequisites

Configuration

Step 1: Create an Azure DevOps PAT

Step 2: Configure Jira Credentials

Step 3: Configure a Listener

Step 4: Create a Jira Bug Issue

Step 5 (Extra): Audit Log

Example screenshots

Listener screen:

First Action:

Second Action:

Execution Logs: