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

To view the documentation for the previous version, select 20.02 from the Product version menu.

Enabling prebuilt integration with Jira Service Desk

You can configure BMC Helix Multi-Cloud Service Management for consolidating your tickets from Atlassian JIRA Software Service Desk to your Remedy IT Service Management (ITSM) or BMC Helix IT Service Management (ITSM) application. After enabling the integration, you can broker tickets from Jira Service Desk to Remedy ITSM and the converse is true. The trigger conditions that you define in BMC Helix Integration Service flows evaluate the criteria for creating Remedy ITSM incidents or Jira Service Desk issues.

Before you begin

Complete all preconfiguration tasks before you configure Jira Service Desk integration.

To select the integration option for Jira Service Desk

  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. From the list of applications, select Workspace > Applications > Multi-Cloud Service Management.
  3. To launch BMC Helix Multi-Cloud Service Management, on the top-right corner of the page, click Visit Deployed Application.

    Tip

    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. Based on how you want to create an incident, select one of the following options and click Done:

    • To create an incident from Jira Service Desk to Remedy ITSM, under Ticket Consolidation, select Jira Service Desk to Remedy incident.

    • To create an issue from Remedy ITSM to Jira Service Desk, under DevOps Integration, select Remedy Incident to Jira Service Desk Request.

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 Service Desk 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 ensures that your vendor is notified about changes to the Remedy ITSM fields by sending updates as a comment to the corresponding vendor ticket.

  1. If you have not already done so, to set up the vendor organizations, on the Configuration Links page, click Manage Vendor Organizations. For instructions, see Performing preconfiguration tasks.

  2. To add or update the vendor mapping, on the Configuration Links page, click Map Vendors.

  3. On the Map Vendors screen, click  to open the Map New Vendor page.

  4. Enter a Description that makes it easy for you to identify the vendor metadata configuration.

  5. Select the Ticketing Technology Provider.
    The Ticketing Technology Provider is the application the vendor uses to manage tickets.

    VendorTicketing Technology Provider
    AmazonAWS
    JIRA SoftwareJIRA
    Salesforce Service CloudService Cloud
    CA Agile CentralAgile Central
    Remedy ITSMVendor Remedy ITSM
    JIRA Software Service DeskJIRA Service Desk
    Microsoft Azure DevopsAzure DevOps
    Azure MonitorAzure Alerts
    IBM QRadarQRadar
    BMC TSOMTrueSight Ops Mgmt for PSR
  6. Click Add Mapping.
    BMC Helix Multi-Cloud Service Management displays the default Instance URL, Vendor Field Mapping and Display Field Mapping.

  7. Update the Instance URL with the ticketing technology provider server and port details.
  8. To add or delete mapped field values, click Click { } to open the JSON editor, and modify Vendor Field Mapping and Display Field Mapping.

    1. If required, update the existing Vendor Field Mapping

      Vendor field mapping defines how BMC Helix Multi-Cloud Service Management maps Remedy ITSM fields to vendor ticket fields.

    2. If required, update the existing Display Field Mapping.

      Display field mapping defines how vendor ticket fields map to the fields on the Smart IT console.

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

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

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

  2. To enter field values, select a 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 list of connectors at the end of this procedure.
  4. To add or update the user account that is used to access the vendor application, click Accounts.

List of connectors for integration with Jira Service Desk


 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
    SiteSelect 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 a Remedy ITSM user account that has permissions to view business service requests and permissions to update incidents, change, or problem requests.


 Multi-Cloud

  • Configuration
    While activating BMC Helix Multi-Cloud Service Management, 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 after you have changed the password for your tenant administrator user account in BMC Helix Innovation Studio.
    For information about changing the user password, see Creating or modifying Person data .


 Jira Service Desk
  • Configuration
FieldValue
NameEnter a name for the connector configuration.
Site

For an on-premises Jira Service Desk instance, select the  site that you created.
OR
For Jira Service Desk instances in the cloud, select  Cloud  as the site.

