This documentation supports the 19.08 version of BMC Helix Multi-Cloud Service Management.

Enabling DevOps between JIRA Software and Remedy ITSM

BMC Helix Multi-Cloud Service Management helps facilitate DevOps practices in organizations that use multiple tools. You can integrate BMC Helix Multi-Cloud Service Management with Atlassian JIRA Software and manage tickets across multiple applications and teams more effectively. For more information about DevOps integration, see DevOps integration with BMC Helix Multi-Cloud Service Management.

Before you begin

Complete all pre-configuration tasks before you enable the integration.

To select the integration option for DevOps between Jira and Remedy ITSM

You can use Multi-Cloud to configure features provided for different cloud service providers through its Quick Configuration Guide section.

  1. Launch BMC Helix Platform by using the URL provided in the email sent to you from BMC, and log in as an administrator.
  2. Select Workspace > Applications > Multi-Cloud Service Management from the list of applications.
  3. To launch BMC Helix Multi-Cloud Service Management, in the top-right corner of the page, click Visit Deployed Application.

    Multi-Cloud URL

    You can access BMC Helix Multi-Cloud Service Management directly by entering the URL https://hostName:portNumber/innovationsuite/index.html#/com.bmc.dsm.mcsm and logging in as a tenant administrator.

  4. To open the configuration page, click Settings.
  5. Select Start Here > Quick Configuration Guide.
    BMC Helix Multi-Cloud Service Management lists the features available to you.

6. For the the DevOps Integration feature for Jira and Remedy ITSM, select the following options under DevOps Integration.

    • Manual association of Remedy Change with Jira Issues
    • Remedy Change to Jira Issue
    • Remedy Incident to Jira Issue
    • Jira Issue to Remedy Change
    • Jira Issue to Remedy Incident
    • Remedy Problem to Jira Issue (requires BMC Remedy IT Service Management and  Remedy with Smart IT version 1808 patch 1)
    • Remedy Work Order to Jira Issue (requires BMC Remedy IT Service Management and  Remedy with Smart IT version 1808 patch 1)

The Configuration Links page displays a list of the common configurations, connectors, flows, and connector targets and processes that you need to configure as described in the next tasks. 

To map Jira vendor data to Remedy ITSM or Smart IT

Configuring vendor data includes setting up a vendor organization and defining vendor mappings for the technology provider. Vendor mapping is the metadata of the vendor that is used to define dynamic field mapping between Remedy ITSM and Vendor application fields. Vendor mapping metadata is required to send Remedy ITSM ticket to the vendor application. Vendor mapping ensures that notifications about changes made to the Remedy ITSM fields are added as a comment to the corresponding vendor application ticket. If you are integrating with multiple instances of Remedy ITSM, create a vendor mapping for each instance of Remedy ITSM.


Best Practice

BMC recommends that you set up the vendor organizations before starting the BMC Helix Multi-Cloud Service Management configuration. For more information about adding vendor organizations, see Performing pre-configuration tasks.

  1. If required, to create or modify a vendor organization, in the Configuration Links page, click  Manage Vendor Organizations  under Configure Jira .

  2. To add or update the vendor mapping, in the Configuration Links page, click Map Vendors under  Configure Jira.

    Note

    For multiple instances of Jira, you need to add a vendor mapping for each instance of Jira.

    1. On the Map Vendors page, click 

       Click here to view image...

    2. Enter a Description that makes it easy for you to identify the vendor metadata configuration.
    3. Select the Ticketing Technology Provider
      The technology provider is the organization that develops the vendor application. For example, Amazon is the Ticketing Technology Provider for AWS.
    4. If you have multiple Jira instances, enter a Instance Name that BMC Helix Multi-Cloud Service Management can use to identify each Jira instance.

      The recommended format for an instance name is \  instanceName instance instanceNumber

    5. Click Add Mapping.
      BMC Helix Multi-Cloud Service Management displays the default Instance URLVendor Field Mapping, and Display Field Mapping.
    6. Update the Instance URL with the server name and the port number for the Jira instance that you are mapping. 
      This URL represents the URL for connecting with your Jira server.
    7. Click  { }  to open the JSON editor, and modify Vendor Field Mapping and Display Field Mapping to add or delete values. 
      • Vendor Field Mapping — Defines how BMC Helix Multi-Cloud Service Management maps Remedy ITSM fields to vendor application ticket fields.

        Update the value of fields.project.name with the name of your Jira project for ticket-brokering-lib:Incident ticket-brokering-lib:Change,  ticket-brokering-lib:Problem, and  ticket-brokering-lib:Work Order .

         Click here to view image

      • Display Field Mapping — Defines how vendor application ticket fields are displayed on the BMC Remedy with Smart IT console.

         Click here to view image

  3. If you do not want the Problem ticket or Work Order to be automatically resolved when the corresponding vendor application ticket is resolved, select for Resolve Problem Ticket When Vendor Closes it or Resolve Work Order When Vendor Closes it. By default,  the ticket is resolved when the corresponding ticket is closed in the vendor application.

