Reference of integration between BMC Helix ITSM change requests and Jira issues by using BMC Helix iPaaS
You can integrate BMC Helix ITSM with Jira to synchronize change requests with Jira issues. When a change request is created in BMC Helix ITSM, a corresponding issue is created in Jira, and the converse is true. You can also synchronize comments and data between the change request and issue.
BMC Helix Multi-Cloud Broker, along with BMC Helix iPaaS, powered by Jitterbit, provides the Sync_BMC_Helix_ITSM_change_request_and_Atlassian_Jira_issue.json integration template that you can use to integrate BMC Helix ITSM with Jira. You configure the integration in BMC Helix Multi-Cloud Broker and deploy the integration template to your BMC Helix iPaaS environment.
List of project variables
The following sections describe the variables that you can update as per your requirements:
BMC Helix iPaaS variables
| Project variable | Value |
|---|---|
| BHIP_API_NAME | The default value of this variable is set to BMCHelixITSMChangeAndJiraIssue. If required, you can change the name. |
| BHIP_API_User_Roles | Specify the organization roles that should have access to the new API. You can add multiple comma separated values. Important: If you do not specify any value, all the organization roles get access to the new API. |
| BHIP_MCSM_API_Profile_Username | The integration template creates an API in BMC Helix iPaaS to handle requests from BMC Helix Multi-Cloud Broker. Enter the user name for the security profile used with the BMC Helix iPaaSAPI for BMC Helix Multi-Cloud Broker. |
| BHIP_MCSM_API_Profile_Password | The integration template creates an API in BMC Helix iPaaS to handle requests from BMC Helix Multi-Cloud Broker. Enter the password for the security profile used with the BMC Helix iPaaSAPI for BMC Helix Multi-Cloud Broker. |
| BHIP_Vendor_API_Profile_Type | The default value is APIKEY. If required, you can change the default value by selecting one of the following supported values:
|
| BHIP_Vendor_API_Profile_Username | Enter the user name for the security profile that you want to use with the vendor API. Important: You need to provide a value for this variable, only if you select the BASIC option in BHIP_Vendor_API_Profile_Type. |
| BHIP_Vendor_API_Profile_Password | Enter the password for the security profile that you want to use with the vendor API. Important: You need to provide a value for this variable, only if you select the BASIC option in BHIP_Vendor_API_Profile_Type. |
| BHIP_Vendor_API_Profile_ApiKey_Name | The default value is apiKey. If required, you can change the default value. |
| BHIP_Host | Enter the BMC Helix iPaaS instance URL where you want to run this project. |
| BHIP_Username | Enter the user name for the BMC Helix iPaaS instance. |
| BHIP_Password | Enter the password for the BMC Helix iPaaS instance. |
Enable_BMC_Helix_To_Vendor_Integration | By default, this variable is set to true. Important: This variable enables the creation of Jira issues from BMC Helix ITSM change requests, synchronizes updates, and shares comments. |
| Enable_Vendor_To_BMC_Helix_Integration | By default, this variable is set to true. Important: This variable enables the creation of BMC Helix ITSM change requests from Jira issues, synchronizes updates, and shares comments. |
Jira project variables
Project variable | Value |
|---|---|
Jira_Host | Enter the host URL of the Jira instance in the following format:
|
Jira_Username | Enter the name of the user accessing Jira. |
Jira_API_Token | Enter the API token for Jira that you created earlier. |
Jira_JQL_Query | Enter the JQL query that decides for which Jira issues, BMC Helix ITSM change requests should be created. For example, if you specify Priority=High, then the Jira issues with High priority are brokered to BMC Helix ITSM. Important:
|
| Jira_Query_Project_Keys | Enter the Jira project key from which you want to filter Jira issues to broker to BMC Helix ITSM. You can add multiple project keys by specifying comma separated values. For example, JiraProject1, JiraProject2, and so on. Important: While adding a value in this variable, make sure that you include the project key specified in the Jira_Create_Issue_Project_Key variable. This enables the synchronization of change requests that are brokered from BMC Helix ITSM to Jira. |
| Jira_Create_Issue_Project_Key | Enter the Jira project key under which you want to create a Jira issue from a BMC Helix ITSM change request. For example, if you specify AB101XYZ as the project key, when a change request is created in BMC Helix ITSM, a corresponding Jira issue is created under the Jira project with the specified key. Important: You can also specify the Jira project key by mapping a BMC Helix Multi-Cloud Broker field that contains the project key with the key field in the target application. To do this, in the MCSM Workflow, you update a transformation by deleting the existing mapping in the key field and then, mapping it with the BMC Helix Multi-Cloud Broker field in the project element. Refer to the following image and perform the steps in the given sequence to map the fields:  |
BMC Helix Multi-Cloud Broker project variables
| Project variable | Value |
|---|---|
| MCSM_Host | Enter the BMC Helix Multi-Cloud Broker host URL to which the Jira issues should be synchronized. |
| MCSM_Username | Enter the user name that enables users to interact with BMC Helix Multi-Cloud Broker. |
| MCSM_Password | Enter the password for the provided username. |
| MCSM_Vendor_Name | For multiple instances of Jira, enter the value in the following format:
The instance name in the format is the name that you entered in the Instance Name field while configuring vendor metadata. |
MCSM_Field_ID_For_Jira_Issue_Type | It is the BMC Helix Multi-Cloud Broker field ID that contains the value for defining the Jira issue type during BMC Helix Multi-Cloud Broker to Jira operations. The default value of this field is 466000053 that is mapped with the Resolution Category Tier 3 field in the change record. If you use any other field from the change record to contain the Jira issue type, enter the ID of that field in this variable. Important: If this variable is blank, by default, a Jira story is created. |
Comments
Log in or register to comment.