Jira Server HostnameEnter the name of the Jira Service Desk server.
Jira server PortEnter the port number of the Jira Service Desk server. Use port number 443 for HTTPS protocol.
ProtocolEnter the protocol used by the Jira Service Desk server.
  • Account
    Add the account of a Jira Service Desk user who can view and update Jira Service Desk incidents.


 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 be used for sending error notifications.

To configure flow triggers and field mappings between Remedy ITSM, BMC Helix Multi-Cloud Service Management, and Jira Service Desk

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

  1. To navigate to BMC Helix Integration Service, on 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.

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


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

  7. Click My Flows and select the flow that you created from the flow template.
  8. To verify the target values for the trigger conditions and the field mappings, in the right pane, click Details.

List of flows for integration with Jira Service Desk

 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.

  • 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 Jira 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 Management record 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.
    PriorityPriorityDefault field mapping
    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.

    DescriptionDescriptionDefault field mapping
    Incident IDLabelThe Incident ID is included in the Summary and also added as a label on the issue.
    Technology Service
    The Create DevOps Incident flow can be used to send incidents to other DevOps vendors like Jira. You can use one of the following options:
    • Use the Target Values option and select the Technology Service from the list
    • Use the Source Fields option and map it to one of the existing field from Remedy ITSM, for example, the Service field. Then, you can use the transformation option to map different ITSM Services to different technology services.


 Create Incident from JIRA Service Desk
  • Trigger
    Select your Jira Service Desk project from the drop-down list in Project.
  • Field Mapping
    Retain the values that are available out-of-the-box.


 Sync JIRA Service Desk Issue Comment
  • Trigger
    Select your Jira Service Desk project from the drop-down list in Project .
  • Field Mapping
    Do not change the following out-of-the-box field mappings.

    FieldValue
    textComment Body
    post_typecomment#remedy
    ticket_typeincident
    VendorJIRA Service Desk
    Vendor Ticket Id

    Issue Key

    commentIdComment ID
    AuthorComment Author
    Attachment Object 1Attachment Object 1
    Attachment Object 2Attachment Object 2
    Attachment Object 3Attachment Object 3


 Create Incident Activity Note

  • Trigger

    FieldValue
    Shared with VendorTrue
  • Field Mapping

    Do not change the following out-of-the-box field mappings.

    FieldValue
    post_typecomment#vendor
    ticketNumberIncident Number
    Attachment Object 1.nameAttachment 1 filename
    Attachment Object 1.contentAttachment 1
    Attachment Object 2.nameAttachment 2 filename
    Attachment Object 2.contentAttachment 2
    Attachment Object 3.nameAttachment 3 filename
    Attachment Object 3.contentAttachment 3

    Note

    You can change the out-of-the-box field mapping for the text field. Default value is set to Notes.

    However, BMC recommends that you retain the existing mapping.


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

  • Trigger

    FieldValue
    Shared with VendorTrue
  • Field Mapping

    Do not change the following out-of-the-box field mappings.

    FieldValue
    post_typecomment#vendor
    ticketNumberIncident Number
    AuthorFull name
    Attachment Object 1.nameAttachment 1 filename
    Attachment Object 1.contentAttachment 1
    Attachment Object 2.nameAttachment 2 filename
    Attachment Object 2.contentAttachment 2
    Attachment Object 3.nameAttachment 3 filename
    Attachment Object 3.contentAttachment 3

    Note

    You can change the out-of-the-box field mapping for the text field. Default value is set to Notes.

    However, BMC recommends that you retain the existing mapping.

By default, the Create Incident Activity Note flow is used. Instead of the default flow, if you want to use the Create Incident Activity Note with Author flow, you must make changes to the flow.