To configure connectors for integrating Remedy ITSM and Jira with Multi-Cloud Service Management

For each feature you selected, complete the following procedure for the connectors listed in the Configuration Links page.

  1. To navigate to BMC Helix Integration Service, in the Configuration Links page, click Configure connectors in Integration Studio under Required Common Configurations.
    You need to configure the connectors listed for each feature, in addition to the connectors listed under Required Common Configuration.

  2. To enter field values, select the connector such as, Remedy ITSM and click Configuration.
    You might need to click the arrow on the ribbon in the lower section of the screen to open the Configuration pane.

  3. To update the configuration defaults, enter the appropriate field values by referring to the corresponding connectors at the end of this section.
  4. To add details of the user account to be used to access the vendor application, click Accounts.

List of connectors for integration with JIRA


 Remedy ITSM

  • Configuration
    If you are integrating BMC Helix Multi-Cloud Service Management with an on-premises instance of Remedy ITSM, enter the following values:
FieldValue
Site Select the site that you created for Remedy.
AR serverEnter the name of your on-premises AR System server.
AR server portEnter the port number for your on-premises AR System server.
  • Account
    Add the account of a Remedy ITSM user who has permissions to view business service requests, and to update incidents, change, or problem requests.


 Multi-Cloud

  • Configuration
    During activation BMC configures the Multi-Cloud connector. Do not modify the default Multi-Cloud connector configuration.
  • Account
    BMC sets up the account for the Multi-Cloud connector.
    Click to re-authenticate your account after you change the password for your tenant administrator account in BMC Helix Innovation Studio.


 SMTP Email

  • Configuration
    To send email notifications for errors, specify values for the following fields:
FieldValue
NameEnter a name for the connector configuration.
SiteSelect the appropriate site for your email server.
Connection typeSelect the type of connection for your email server.
  • Account
    Add an email account to use for sending error notifications.


 Jira
  • Configuration
    • If you are integrating with an on-premises instance of Remedy ITSM, enter values for the following fields:

      FieldValue
      Name Enter a name for the connector configuration
      Site For each on-premises Jira instance, select the site that you created.
      For Jira instances in the cloud, select Cloud as the site.
      Jira Server Hostname Enter the name of your Jira server.
      Jira server Port

      Enter the port number of the Jira server.
      Enter 443 if your Jira server is SSL enabled.

      Protocol Enter the protocol used by the Jira server.
    • If you need to integrate with multiple instances of Jira, add a Connector Configuration for each instance.
  • Account
    • Add the account of a Jira user who can view and update Jira issues.
    • If you need to integrate with multiple Jira instances, add an account for each of the Jira instances.

To configure flows between Remedy ITSM, Multi-Cloud, and Jira

For each feature you selected, complete this procedure for the flows listed in the Configuration Links page.

  1. To navigate to BMC Helix Integration Service, in the Configuration Links page, click Configure flows in Integration Studio under Required Common Configurations.

    You need to configure the flows listed for each feature, in addition to the flows listed under Required Common Configuration.

  2. To open the flow template page, on the Catalog tab in Integration Studio, click the flow you want to configure.

     Click here to view the image

  3. To create a copy of the flow template, click .

    To update the name of the flow that you have copied from the flow template, select My Flow, open the flow that you have copied and update the title.
  4. Select the appropriate accounts for the end-point connectors of the selected flow.
    You specify the connector accounts when configuring connectors.
  5. Specify the trigger Conditions and Field mapping, and click OK.
    For more information about trigger conditions and field mappings, see the list of flows in the Configuring flows section.

  6. Click My Flows and select the flow that you had created from the flow template.
  7. Click Details in the right pane to verify the target values for the trigger conditions and the field mappings.

