Versions Compared

Old Version 6

changes.mady.by.user Derya Özdemir

Saved on

compared with

New Version 7

changes.mady.by.user Derya Özdemir

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This examples

Button handy
blankfalse
color#0052CC
nameCloud
linkhttps://appfire.atlassian.net/wiki/spaces/EIFJC/pages/10125437/Installation
width84
Button handy
blankfalse
color#EBECF0
nameOn-Prem
linkhttps://appfire.atlassian.net/wiki/spaces/EI4J/pages/11206868/Installation
width85

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#F4F5F7

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

This example shows an Easy Integrations listener to create an Azure DevOps work item when a Jira issue is created.

...

1- Open Azure DevOps profile and create a Personal Access Token (PAT) with the maximum Expiration date. Don't forget to note the token!Image Removed

...



2- Open Jira > Easy Integrations configuration > Credentials, and add a new Basic Authorization credential with the PAT information.Image Removed

...


3- Open Jira > Easy Integrations configuration > Listeners, and add a Listener with the following information.

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



Save


Click Submit to save


4- Create a Jira bug issue. If everything went well, a new Azure DevOps work item should be created and all operations should be logged to Execution Logs.

...

Example Screenshots

Listener screen

...

First Action

...


Second Action

...