For more information about using the flow, see Updating flows.


 Send Error Notification

  • Trigger

    FieldValue
    Flow Target Multi-Cloud
  • Field Mapping

    FieldValue
    To
    Enter the email account that will receive the error notification.
    Subject
    Flow Title
    From
    Note:
    The value of this field is set to Integration Service.
    NA

    Note

    You can change the following out-of-the-box field mappings:

    • Subject
    • From

    However, BMC recommends that you retain the existing mappings.


 Create Jira Service Desk Issue

  • Trigger
    The following trigger conditions are provided out-of-the-box:

    FieldValue
    Condition is${webhookContext.466000228} = "Jira Service Desk"
    Include All Fields istrue
    is Newis true
  • Field Mapping

    • Flow Target 1 (Jira Service Desk)
      The following mappings are provided out-of-the-box:

      FieldValue
      Issue SummarySummary
      LabelsRemedy Incident Number
    • Flow Target 2 (BMC Helix Multi-Cloud Service Management)
      The following mappings are provided out-of-the-box:

      FieldValue
      Status
      Note: The value of this field is set to New.
      NA
      Parent Ticket IdID
      Parent Ticket Type Note: The value of this field is set to Incident.NA
      Vendor Ticket Id(Target 1) Issue Key
      Vendor Ticket Properties
      • fields.summary
      • key
      • fields.status.name
      • fields.issuetype.name
      • (Target 1) Issue Summary
      • (Target 1) Issue Key
      • (Target 1) Status
      • (Target 1) Issue Type
    • Flow Target 3 (Remedy ITSM)
      The following mappings are provided out-of-the-box:

      FieldValue
      Incident NumberRemedy Incident Number
      Broker Vendor NameWebhook Condition Parameter



 Update Jira Service Desk Issue from Multi-Cloud Incident

  • Trigger
    The following trigger conditions are provided out-of-the-box:

    FieldValue
    Condition is${webhookContext.466000243} = "true"
    Include All Fields istrue
    Record Event equalsupdate
    Source ID containsNA
  • Field Mapping

    • Flow Target 1 (BMC Helix Multi-Cloud Service Management)
      The following mappings are provided out-of-the-box:

      FieldValue
      Parent Ticket IdID
    • Flow Target 2 (Jira Service Desk)
      The following mappings are provided out-of-the-box:

      FieldValue
      Issue Key(Target 1) Vendor Ticket Id
      Issue DescriptionDescription
      Issue SummarySummary
    • Flow Target 3 (BMC Helix Multi-Cloud Service Management)
      The following mappings are provided out-of-the-box:

      FieldValue
      incidentNumberRemedy Incident Number
      Sync Vendor Ticketfalse


 Sync Jira Service Desk Issue to Multi-Cloud Incident

Use this flow when you want direct data updates between a Jira Service Desk issue and an incident.

  • Trigger
    The following trigger conditions are provided out-of-the-box:

    FieldValue
    Project isNA
    Is Modifiedis true
    Labels matchesINC
  • Field Mapping

    • Flow Target 1 (BMC Helix Multi-Cloud Service Management)
      The following mappings are provided out-of-the-box:

      FieldValue
      StatusStatus
      Vendor Ticket IdIssue Key
      Vendor Ticket Properties
      • fields.summary
      • key
      • fields.status.name
      • fields.issuetype.name
      • Issue Summary
      • Issue Key
      • Status
      • Issue Type
    • Flow Target 2 (BMC Helix Multi-Cloud Service Management)
      The following mappings are provided out-of-the-box:

      FieldValue
      Issue Key(Target 1) Vendor Ticket Id
      Issue DescriptionDescription
      Issue SummarySummary
    • Flow Target 3 (BMC Helix Multi-Cloud Service Management)
      The following mappings are provided out-of-the-box:

      FieldValue
      incidentNumber(Target 1) Parent Ticket Id
      Summary(Target 1) Issue Summary
      Description(Target 1) Issue Description
      PriorityPriority