List of flows for integration with JIRA


 Send Error Notification

  • Trigger
    Ensure that Flow Target is set to Multi-Cloud.

  • Field mappings
    • In the To field, enter the email account that will receive the error notification.
    • The following out-of-the-box field mappings can be modified; however, BMC recommends that you retain the default values.
      • Subject
      • From


 Create Incident
  • Project
    To query for issues to send to Remedy ITSM, enter the name of the projects.

  • Trigger

    The trigger condition determines the qualification criteria to create a Remedy ITSM ticket. You can use any field in your trigger condition. A single issue in Jira can only be related to a single record in Remedy ITSM.

    Note

    If you are also creating Work Orders and Change Requests from Jira, make sure the trigger condition is unique to creating an incident.

  • Field mapping
    The default field mappings follow the best practices for mapping data from a Jira issue to a Remedy ITSM Incident. You can change these mappings as per your business requirements.

    Remedy ITSM fieldJira fieldAdditional information
    Priority Priority
    Summary Issue Summary
    Company

    Out of the box, this field is hard coded to map to a company.

    However, you can map any Jira field with a company value or build a transformation for any other field to set the company value. You must set the field to a value that matches the company created in BMC Helix Multi-Cloud Service Management and Remedy ITSM.

    Description Issue Description
    Customer First and Last Name
    Map these fields to the Jira fields that map to users registered in Remedy ITSM. If you do not have fields in Jira that map to Remedy ITSM users, you can add a transformation or hard code the values.
    Status
    For new incidents that are created in the system, hard code this value to New.
    Urgency and Impact Priority
    Incident Type
    By default, this field is set to User Service Restoration.
    Reported Source
    By default, this field is set to Other.
    Vendor
    Select the vendor name tied to this flow. If you are integrating with multiple instances of Jira, set this value to the vendor mapping defined for that instance of Jira.
    Vendor Ticket Properties

    These properties are used by BMC Helix Multi-Cloud Service Management to display Jira data in BMC Remedy with Smart IT.


 Create Change
  • Project
    Enter the name of the projects to query for issues to send to Remedy ITSM.
  • Trigger
    The trigger condition is an example of how to determine for which issue you should create a Remedy ITSM ticket. Update the trigger condition as per your business requirements. You can use any field in your trigger condition. A single issue in Jira can only be related to a single record in Remedy ITSM.

    Note

    If you are also creating Work Order and Incident Requests from Jira, make sure the trigger condition is unique to creating a change.

  • Field mapping
    The default field mappings provided in the flow follow the best practices to map data from a Jira issue to Remedy Change Requests. You can change these mappings as per your business requirements.
    The following values are mapped out-of-the-box:

    Remedy ITSM fieldJira fieldAdditional information
    Priority Priority
    Summary Issue Summary
    Company

    Set this field to your Remedy ITSM company.

    You can map any Jira field with a company value or build a transformation for any other field to set the company value.

    Description Issue Description
    Change ID Label The Change ID is included as a part of the Summary.
    Customer First and Last Name
    Map these fields to the Jira fields that map to users registered in Remedy ITSM. If you do not have fields in Jira that map to Remedy ITSM users, you can add a transformation or hard code the values.
    Status
    Set this to the appropriate status for creating a Change Request using one of the following options: - Hard code this value - Add a transformation to set from a value in Jira - Leave it blank to use the Remedy ITSM status
    Urgency and Impact Priority The default transformation sets the value in Remedy ITSM with the priority from Jira. You can change this transformation as per your business requirements.
    Risk Level
    By default, this value is set to Level 3. You can set this to appropriate value based on the data in the issue.
    Class
    By default, this value is set to Normal. You can set this to the appropriate value based on data in the issue.
    Change Type
    By default, this value is set to Change. You can set this to the appropriate value based on your business requirements.
    Vendor
    Select the vendor name tied to this flow. If you are integrating with multiple instances of Jira, this value should be set to the vendor mapping defined for that instance of Jira.
    Vendor Ticket ID Issue Key
    Vendor Ticket Properties

    These properties are used by BMC Helix Multi-Cloud Service Management to display the Jira data in BMC Remedy with Smart IT.


 Create DevOps Change
  • Trigger
    You need to set a trigger condition for this flow to determine which change requests should be sent to Jira. For example, you can use the following triggers:

    • Categorization fields
    • Assignment of the change
    • Add a custom field as per your requirement

