Skip to end of banner
Go to start of banner

Create an Azure DevOps Work Item when a Jira Issue is Created

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

This page is about Easy Integrations for Jira Cloud. Using Jira On-Prem? Click the On-Prem button above.

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).

  • Before you proceed, generate a Personal Access Token with the following specifications:

    • Set the token's expiration date to the maximum allowed.

    • Make sure to note down the generated PAT. You will need this token for authentication during the integration configuration. For more information, refer to the related documentation.

🎯 Index

Configuration

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

Step 1: Create an Azure DevOps Personal Access Token (PAT)

  1. Open your Azure DevOps profile.

  2. Create a Personal Access Token (PAT) with the maximum expiration date. Make sure to note the token for later use.

Step 2: Configure Jira Credentials

  1. Navigate to Apps in the Jira top menu and select Manage your apps.

  2. From the sidebar, navigate to Easy Integrations configuration.

  3. Click on the Credentials app menu item.

  4. Add a new Basic Authorization credential with the PAT information.

Step 3: Configure Easy Integrations Listener

  1. In Jira, access Easy Integrations configuration.

  2. Under Listeners, add a new Listener with the following details:

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 fieldExample value

JQL supported
EventsIssue created
JQLissuetype = 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 fieldExample
Action nameCreate an Azure DevOps Ticket
ConditionUnchecked

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;
URLhttps://dev.azure.com/{organization}/{project}/_apis/wit/workitems/$task?api-version=6.0
MethodPOST
HeadersAccept=*/*
Cache-Control=no-cache
Content-Type=application/json-patch+json

Basic
CredentialSelect the Credential that is created on second step

[
  {
    "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 fieldExample
Action nameAdd Azure DevOps work-item link to Jira issue
ConditionUnchecked

Unchecked

Checked
Issue fields

We will save work item link to a text custom field



FieldSelect a text Custom Field

return data.apiData.api1.responseBody._links.html.href

Unchecked

  1. Click Save and then Submit to save your configuration.

Step 4: Create a Jira Bug Issue

  1. 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.

Example Screenshots

Listener screen:

First Action:

Second Action:

Execution Logs:

  • No labels