To update connector targets for Jira Service Desk integration

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.

    FieldInstructions
    NameEnter a unique name for the configuration.
    The name is associated with the process that is related to the connector you are configuring.
    Connector Type

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

    Configuration

    Select a configuration from the list.

    For example, if you select qradar as the Connector Type, all the configurations that you have made for qradar are displayed in the Configuration list.

    ProfileSelect a profile. For example, if you select qradar as the Connector Type, all the profiles that you have created for qradar are displayed in the Configuration list.

List of connector targets for integration with Jira Service Desk


 Connector Process Remedy ITSM

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


 MCSM JIRA Service Desk

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 that incidents are being brokered from Jira Service Desk to Remedy ITSM.

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

You can send and receive the value of custom fields created in Jira Service Desk from a field in Remedy ITSM by updating the Jira Service Desk connector, flow and vendor data configuration.

  1. Create a custom field in Jira Service Desk.

    1. Log in to Jira Service Desk 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. 

  2. Synchronize the Jira Service Desk connector.

    1. Log in to BMC Helix Integration Studio.

    2. Navigate to Catalog and click Connectors.

    3. Select the Jira Service Desk 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 Service Desk Issue flow to synchronize the new field. 

    1. Get the internal ID from Jira Service Desk 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 from the json file and use it in the application Id field in the next command. Find from the list of appConfig your configuration by name and copy value from the Id field. Use the value that you have copied in the configuration Id field in the 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 the Sync JIRA Service Desk Issue flow.

    4. On 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 Display Mapping in 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 Service Desk metadata that you want to update and click Edit.

    4. Add the vendor specific values, if required, for the custom fields.

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

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

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

To sync the values of mapped fields between Jira Service Desk and Remedy ITSM

You can configure the prebuilt integration between Jira Service Desk and Remedy ITSM to automatically update the values of fields mapped between Jira Service Desk and Remedy ITSM in the applications, instead of adding them as a comment. If you update the value of a mapped field in one application, the value is automatically updated in the other application. For example, after brokering the ticket, the initial value of the Status field in Jira Service Desk and Remedy tickets is In Progress. Now, when you update the status of the Jira Service Desk ticket to Closed, the status of the Remedy ITSM change ticket is automatically updated to the same status.

To update the Jira Service Desk field value when Remedy ITSM field value is changed

You must first map the Remedy ITSM and Jira Service Desk fields that you want to keep in sync in the Jira Service Desk Vendor Field Mapping.  Then, configure the flows required to update the value of the Jira Service Desk fields. 

The following table lists the steps that you must perform to update a Jira Service Desk field value when a Remedy ITSM field value is changed:

ProductSteps

BMC Helix Multi-Cloud Service Management

  1. Log in to BMC Helix Multi-Cloud Service Management.
  2. Click to open the configuration page.
  3. Navigate to Configure Vendors > Map Vendors.
  4. Select the vendor that shows Jira Service Desk as the Ticketing Technology Provider, and click Edit.
  5. Click { } for Vendor Field Mapping and navigate to ticket-brokering-lib:Incident to sync incident data.
  6. Under Remedy to Vendor Sync Fields, add the field IDs of the BMC Helix Multi-Cloud Service Management record definition fields mapped to Jira Service Desk that you want to keep in sync.

BMC Helix Integration Service

  1. Log in to BMC Helix Integration Service.
  2. Create Sync Incident flow from the template.
  3. To sync the value of Remedy ITSM incident and Jira Service Desk fields, create the Update Jira Service Desk Issue from Multi-Cloud Incident flow from the template and map the fields that you want to keep in sync in the flow.

Important: In the flows that you create, ensure that you map the fields that are defined in the Remedy to Vendor Sync Fields  property in the vendor metadata. If you map additional fields in the flow that are not listed in the vendor metadata, the values of these fields are also updated in Jira Service Desk.


To update the Remedy ITSM field value when Jira Service Desk field value is changed