Note

The Create DevOps Change flow is used to send change requests to different instances of Jira and different DevOps vendors like Agile Central. Use the Technology Service mapping to determine the instance and vendor that the change should be sent to. The mapping for this is usually based on a value in the change request, and is done in the flow.

  • Field mapping
    The following values are mapped out-of-the-box:

    Remedy ITSM fieldJira fieldDescription

    Project

    In the Vendor Field Mapping of the Map Vendor definition, the value of Project is set under fields.project.name . By default, project is set to MultiCloud .

    You should change this value to the appropriate project name. If you have a corresponding field in Remedy ITSM for the project name:

    1. Change the project field type to dynamic.
    2. Select the Field ID on the BMC Helix Multi-Cloud Service Managementrecord definition of the field that stores the Remedy ITSM project value.
    3. Define the mapping from the Remedy ITSM value to the Jira value. You can add the transformations to select the appropriate project based on the value received from Remedy ITSM.
    Priority Priority The Vendor Field Mapping section in the Map Vendor definition defines the transformation from the Remedy ITSM priority field to the Jira priority field. Update the mapping in the flow to update the value transformation from Remedy ITSM to Jira.
    Summary Issue Summary The Change ID is included as a part of the Summary.
    Categorization Tier 3 Issue Type

    In the Vendor Field Mapping of the Map Vendor definition, the value of Issue Type is set under field.issuetype.name for the instance of Jira you are integrating with.

    Jira provides several issue types out of the box and also enables users to create their own custom issue types. There are various options to indicate which issue type should be created.

    The example template uses the Categorization field to decide the issue type. Using the third tier of the change request categorization, we indicate which issue type to create in Jira.

    You can use other fields or transformations to define this. However, the value passed to the Issue Type must match the name of the issue.

    Description Issue Description
    Change ID Label The Change ID is included in the Summary and also added as a label on the issue.


 Create DevOps Incident
  • Trigger
    You need to set a trigger condition for this flow to determine which Incidents should be sent to Jira. For example, you can use the following triggers:
    • Operational or Product Categorization fields in Remedy ITSM
    • Assignment of the incident
    • Add a custom field as per your requirement.

      Note

      The Create DevOps Incident flow can be used to send incidents to different instance of Jira as well as to different DevOps vendors like Agile Central. Use the Technology Service mapping to determine the instance and vendor the incident should be sent to. Usually the mapping is based on a value on the incident, and is defined in the flow.

  • Field mapping

    The following values are mapped out-of-the-box:

    Remedy ITSM fieldJira fieldAdditional information
    Project

    In the Vendor Field Mapping of the Map Vendor definition, the value of Project is set under fields.project.name. By default, project is set to MultiCloud.

    You should change this value to the appropriate project name. If you have a corresponding field in Remedy ITSM for the project name:

    1. Change the project field type to dynamic.
    2. Select the Field ID on the BMC Helix Multi-Cloud Service Managementrecord definition of the field that stores the Remedy ITSM project value.
    3. Define the mapping from the Remedy ITSM value to the Jira value. You can add the transformations to select the appropriate project based on the value received from Remedy ITSM.
    PriorityPriority
    SummaryIssue SummaryThe Incident ID is included as a part of the Summary.
    Resolution Category Tier 3Issue TypeIn the Vendor Field Mapping of the Map Vendor definition, the value of Issue Type is set under field.issuetype.name for the instance of Jira you are integrating with.

    Jira provides several issue types out of the box and also enables users to create their own custom issue types. There are various options to indicate which issue type should be created.

    The example template uses the Categorization field to decide the issue type. Using the third tier of the incident request categorization, we indicate which issue type to create in Jira.

    You can use other fields or transformations to define this. However, the value passed to the Issue Type must match the name of the issue.

    DescriptionDescription
    Incident IDLabelThe Incident ID is included in the Summary and also added as a label on the issue.


 Create DevOps Problem
  • Trigger
    You need to set a trigger condition for this flow to determine which Problems should be sent to Jira. For example, you can use the following triggers:
    • Operational or Product Categorization fields in Remedy ITSM
    • Assignment of the problem
    • Add a custom field as per your requirement.
  • Field mapping

    The following values are mapped out-of-the-box:

    Remedy ITSM fieldJira fieldDescription

    Project

    In the Vendor Field Mapping of the Map Vendor definition, the value of Project is set under fields.project.name. By default, project is set to MultiCloud.

    You should change this value to the appropriate project name. If you have a corresponding field in Remedy ITSM for the project name:

    1. Change the project field type to dynamic.
    2. Select the Field ID on the BMC Helix Multi-Cloud Service Managementrecord definition of the field that stores the Remedy ITSM project value.
    3. Define the mapping from the Remedy ITSM value to the Jira value. You can add the transformations to select the appropriate project based on the value received from Remedy ITSM.
    Priority Priority
    Summary Issue Summary The Problem ID is included as a part of the Summary.
    Category Tier 3 Issue Type In the Vendor Field Mapping of the Map Vendor definition, the value of Issue Type is set under field.issuetype.name for the instance of Jira you are integrating with.

    Jira provides several issue types out of the box and also enables users to create their own custom issue types. There are various options to indicate which issue type should be created.

    The example template uses the Categorization field to decide the issue type. Using the third tier of the problem request categorization, we indicate which issue type to create in Jira.

    You can use other fields or transformations to define this. However, the value passed to the Issue Type must match the name of the issue.

    Description Description
    Problem ID Label The Problem ID is included in the Summary and also added as a label on the issue.


 Create DevOps Work Order
  • Trigger
    You need to set a trigger condition for this flow to determine which Work Orders should be sent to Jira. For example, you can use the following triggers:
    • Operational or Product Categorization fields in Remedy ITSM
    • Assignment of the problem
    • Add a custom field as per your requirement.
  • Field mapping

    The following values are mapped out-of-the-box:

    Remedy ITSM fieldJira fieldDescription

    Project

    In the Vendor Field Mapping of the Map Vendor definition, the value of Project is set under fields.project.name. By default, project is set to MultiCloud.

    You should change this value to the appropriate project name. If you have a corresponding field in Remedy ITSM for the project name:

    1. Change the project field type to dynamic.
    2. Select the Field ID on the BMC Helix Multi-Cloud Service Managementrecord definition of the field that stores the Remedy ITSM project value.
    3. Define the mapping from the Remedy ITSM value to the Jira value. You can add the transformations to select the appropriate project based on the value received from Remedy ITSM.
    Priority Priority
    Summary Issue Summary The Work Order ID is included as a part of the Summary.
    Category Tier 3 Issue Type In the Vendor Field Mapping of the Map Vendor definition, the value of Issue Type is set under field.issuetype.name for the instance of Jira you are integrating with.

    Jira provides several issue types out of the box and also enables users to create their own custom issue types. There are various options to indicate which issue type should be created.

    The example template uses the Categorization field to decide the issue type. Using the third tier of the work order request categorization, we indicate which issue type to create in Jira.

    You can use other fields or transformations to define this. However, the value passed to the Issue Type must match the name of the issue.

    Description Description
    Problem ID Label The Work Order ID is included in the Summary and also added as a label on the issue.


 Create Change Activity Note

  • Trigger
    Ensure that the appropriate project is selected in the Broker Vendor Name list.
  • Field mappings
    • The following out-of-the-box field mappings should not be changed:
      • post_type: comment#vendor
      • ticketNumber: Change ID
      • vendorTicketId: Broker Vendor Ticket Id
      • Attachment Object 1.name: Attachment 1 filename
      • Attachment Object 1.content: Attachment 1
      • Attachment Object 2.name: Attachment 2 filename
      • Attachment Object 2.content: Attachment 2
      • Attachment Object 3.name: Attachment 3 filename
      • Attachment Object 3.content: Attachment 3
    • The following out-of-the-box field mappings can be changed required by your organization. However, it is recommended that you retain the existing values.
      • text: Notes


 Create Incident Activity Note

  • Trigger
    Ensure that Shared with Vendor is set to True.
  • Field mappings
    • The following out-of-the-box field mappings should not be changed:
      • post_type: comment#vendor
      • ticketNumber: Incident Number
      • Attachment Object 1.name: Attachment 1 filename
      • Attachment Object 1.content: Attachment 1
      • Attachment Object 2.name: Attachment 2 filename
      • Attachment Object 2.content: Attachment 2
      • Attachment Object 3.name: Attachment 3 filename
      • Attachment Object 3.content: Attachment 3
    • The following out-of-the-box field mappings can be changed as required by your organization. However, BMC recommends that you retain the existing values.
      • text: Notes


 Create Problem Activity Note with Author

  • Trigger

    Ensure that Broker Vendor Name is set to is not empty.

  • Field mappings

    • The following out-of-the-box field mappings should not be changed:

      • post_type: comment#vendor
      • ticketNumber: Problem ticket
      • Attachment Object 1.name: Attachment 1 filename
      • Attachment Object 1.content: Attachment 1
      • Attachment Object 2.name: Attachment 2 filename
      • Attachment Object 2.content: Attachment 2
      • Attachment Object 3.name: Attachment 3 filename
      • Attachment Object 3.content: Attachment 3
    • The following out-of-the-box field mappings can be changed as required by your organization. However, BMC recommends that you retain the existing values.

      • text


 Create Work Order Activity Note

  • Trigger
    Ensure that the appropriate project is selected in the Broker Vendor Name list.
  • Field mappings
    • The following out-of-the-box field mappings should not be changed:
      • post_type: comment#vendor
      • ticketNumber: Work Order ID
      • ticket_type: workorder
      • vendorTicketId: Broker Vendor Ticket Id
      • Attachment Object 1.name: Attachment 1 filename
      • Attachment Object 1.content: Attachment 1
      • Attachment Object 2.name: Attachment 2 filename
      • Attachment Object 2.content: Attachment 2
      • Attachment Object 3.name: Attachment 3 filename
      • Attachment Object 3.content: Attachment 3
    • The following out-of-the-box field mappings can be changed required by your organization. However, it is recommended that you retain the existing values.
      • text: Notes


 Create Change Activity Note with Author (Remedy 9.1.06 or later)

  • Trigger
    Ensure that the appropriate project is selected in the Broker Vendor Name list.
  • Field mappings
    • The following out-of-the-box field mappings should not be changed:
      • post_type: comment#vendor
      • ticketNumber: Change ID
      • vendorTicketId: Broker Vendor Ticket ID
      • Attachment Object 1.name: Attachment 1 filename
      • Attachment Object 1.content: Attachment 1
      • Attachment Object 2.name: Attachment 2 filename
      • Attachment Object 2.content: Attachment 2
      • Attachment Object 3.name: Attachment 3 filename
      • Attachment Object 3.content: Attachment 3
      • Author: Full name
    • The following out-of-the-box field mappings can be changed as required by your organization. However, it is recommended that you retain the existing values.
      • text: Notes

