Overview

This article describes how to set up the JetPatch integration with Jira Server as a ticketing system. 

The integration allows approving and rejecting remediation plans and agent deployment tasks directly through Jira.

Once configured, JetPatch will automatically open a Jira ticket when a remediation plan is activated. 

The ticket can then be approved or rejected in Jira, and JetPatch will respond accordingly - proceeding with or halting the remediation.

Prerequisites

Before starting the setup, ensure the following:

• A Jira user with REST API capabilities is available, with permissions to Open, Read, and Write (Change) tickets.
• Integration with other ticketing systems (e.g., ServiceNow) is disabled in the JetPatch configuration.

Step 1: Configure Jira in intigua.properties

Before Version 5.0

1. Open the properties file for editing:

vi /usr/share/tomcat/default/conf/intigua.properties

Post Version 5.0

1. Open the properties file for editing:

vi /usr/share/intigua/services/data/intigua-main/conf/intigua.properties

Add Jira Configuration

Add the following configuration block to intigua.properties:

###############################################

################JIRA CONFIGURATION#############

###############################################

jira.hostUrl=https://jira.example.com:8080/

jira.username=Admin

jira.password=Password

# Enable / Disable JIRA for agent management

jira.enabled=true

#Enable / Disable JIRA for Remediation plans

jira.remediationPlanEnabled=true

#Name of custom, single-line text field used by Intigua to track tickets it creates.

jira.correlation.field=Intigua Correlation ID

#Name of the transition to use when closing a ticket

jira.transitions.success=Done

jira.approval.approved.values=Scheduled

jira.approval.reject.values=Rejected

jira.approval.pending.values=Pending Approval

# Priority to use for new tickets

jira.pg.priority=Medium

#Issue type to use for new tickets

jira.pg.issueType=Task

#Comma-separated list of labels for new tickets

jira.pg.labels=Jetpatch

#Project key to use for new tickets (e.g. CORE)

jira.pg.project=CORE

#Username of Remediation Plans approval assignee

jira.pg.assigneeUserName=john doe

####Add the following configuration for agent manager policies####

# Project key to use for new tickets (e.g. CORE)

jira.project=CORE

# Priority to use for new tickets

jira.priority=Medium

#Issue type to use for new tickets

jira.issueType=Task

#Comma-separated list of labels for new tickets

jira.labels=jetpatch,rocks

#Username of the agent management assignee

jira.assigneeUserName=Bobi

####################################################

Save and Restart

1. Save and exit the intigua.properties file.
2. Restart the service:

Before version 5.0:

systemctl restart tomcat

Post version 5.0:

docker restart intigua-main

Additional Configuration (Optional)

To add additional field configurations, follow Steps 2 and 3 in the ITSM Integration Setup article.

Step 2: Approve / Reject a Remediation Plan

After the Jira integration is established, create remediation plans in JetPatch and approve or reject them via Jira.

For the full approval process, see the JIRA Integration - Remediation Plan Approval Process article.