Reference of integration between BMC Helix ITSM known errors and Jira issues by using BMC Helix iPaaS
You can integrate BMC Helix ITSM with Jira to create known errors from Jira issues. You can also synchronize comments and data between the known error and issue.
BMC Helix Multi-Cloud Broker, along with BMC Helix iPaaS, powered by Jitterbit provides Create_BMC_Helix_ITSM_known_error_from_Atlassian_Jira_issue.json integration template that you can use to integrate BMC Helix ITSM and 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 BMCHelixITSMKnownErrorAndJiraIssue. 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 updation of Jira issues from BMC Helix ITSM known errors, 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 known errors from Jira issues, synchronizes updates, and shares comments. |
Jira project variables
Project variable | Value |
|---|---|
Jira_Host_URL | 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_Project_Name | Enter the default project name that you want to work on for the BMC Helix ITSM and Jira integration. You can keep this variable blank. In this case, the template uses the JQL query. |
Jira_JQL_Query | Enter the JQL query that specifies for which Jira issues, BMC Helix ITSM known errors should be created and synchronized. For example, if you specify Priority=High, then the Jira issues with High priority are brokered to BMC Helix ITSM. Important: Do not include a project condition in this variable. |
| 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. |
BMC Helix iPaaS project variables
| Project variable | Value |
|---|---|
| MCSM_Host | Enter the BMC Helix Multi-Cloud Broker host URL to which 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 determining 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 incident record. If you use any other field from the incident 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 updated, only if it exists. |
Related topics
Getting started with BMC Helix Multi-Cloud Broker
Creating known errors from Jira issues via BMC Helix iPaaS, powered by Jitterbit
Comments
Log in or register to comment.