Jira Cloud Marketplace Guide

Jira is a proprietary issue tracking product developed by Atlassian that allows bug tracking and agile project management.

The Jira Cloud Marketplace Connection, just like its on-premises counterpart, enables you to integrate your Jira instance with Xurrent IMR on an account level, map Xurrent IMR Services with Jira Projects, allowing you to create incidents in Xurrent IMR for Jira Issues, and vice-versa, create Jira Issues for Xurrent IMR Incidents with synchronized statuses and notes.

⚠️

This is an account level Jira Cloud Marketplace Connection, providing two-way incident and ticket creation and status and notes synchronisation.

For other purposes, we also support:

The Legacy Jira One-Way integration - allowing you to only create incidents in Xurrent IMR for tickets/issues created in Jira.

The Jira Outgoing Two-Way Sync Integration, allowing you to create tickets/issues in Jira for every Incident created in Xurrent IMR, with bidirectional status and notes synchronization across the platforms.

In Jira Cloud:

Navigate to the Atlassian Marketplace, search for Xurrent IMR and click on the Get it Now button to download the app.
Once the app is installed, click on Manage app in the confirmation dialog that pops up. On the following screen, click on Configure.
You will see a Xurrent IMRToken in the instructions that appear. Copy this key and keep it in a safe place for use later.

In Xurrent IMR:

Click on your profile bubble on the top-right corner and then on Account.
To integrate Jira with Xurrent IMR, follow these steps to add a new key and configure account level settings:
- Navigate to the Connections section, choose Jira Cloud and click on Add New Key.
- Paste the key that you copied earlier into the provided field.
- Additionally, you will need to choose the account level setting. This can be either single or multiple Jira projects per Xurrent IMR service.
  - If you choose single Jira project per Xurrent IMR service, each Xurrent IMR service can be mapped to only one Jira project.
  - If you opt for multiple Jira projects per Xurrent IMR service, keep in mind that the project direction is locked at the account level. This means that a specific Jira project can only be mapped to a Xurrent IMR service as either an incoming or outgoing source across all services.
- It's essential to carefully consider the implications of selecting multiple Jira projects per Xurrent IMR service, as this configuration restricts the flexibility of mapping Jira projects to Xurrent IMR services based on their individual needs.

Now, go to Teams on Xurrent IMR and click on the team you want to add the integration to.
Next, go to Services and click on the relevant Service.
Go to Integrations and then Add New Outgoing Integration. Select the application 'Jira Marketplace' from the menu.
Follow these steps to configure integration settings for connecting your Xurrent IMR service with a Jira project:
- In the configuration section, start by selecting the appropriate tenant from the list of tenants associated with your account.
- Next, choose the specific Jira project that you intend to connect to this Xurrent IMR service.
- Select the desired Issue Type that aligns with your integration requirements.
- Choose the Integration Type based on the direction of data flow:
  - Incoming (Jira -> Xurrent IMR): For data flowing from Jira to Xurrent IMR.
  - Outgoing (Xurrent IMR -> Jira): For data flowing from Xurrent IMR to Jira.
  - Two-Way (Xurrent IMR <-> Jira): For bidirectional data flow between Xurrent IMR and Jira.
- You can also choose to lock the update direction if choosing the incoming or outgoing data flows — to create an integration where data doesn't flow back from the receiving platform in case of status updates.
- Customize your integration further by adding all the necessary custom mappings to meet your specific requirements.
Enable Sync Jira Comments Live on if you're like to sync the notes and comments between Jira and Xurrent IMR.

You can also choose to turn on the Sync Assignee option, after which all users with the same email on both Xurrent IMR and Jira will be automatically assigned the respective incidents/tickets on the other platform.

In certain advanced use cases, such as integrating with the Epic issue type, custom field mapping becomes essential. This is particularly useful when dealing with specific attributes, like the Epic Name. By default, this feature is disabled, but it can be enabled to accommodate your unique integration requirements.
- Identify the specific use case, such as integrating with the Epic issue type, where custom field mapping is necessary.
- Navigate to the integration settings and locate the option for custom field mapping.
- Enable the custom field mapping feature to unlock the ability to map fields dynamically.
- Once enabled, you can map the fields to dynamic inputs provided by the integration platform. In the case of sending messages to Jira, these dynamic inputs form the basis for the fields that will be included in the message.
- To create custom fields in Jira, navigate to Settings -> Issues -> Custom Fields from the left panel. Click on the Create Custom Field button on the top right and select the field type as desired. For eg: the Paragraph custom field can be used for Incident Summary or the Short Text field for most single line use-cases.

Now, click on Test Issue Creation then go to your Jira Dashboard, you should see a new issue created.

Note

When creating a mapping of Xurrent IMR service to Jira Project via this connection, you will only be able to create it only if there is no Jira Outgoing Integration mapped to that service for that particular project.

Alert Rule Jira Custom Fields

To Access the Incoming JIRA Custom fields, one would need to check for the custom fields in the Alert Payload that comes from JIRA.

In Alert rules, When either in JIRA Bidirectional (Jira <-> Xurrent IMR) or Incoming JIRA configuration (Jira -> Xurrent IMR)

Payload search can be used to look into the Custom Fields that JIRA Sends.
We can look into the latest alerts to get the ID of the Custom field that is needed.

Once we access this, one can essentially have the same functionality that JQL filter provides with Custom Fields.

Jira Custom Field Mapping

Jira Custom Fields can be used to create/update Jira tickets that need Custom Fields to be set upon creation of an Incident.

In a Default Jira setup, a common use-case for the same is the required Custom field Resolution Notes while closing a Epic Jira Ticket.

Upon activating Jira Custom Fields, the required fields for the given Issue type are automatically added as it needs to be set.
Any additional fields can be set be clicking the Add Field button on the top-right.

You can also add Dynamic variables that take information from the incident and auto append it to the JIRA message.