You must first map the Jira Service Desk and Remedy ITSM fields that you want to keep in sync in the Jira Service Desk Vendor Field Mapping.  Then, configure the flows required to update the value of the Remedy ITSM fields. 

The following table lists the steps that you must perform to update a Remedy ITSM field value when a Jira Service Desk field value is changed:

ProductSteps

BMC Helix Multi-Cloud Service Management

  1. Log in to BMC Helix Multi-Cloud Service Management.
  2. Click to open the configuration page.
  3. Navigate to Configure Vendors > Map Vendors.
  4. Select the vendor that shows Jira Service Desk as the Ticketing Technology Provider, and click Edit.
  5. Click { } for Vendor Field Mapping and navigate to Vendor to Remedy Sync Fields.
  6. Add the field IDs of the BMC Helix Multi-Cloud Service Management record definition fields mapped to Jira Service Desk that you want to keep in sync in the Remedy to Vendor Sync Fields section.

BMC Helix Integration Service

  1. Log in to BMC Helix Integration Service.
  2. To sync an incident in Remedy ITSM, create the Sync Jira Service Desk Issue to Multi-Cloud Incident flow.
    This flow brings the update to the Jira Service Desk incident to Multi-Cloud for incident. You must map the fields in the flows that you want to keep in sync.
  3. To sync the value of Remedy ITSM incident and Jira Service Desk fields, create the Update Remedy Incident from Multi-Cloud Incident flow from the template and map the fields that you want to keep in sync in the flow.

Important: In the flows that you create, ensure that you map the fields that are defined in the Remedy to Vendor Sync Fields  property in the vendor metadata. If you map additional fields in the flow that are not listed in the vendor metadata, the values of these fields are also updated in Jira Service Desk.


To store custom field values in Remedy ITSM or Jira Service Desk

By enabling the custom field mapping with Jira Service Desk, you can display the value of custom fields in Smart IT Ticket Details section. However, you can also store the custom field values in Remedy ITSM or Jira Service Desk by modifying the required flow and connector process. To send the custom field values created in Jira Service Desk to Remedy ITSM, perform the following task.

  1. Create the custom field in Jira Service Desk.

    1. Log in to Jira Service Desk 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.

  2. Create similar custom field in Incident record definition in Ticket Brokering Library

    1. Login to BMC Helix Platform. 

    2. Go to Ticket Brokering Library > Incident.

    3. Click + New Field to create a new field.

  3. Create a custom field in Remedy ITSM to store the custom field value from Jira Service Desk.

  4. Synchronize the Jira Service Desk connector.

    1. Log in to BMC Helix Integration Studio.

    2. Navigate to Catalog and click Connectors.

    3. Select the Jira Service Desk 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.

  5. Repeat step 4 for Multi Cloud and Helix Remedy ITSM connector.

  6. Update the Create Incident from Jira Service Desk flow to send the value of the new custom field to Remedy ITSM.

    1. Login to BMC Helix Integration Studio.

    2. To create a flow from Jira Service Desk to Remedy ITSM, if you do not have an existing flow, create Create Incident from Jira Service Desk flow from the template. 

      If you have an existing flow, refresh the schema to populate the Jira Service Desk custom field in the flow mapping.

    3. Open the flow. Go to Details tab and click FIELD MAPPING to display the fields mapped to the flow.

    4. Find the custom field created in Ticket Brokering Library and map it to Jira Service Desk custom field.

  7. Update the Connector Process Remedy ITSM to pass the value to Remedy ITSM.

    1. Login to BMC Helix Platform.

    2. Go to Ticket brokering library > Processes > Connector Process Remedy ITSM.

    3. Select Create Incident block.

    4. In Properties section, click Add/Remove parameters and select the custom field from Remedy ITSM you want to store the value into.

    5. Map the custom field to the field from the Ticket Brokering Library.

    6. Save the connector process.


Related topic

Configuring BMC Helix Multi-Cloud Service Management


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

Comments