Side by side
The same questions, answered by deployment gating and by a Merge Pilot change policy.
| Topic | Jira Service Management deployment gating | Merge Pilot |
|---|---|---|
| What is held | A deployment. A deployment to a gated environment waits until its change request is approved in Jira Service Management; with GitHub, a declined change request leaves the deployment failed, with a link to the change request. | A merge. GitLab or GitHub keeps the merge request from merging until its change policy is met for the latest commit: an approval rule only Merge Pilot's bot user can meet on GitLab, a required check from Merge Pilot's App on GitHub.Read the docs |
| What opens a change request | A deployment from a connected CI/CD tool to an environment you chose to gate; the change request is created by Jira automation. | A merge request whose change policy makes it a normal or emergency change. Standard changes merge once their checks pass, without a change approval, unless the policy opens one as a record.Read the docs |
| Tools it works with | Bitbucket Pipelines, Jenkins, GitHub (an environment with Jira as its deployment protection rule) and GitLab (a protected environment with a Jira service account as approver, on GitLab Premium or Ultimate). Deployment gating is a Jira Service Management Cloud Premium capability. | GitLab (Premium or Ultimate for the gate) and GitHub (github.com and GitHub Enterprise Server 3.12 and newer). Change approvals go to Jira Cloud, Jira Server or Data Center, or Merge Pilot's built-in tracker.Read the docs |
| How the decision is passed on | You choose the change request statuses that allow and that prevent a deployment (by default Implementing and Declined); Jira Service Management tells the deployment tool which it is. | You choose the Jira statuses that approve and that reject a change approval. Merge Pilot reads the decision from Jira's webhook and sets the gate; a decision counts only when its maker may decide the change, and the author never may.Read the docs |
| What one approval covers | One deployment: each deployment to a gated environment is sent to approvers. | One commit: a new commit needs its own decision and, by default, a fresh change approval; the policy can instead reopen the same Jira issue or keep the approval.Read the docs |
When each fits
Deployment gating
When the moment to control is the release to an environment such as production, and change management already runs in Jira Service Management: deployments from Bitbucket Pipelines, Jenkins, GitHub or GitLab wait for a change request that approvers decide in Jira Service Management.
A Merge Pilot change policy
When the moment to control is the merge into a protected branch on GitLab or GitHub: what a change needs depends on its paths, labels, size, risk and type, a new commit needs a new decision, and security checks are part of the same policy.
Read the docsBoth together
They gate different moments, and both can keep the approval in Jira. Merge Pilot opens its change approvals as issues in the Jira project and issue type you choose, from templates with your fields, links them to the work items, and can move them on when the merge request is merged or closed. Deployment gating can then hold the release that follows.
Read the docsWhat to consider
Merge Pilot sees merge requests on GitLab and GitHub, not deployments. Teams without Jira can keep change approvals in Merge Pilot's built-in tracker.
Read the docsSee it on your own repositories
Ask for a demo on your own GitLab or GitHub repositories.
Sources
What this page says about Jira Service Management comes from Atlassian's documentation:
- Atlassian Support: What is deployment gating?
- Atlassian Support: Set up deployment gating
- Atlassian Support: Use deployment gating with GitHub
- Atlassian Support: Use deployment gating with GitLab
Product details as of November 2026; check the vendor's documentation for changes.
All product names and trademarks belong to their respective owners. Their use here identifies the products and implies no endorsement.
