FlexDeploy provides integration with various Service Management tools for both Change Management and Incident Management
Change Management - Create new change tickets or link to existing change tickets, and bind them to an automated approval for ad-hoc execution or within a pipeline
Incident Management - Automatically create incidents whenever a deployment or pipeline stage fails
Features and Use Cases
The Change Management System integration provides rich features and enables a number of powerful use cases to further integrate and automate the DevOps lifecycle.
Out of the box integrations with a few popular change management systems
Associate existing CMS tickets with deployment requests or pipeline stage executions
Automatically create change tickets (whether for adhoc deployment requests or as part of a pipeline)
Define the ticket fields and map their values to provide context
Bind deployment request approvals or pipeline approvals to the status of the linked ticket(s). Automatic approval in FlexDeploy when the linked ticket in the CMS is approved.
Use one ticket per release, one ticket snapshot, or even one ticket per project/package in the snapshot.
Propagate the ticket numbers across pipeline stages to avoid duplication data entry by users.
Utilize Outgoing Webhooks to automatically create Service Management Incidents when deployments or pipeline stage executions fail.
Deployment report data is tied back to the CMS ticket number for auditing
Framework to include to enable all these features or other CMS Systems via custom integrations.
Change Management System can be viewed from, the Administration → Integrations→ Change Management Systems menu item. There are number of integrations available out of box, or you can define custom change management system.
Terminology
FlexDeploy Term | Description |
|---|---|
Change Management System | Defines the system used to ensure that changes are managed in a cohesive way, ensuring frequent checks and balances around user impact, corporate policies, regulatory compliance, security, etc. and to establish and support the implemented enterprise operational model. ServiceNow, BMC Remedyforce, Freshworks Freshservice, and Jira ITSM are available out of box, but you can add a custom integration using a Java or Groovy implementation. |
Change Management System Instance | Instance represent the physical connection details of the Change Management System. |
Property | Properties are used to define the inputs necessary to connect to the system, |
Topics
If you want to configure ServiceNow, BMC Remedyforce, Freshworks Freshservice, or Jira ITSM, use the Configure Change Management Systems to make any changes to properties or other configurations
For adding a custom change management system, follow the steps described in Custom Change Management System
Once the Change Management System properties are configured, create an instance to integrate with FlexDeploy. Configure Change Management System Instance shows how to set up the instance by providing the server and credential information
The next steps after creating and testing the instance is to Configure Change Management. Here you can choose out of box ServiceNow, BMC Remedyforce, Freshworks Freshservice, Jira ITSM, or any other custom system configured
Change Requests are verified/created when a project is deployed. Associate Change with Deploy describes how FlexDeploy handles the Change
Follow the necessary steps to configure Freshservice, BMC Helix Remedyforce, ServiceNow, or Jira ITSM.