The problem
A customer reports a bug. A support agent escalates it. An engineer creates an MR fixing the issue. The MR moves through review, gets approved, eventually merges to main, and ships in the next release.
Through that whole journey, your support agent has no idea what's happening. To answer the customer's "any update?" email, they have to:
- Find the engineer who took the ticket.
- Slack them: "any progress on TICKET-12345?"
- Wait for a reply (the engineer is in standup / on vacation / has other priorities).
- Translate "yeah the MR's in review, should merge today" into customer-friendly language.
- Email the customer.
- Repeat tomorrow.
Multiplied across dozens of in-flight tickets, this is hours of agent time per week and an annoyed engineering team that hates the constant interruptions.
What Git-Zen does
Once a Zendesk ticket is linked to a GitLab issue (one click in the Git-Zen sidebar) and that issue is referenced in an MR, Git-Zen surfaces MR activity inside the Zendesk ticket automatically:
- MR opened → comment appears on the ticket: "Merge request !456 opened: Fix tag rendering issue."
- MR merged → comment: "Merge request !456 merged into main."
- MR closed without merging → comment: "Merge request !456 closed."
- MR comment posted → surfaces in Zendesk (filterable via regex if you want to strip noise).
Your support agent now has live MR status inside the ticket, no GitLab account required, no Slack ping required. They can answer "any update?" emails directly from the ticket timeline.
Reference tags — the developer side
For developers, the workflow is the standard gz# reference-tag pattern. In a commit message or MR description, drop:
gz#12345— references Zendesk ticket #12345gz#12345 gz#67890— references multiple tickets at once
Git-Zen detects the reference tag, links the MR/commit to the ticket, and starts surfacing activity. No additional configuration required — the tag IS the link.
How to set it up
Install Git-Zen for GitLab from the Zendesk Marketplace
14-day free trial, no credit card required. Connect via OAuth or PAT (PAT guide).
Verify the GitLab webhook is configured
Git-Zen automatically configures the webhook on each GitLab project you select during setup. Verify in your GitLab project's Settings → Webhooks — you should see a Git-Zen webhook with Merge request events, Push events, and Comments enabled.
Use gz# reference tags in your MRs
When opening an MR that fixes a Zendesk-tracked issue, include gz#TICKET in the MR description (or commit message). Git-Zen auto-links and starts surfacing activity in the ticket.
Optional: configure regex sync filters in Git-Zen settings to strip out noise (CI bot comments, code review automated messages) so only meaningful MR comments appear in Zendesk.
Try Git-Zen for GitLab free
14-day free trial — no credit card required. Install from the Zendesk Marketplace.
Install Git-Zen for GitLabRelated
Git-Zen for GitLab overview → · GitLab integration docs → · Zendesk + GitHub Projects V2 → · Zendesk + Azure Boards →