Note

For more information about using this flow instead of Create Change Activity Note, see Updating flows.


 Create Incident Activity Note with Author (Remedy 9.1.06 or later)

  • Trigger
    Ensure that Shared with Vendor is set to True.
  • Field Mapping
    • The following out-of-the-box field mappings should not be changed:
      • post_type: comment#vendor
      • ticketNumber: Incident Number
      • Author: Full name
      • Attachment Object 1.name: Attachment 1 filename
      • Attachment Object 1.content: Attachment 1
      • Attachment Object 2.name: Attachment 2 filename
      • Attachment Object 2.content: Attachment 2
      • Attachment Object 3.name: Attachment 3 filename
      • Attachment Object 3.content: Attachment 3
    • The following out-of-the-box field mappings can be changed as required by your organization. However, BMC recommends that you retain the existing values.
      • text: Notes


Note

For more information about using this flow instead of Create Incident Activity Note, see Updating flows.


 Create Work Order Activity Note with Author (Remedy 9.1.07 or later)

  • Trigger
    Ensure that the appropriate project is selected in the Broker Vendor Name list.
  • Field mappings
    • The following out-of-the-box field mappings should not be changed:
      • post_type: comment#vendor
      • ticket_type: workorder
      • ticketNumber: Work Order ID
      • vendorTicketId: Broker Vendor Ticket ID
      • Author: Full name
      • Attachment Object 1.name: Attachment 1 filename
      • Attachment Object 1.content: Attachment 1
      • Attachment Object 2.name: Attachment 2 filename
      • Attachment Object 2.content: Attachment 2
      • Attachment Object 3.name: Attachment 3 filename
      • Attachment Object 3.content: Attachment 3
    • The following out-of-the-box field mappings can be changed as required by your organization. However, it is recommended that you retain the existing values.
      • text: Notes


 Sync Jira Issue
  • Trigger
    Retain the values that are available out-of-the-box.
  • Field mapping
    The following out-of-the-box field mappings should not be changed:
    • Vendor: Jira
    • Vendor Ticket Id: Issue Key
    • Vendor Ticket Properties: Retain the out-of-the-box properties mapping.


 Sync Jira Issue Comment
  • Trigger

    Retain the values that are available out-of-the-box.

  • Field mapping

    The following out-of-the-box field mappings should not be changed:

    • text: Retain the prefix Comment Body
    • post_type: comment#remedy
    • Vendor: JIRA
    • Vendor Ticket Id: Issue Key
    • commentId: Comment ID
    • Attachment Object 1: Attachment Object 1
    • Attachment Object 2: Attachment Object 2
    • Attachment Object 3: Attachment Object 3

