Self-Solve Knowledge Search

Minimize Maximize
Integration [847] - Defect Case Exchange Service Adapter for JIRA (SX - JIRA)
Title :
Integration [847] - Defect Case Exchange Service Adapter for JIRA (SX - JIRA)
Document ID :
KM02029643
Product - Version:
service manager ;
OS :
Updated :
Mon Apr 03 00:00:00 GMT 2017
Summary :
HPE SW Integration Catalog
Defect Case Exchange Service Adapter for JIRA (SX - JIRA) - Catalog Id: 847

Description

Click here to learn more about Service Exchange Adapter

This Service Exchange Adapter allows connecting Atlassian JIRA to Service Exchange. This allows exchanging entities with any other product that is connected to Service Exchange as well (for example, ALM).

This page explains which use cases are supported by the JIRA Adapter.

 

The following diagram describes which are the inbound events the JIRA Case Exchange adapter handles and which are the outbound events the JIRA Case Exchange adapter can fire out.

This Adapter can be used in any project to connect Atlassian JIRA to another product-either directly, if the supported Use Cases fit the project needs, or by extending the supported Use Cases, as needed, through additional development.

Supported Use Cases:

Inbound Events

  1. Clone Incident. JIRA CX adapter can get an event of cloneIncident and invoke REST API to create new JIRA Issue linked to the source entity details.
  2. Retrieve Incident. JIRA CX adapter can get an event of retrieveIncident and invoke REST API to get specific JIRA Issue details.
  3. Update Linked Incident. JIRA CX adapter can get an event of updateLinkedIncident and invoke REST API to add a comment on JIRA Issue describing the action committed on source entity (for example, updating source entity summary or description).
  4. Incident Resolved. JIRA CX adapter can get an event of incidentResolved and invoke REST API to add a comment on JIRA Issue stating that the status of the source entity has been resolved.
  5. Incident Reopen. JIRA CX adapter can get an event of incidentReopen and invoke REST API to change JIRA Issue status to Reopen and, in addition, add a new relevant comment.
  6. Incident Closed. JIRA CX adapter can get an event of incidentClosed and invoke REST API to add a comment on JIRA Issue stating that the status of the source entity has been closed.
  7. Get Changed Incidents For Case Exchange. JIRA CX adapter can get an event of getChangedIncidentsForCx and invoke REST API and retrieve all changed issues from last checkpoint. The result of this REST API will determine if the JIRA CX adapter will fire its outbound events into OO system.


Outbound Events

  1. Incident Rejected. JIRA CX adapter can fire an event incidentRejected that notifies the source adapter that the JIRA Issue was rejected by a JIRA user that has changed the Issue status to Resolved or Closed, with the resolution Won't do or Won't fix.
  2. Incident Resolved. JIRA CX adapter can fire an event incidentResolved that notifies the source adapter that the JIRA Issue was resolved by a JIRA user that has changed the Issue status to Resolved, with the resolution Fixed.
  3. Incident Suspended. JIRA CX adapter can fire an event incidentClosed that notifies the source adapter that the JIRA issue was:
    1. Suspended by a JIRA user that has changed the Issue status to Resolved or Closed, with the resolution Incomplete or Cannot Reproduce.
    2. Closed by a JIRA user that has changed the Issue status to Closed, with the resolution Fixed.

 

General

Atlassian JIRA

Currently no Solution uses this adapter
Service Exchange
2/19/2016

Documentation

Documentation
Downloadable Adapter Material

Supported Versions

Prerequisites

The following products must be installed and fully functional:
  • Propel SX version 2.0 or later. Installed and running.
  • Atlassian JIRA version 6.4.8. Installed and running.
  • JAVA JDK version 1.7 or later. Installed and running.

Supported Versions
  • Propel Service Exchange 2.0 or later (Recommended 2.0)
  • Atlassian JIRA 6.4.8
  • JAVA JDK 1.7 or later (Recommended 1.7)

 

Support Matrix

Atlassian JIRA
Propel Service Exchange
SupportedSupported (see comments)Not Supported

IT4IT™ Reference Architecture and HPE Implementations

Want to see how you can realize the best value from integrating HPESW products? See the IT4IT™ Reference Architecture and HPESW Reference Implementation.

Generated: 4/3/2017 4:40:46 AM