Use Case

  • Collect new Jira Tasks to create new Remedy Problems
  • Synchronize any updates to either Jira Tasks or Remedy Problems, like title, description, urgency, comments, attachments, etc. to the other system

Requirements

This section provides information about the requirements, which should be met, in order the integration template could be used.

Integration Requirements


Jira RequirementsRemedy Requirements
Access Details 
  • Server URL 
  • Integration User 
  • URL to access the Remedy AR System REST
  • Integration User
Permissions
  • Browse Projects
  • Assign issues
  • Edit Issues
  • Resolve Issues
  • Transition issues
  • Add Comments
  • Create Attachments

    Advanced
    • Create Problem
      • Browse Projects
    • Update Problem
      • Browse Projects
    • Backsync Task
      • Edit Issues
      • Resolve Issues
      • Transition issues
      • Add Comments
      • Create Attachments
  • READ access to Remedy form: "AR System Metadata: arschema"
  • Problem Master and Problem Viewer 
    • Support Staff = YES (member of support group)
    • Access Restriction = Unrestricted Access 

      Advanced
      • Create Problem
        • Problem Master
      • Update Problem
        • Problem Master
      • Backsync Task
        • Problem Viewer

Network Requirements


Network Requirements
Communication
  • ZigiOps → Jira (80/443)
  • ZigiOps → Remedy (80/443)

Setup

To enable the integration, you should follow the steps below.

  1. You should start with the selection of the integrated systems and the integrated entities. The integrated entities should be pre-selected if there are no issues with the credentials/permissions, used in the connected systems configuration.

    Example

  2. Press the Save button to save the changes.

    Example

  3. You should enable the operations to start the integration.

    Example

Operations Explanation

This section provides information about the predefined operations of this integration template, including the default field mapping configuration. Each operation consists of two tabs - Source, Field Map. The Source tab contains the trigger, trigger conditions and expressions configuration. The Field Map tab contains the mapping configuration. 

Create Problem

This operation polls the data from Jira. It is designed to collect Tasks from Jira and create Problems in Remedy. The task is collected from the Jira instance, then it is internally processed through the field mapping configuration, and finally, a request is sent to Remedy to create a new Problem.

Source

From this tab you could customize the polling interval, trigger conditions and expressions or use the defaults.

Example

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements.

Example

Update Problem

This operation polls the data from the Jira system. It is designed to detect any changes to the taks and synchronize them with the corresponding Remedy problem, as per the mapping, configured on ZigiOps side.

Source

From this tab you could customize the polling interval, trigger conditions and expressions or use the defaults.

Example

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements.

Example

Backsync Task

This operation polls the data via the Remedy AR System REST API. It is designed to detect any changes to the problem and synchronize them with the corresponding Jira task, as per the mapping, configured on ZigiOps side.

Source

From this tab you could customize the polling interval, trigger conditions and expressions or use the defaults.

Example

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements.

Example

Recommendations

This section provides information about the recommended considerations, which should be taken into account, before starting the integration.

Correlation

It is recommended to keep the default correlation configuration, unless you're familiar with the integration and the specifics of the integrated systems. You could contact our support team for assistance, prior further changes to the correlation configuration.

Mapping

The predefined templates are complied with the specifics of the integrated systems. It is recommended to confirm if your integrated systems have any required fields, which must be reported, so you could map them accordingly. Please note that if a required field is not mapped, the operation might fail. In this case, you could review the troubleshooting page for more information about the operation's execution history.

Required Fields

Please note that the below fields are required by default. It is highly recommended to map all required fields before starting the integration.

FieldValueAction
first_nameJohnCreate Problem
last_nameDoeCreate Problem
z1d_actionPROBLEMCreate Problem