To define connector targets to enable DevOps between Jira and Remedy ITSM

BMC preconfigures the out-of-the-box Connector Targets for all BMC Helix Multi-Cloud Service Management features. If you want to update the connector configuration or account information, update the Connector Target for the feature.

Warning

Do not delete the out-of-the-box Connector Targets.

  1. To navigate to BMC Helix Platform, in the Configuration Links page, click Configure Connector Targets in Innovation Studio under Required Common Configurations .
    You need to configure the Connector Targets listed for each feature on the Configuration Links page, in addition to the ones listed under Required Common Configuration.
  2. Click the Connector Target you want to configure or click to configure a new Connector Target.
  3. Enter or update the following values and save the configuration.

    FieldDescription
    NameEnter a unique name for the configuration. This name is associated to the process related to the connector you are configuring.
    Connector Type

    Select the connector type from the list. The connectors available to you in BMC Helix Integration Service are provided in the list.

    Configuration

    Based on the connector type selected, the configuration defined for that connector in BMC Helix Integration Studio are listed. Select a configuration from the list.

    ProfileSelect the profile defined for the selected configuration.
  4. You must complete this procedure for all the connector targets listed in the Configuration Links page.

To copy connector processes for each Jira instance 

When you are integrating with multiple instances of Jira, create a copy of the  Connector Process Jira  process for each instance and name them,  Connector Process Jira for <instance name> . Then, complete the following steps for each Jira instance.

