Automate change management with Jenkins
Changes to Free and Standard plans in Jira Service Management
As of October 16, 2024, change management for Jira Service Management will move from Standard to Premium plans. After this point, only Premium and Enterprise plans will have access to this feature.
Existing service projects in Free and Standard plans will continue to support existing request types and work types. Read more about the plan changes.
Deployment events sent from Jenkins can trigger Jira automation rules, allowing you to automate a wide range of commonly used manual change management steps.
For example, you could automatically:
create, update, or transition change requests
perform risk and impact assessments
trigger approvals and dynamically set approvers based on risk, impact, or affected service
notify stakeholders or end users of changes in real-time, via email, Slack, or Webhook
update a change request when implementation is complete, including whether or not it was successful
Learn more about deployment triggers in Jira Automation.
The Jira Cloud plugin for Jenkins can also help you automate your change management processes using deployment tracking and deployment gating, which can be used separately or in combination within a single Jenkins pipeline.
To begin automating your change management processes with Jenkins, link Jira Service Management with Jenkins.
Was this helpful?