Skip to content

Jira Service Management Data Mapping

Data Mapping and Transformation is one of the powerful features of Connect iPaaS. When you create a workflow, certain data points of your Trigger application are available in the Action application for data mapping.

These Data Mapping can be mapped to the specific attributes of the Action application. This powerful capability not only allows field mapping but also the complex transformation using excel style functions with hundreds of formulas and operations.

Example Scenario with Jira Service Management Trigger

In the example workflow, shown below, Jira Service Management is the trigger application. You can access the following attributes of the Jira Service Management event in any of the action applications while designing your workflow. In Jira Service Management, attributes will depend on the entity you will choose.

Click here to see the complete list of entities and their attributes. For Example, Request entity has the following attributes:

  • Issue Type - Type of the issue.
  • Project Name - Project Name in which issue will be created.
  • Project Key - Key of the project in which issue will be created.
  • Created At - Created time of issue.
  • Priority - Priority of the issue.
  • Summary - Summary of the issue.
  • Description - Description of the issue.
  • Issue Key - Key of the issue
  • Reporter - Reporter of the issue.
  • Assignee - Assignee of the issue.

Data mapping and transformation on Jira Service Management

Figure 1. Data mapping and transformations on Jira Service Management

As shown in Figure 1 above, we are mapping parameters from the Jira Service Management "Entity Created" trigger to the Microsoft Teams Action of sending a message to a channel. We can send messages in the channel based on data attributes of the Jira Service Management trigger. In this example, we are constructing the Message of the channel using Summary, Issue Type, Project Name, Created At, Priority, and Reporter.