Note

Make a note of the instance name and use the same name for your Jira instance when configuring vendor data.

For updating existing connector processes to support problem integration if you are using an older version where it is not enabled by default see, .Configuring support for problem integration when using multiple instances of Jira .

  1. On the Configuration Links page, click Copy processes in Innovation Studio to navigate to BMC Helix Platform for the process configuration.
  2. For each process listed on the Configuration Links page, select it from the Processes list and click Copy. The processes that you need to configure are listed at the end of this section.

    A copy of the process is created, and all the connectors and components of the selected process are displayed.

     Click here to view image...

  3. Enter the name suggested on the Configuration Links page in Name field of the General tab.

  4. Click Save.

You must contact BMC DevOps to setup the connector configuration for the processes that you have created. After saving your updates, complete this procedure for all the Connector Targets listed on the Configuration Links page.

List of connector targets for integration with Jira


 MCSM Remedy ITSM

For the MCSM Remedy ITSM Connector Target, define the connection configuration and profile required by the connector process.


 MCSM JIRA

For the Connector Targets, define the connection configuration and profile required by the connector process in BMC Helix Platform.

When you complete the configuration for all the components,verify the incidents are being brokered from Remedy ITSM to Jira.

To enable mapping between Remedy ITSM fields and custom fields created in Jira

