Jira integration reference
To establish the integration with Jira, you must configure the connectors, flows, and connector targets. You need to set up tenant level configurations. BMC Helix Multi-Cloud Broker provides out-of-the-box mappings and application level configurations required for the integration. After you complete the integration, you can broker tickets from ITSM to Jira, sync Jira ticket details to ITSM and so on. Each flow in the list of flows is essentially a feature that you can use. Depending upon your use case, you might have to configure multiple flows. BMC Helix Multi-Cloud Broker logically chains the flows and connector processes to complete the feature.
The following table lists the sections for the integration details with Jira for different ticket types:
| Ticket type | Reference |
|---|---|
| Incident request | Jira integration reference for incident requests |
| Change request | Jira integration reference for change requests |
| Work order item | Jira integration reference for work order items |
| Problem ticket | Jira integration reference for problem tickets |
| Known error request | Jira integration reference for known error requests |
Related topics
Enabling prebuilt DevOps integration between JIRA Software and BMC Helix ITSM
Comments
Regarding the following sentence:Select the Field ID on the BMC Helix Multi-Cloud Service Management record definition of the field that stores the Remedy ITSM project value.
The BMC Helix Multi-Cloud Service Management has no record definitions. I think it should be on be BMC Helix Ticket Brokering Library record definition.
Hello Christoph Klapetke,
Thank you, for pointing this out. We have corrected the library name.
Regards,
Anushree
Log in or register to comment.