When integrating with Jira, you can send and receive the value of custom fields created in Jira to a field in Remedy ITSM by specifying the appropriate mapping for the fields. After you create the custom field, you need to update the Jira connector, flow and vendor data configuration.

  1. Create the custom field in Jira.
    1. Log in to Jira and add the custom fields that you need. 
    2. Ensure that the custom fields are available on all the screens and issue types that you want to integrate with. 
      For information on adding custom fields, see the documentation for Jira.
  2. Synchronize the Jira connector.
    1. Log in to BMC Helix Integration Studio.
    2. Navigate to Catalog and click Connectors.
    3. Select the Jira connector and click Custom Fields in the Configuration pane.
      You might need to click the arrow on the ribbon in the lower section of the screen to open the Configuration pane.
    4. Select the connector configuration that you want to update for custom fields and click Generate or Re-Generate.
  3. Update the Sync Jira Issue flow to synchronize the new field. 
    1. Get the internal ID from Jira for your custom fields. 

      1. Run echo -n username:password| base64
        to generate base64 encoded string for subsequent requests.

      2. Run wget --no-check-certificate --header='X-Requested-With: XMLHttpRequest' --header='Authorization: Basic [base64 encoded username:password]' --output-document applications.json 'https://[host]/api/v1.0/apps/search?lower_case_name=[connector name]'

        This command creates applications.json file that contains response from the Integration  service. Copy value from id field. This is application Id field that you can use in the next command. Find from the list of appConfig your  configuration by name and copy value from Id field. This is configuration Id value that you can use in next command.

      3. Run wget --no-check-certificate --header='X-Requested-With: XMLHttpRequest' --header='Authorization: Basic [base64 encoded username:password]' --output-document app_triggers.json 'https://[host]/api/v1.0/apps/[application Id]/configs/[configuration Id]/triggers'

        This request creates  app_triggers.json file with available triggers. Each trigger object contains a fields field that is an array of available fields. Copy value from systemName field. Use this value in step f.

      4. Run wget --no-check-certificate --header='X-Requested-With: XMLHttpRequest' --header='Authorization: Basic [base64 encoded username:password]' --output-document app_actions.json 'https://[host]/api/v1.0/apps/[application Id]/configs/[configuration Id]/actions'

        This request creates  app_actions.json  file with available actions. Each action object contains a fields field that is an array of available fields. Copy the value of systemName field. These fields can be used as Vendor field mapping properties.

    2. Log in to BMC Helix Integration Studio.

    3. Navigate to My Flows and select Sync Jira Issue flow.
    4. In the Details tab, click Field Mapping, locate Vendor Ticket Properties.
    5. Click Add Property for each field that you want to use. 
    6. Enter the systemName field and select the field in which the value of the custom field needs to be populated.
  4. To display the custom field, update the Display Mapping in the Vendor Data configuration.

    1. Log in to BMC Helix Multi-Cloud Service Management and click Settings .

    2. Navigate to Configure Vendors > Map Vendors.

    3. Select the Jira metadata to update and click Edit.

    4. Add new vendor specific values for the custom fields that you need.

      • Vendor Field Mapping defines how BMC Helix Multi-Cloud Service Management maps Remedy ITSM fields to vendor ticket fields. 

         Click here to view image

      • Display Field Mapping defines how vendor ticket fields map to the fields on the BMC Remedy with Smart IT console.

         Click here to view image


        The configuration allows you to send data from the custom Jira field to the Remedy ITSM field mapped in the Vendor Field Mapping.

Related topic

Configuring BMC Helix Multi-Cloud Service Management

Was this page helpful? Yes No Submitting... Thank you

Comments