Git-Zen — What's New https://git-zen.com/new/ New features, improvements, and shipped changes in Git-Zen — the Zendesk integration for GitHub, GitLab, Azure DevOps, and Linear. All updates are live for every customer, no upgrade required. en-us Third South Capital support@git-zen.com (Git-Zen Team) support@git-zen.com (Git-Zen Team) Wed, 22 Apr 2026 00:00:00 +0000 Wed, 22 Apr 2026 00:00:00 +0000 720 https://git-zen.com/images/logo.png Git-Zen — What's New https://git-zen.com/new/ Git-Zen for Jira is here https://git-zen.com/zendesk-jira-integration.html git-zen-2026-04-jira-integration Wed, 22 Apr 2026 00:00:00 +0000 Jira New Integration Git-Zen now bridges Zendesk to Jira Cloud with the same two-way sync depth as our GitHub, GitLab, Azure DevOps, and Linear integrations. Your support agents can create and update Jira issues directly from Zendesk tickets — no Jira seat required.

  • One-click Jira issue creation from Zendesk tickets — set project, labels, priority, assignee, due date, fix version.
  • Two-way comment sync between Zendesk tickets and Jira issues (with regex filters to strip noise).
  • Reference Zendesk tickets from Jira via gz#12345 in any issue comment or description.
  • OAuth 2.0 with refresh tokens — agents stay signed in without hourly re-auth.

Read about Git-Zen for Jira

]]> Git-Zen for Linear is here https://git-zen.com/zendesk-linear-integration.html git-zen-2026-04-linear-integration Wed, 16 Apr 2026 00:00:00 +0000 Linear New Integration Git-Zen now bridges Zendesk to Linear with the same two-way sync depth as our GitHub, GitLab, and Azure DevOps integrations. Your support agents can create and update Linear issues directly from Zendesk tickets — no Linear seat required.

  • One-click Linear issue creation from Zendesk tickets — set team, project, cycle, labels, priority, status, assignee.
  • Two-way comment sync between Zendesk tickets and Linear issues (with regex filters to strip noise).
  • Reference Zendesk tickets from Linear via gz#12345 in any issue comment.
  • Free Lite version lets developers reference tickets without paying.

Read about Git-Zen for Linear

]]> Self-hosted GitLab is now supported on the Enterprise plan https://git-zen.com/self-hosted/ git-zen-2026-04-gitlab-self-hosted Tue, 15 Apr 2026 00:00:00 +0000 GitLab Enterprise Git-Zen Enterprise plan now supports self-hosted GitLab — Community Edition or Enterprise Edition. Configure your instance Base URL during setup, add Git-Zen's outbound IP to your firewall allowlist, and you have the full Git-Zen workflow inside your network.

  • Two-way ticket ↔ issue and comment sync, same as gitlab.com
  • Commits, merge requests, labels, milestones, weight
  • Custom fields, tag/label pairs, role permissions
  • Webhooks reach Git-Zen via your firewall allowlist

Learn about self-hosted Git-Zen

]]> GitHub Enterprise Server (GHE) is now supported on the Enterprise plan https://git-zen.com/self-hosted/ git-zen-2026-04-github-enterprise-server Tue, 15 Apr 2026 00:00:00 +0000 GitHub Enterprise Git-Zen Enterprise plan now supports GitHub Enterprise Server (GHE). Same workflow as our github.com integration, configured to talk to your on-premise instance.

  • Two-way ticket ↔ issue and comment sync
  • Commits, PRs, labels, projects, milestones
  • Custom fields, tag/label pairs, role permissions
  • Outbound webhooks reach your GHE via firewall allowlist

Learn about self-hosted Git-Zen

]]> Route new issues straight into your GitHub roadmap (GitHub Projects V2) https://git-zen.com/new/#github-projects-v2 git-zen-2026-04-github-projects-v2 Mon, 14 Apr 2026 00:00:00 +0000 GitHub Connect synced issues to your GitHub Projects V2 boards automatically. Your roadmap stays accurate without developers having to manually re-file every ticket that comes in from support.

  • Pick a default Projects V2 board in your Git-Zen settings — new issues land there on creation.
  • Set project fields like Status and custom single-select values while the issue is being created.
  • Classic Projects still work if your team hasn't migrated yet — no configuration changes needed.

Read the GitHub Projects V2 docs

]]> Custom issue headers — give developers the ticket context they actually need https://git-zen.com/new/#custom-issue-headers git-zen-2026-04-custom-issue-headers Mon, 14 Apr 2026 00:00:00 +0000 GitHub GitLab Azure DevOps Choose which Zendesk fields land at the top of every synced issue — priority, requester, tags, organization, custom fields — and stop forcing your devs to click back into Zendesk just to find the details they need to triage.

  • Pick and reorder any combination of standard and custom Zendesk fields for the issue body.
  • Works across GitHub, GitLab, and Azure DevOps with a shared configuration.
  • Existing setups keep the previous default header format until you change it.

Read the docs: GitHub · GitLab · works the same on Azure DevOps

]]> Regex sync filters — strip noisy comment content before it reaches your repos https://git-zen.com/new/#regex-sync-filters git-zen-2026-04-regex-sync-filters Mon, 14 Apr 2026 00:00:00 +0000 GitHub GitLab Azure DevOps Define regex patterns that match against comment bodies so internal notes, email signatures, and boilerplate chatter never land on your issues — and the same the other way, so developer-side noise doesn't leak back into Zendesk.

  • Filters run against the comment body only — ticket metadata and other syncs are untouched.
  • Live validation tells you immediately if your regex is malformed.
  • Default is "sync everything" — existing customers see no change until they add a filter.

Read the docs: GitHub · GitLab · works the same on Azure DevOps

]]> Self-serve tag/label pairing — no support ticket required https://git-zen.com/new/#self-serve-tag-label-pairing git-zen-2026-04-self-serve-tag-label-pairing Mon, 14 Apr 2026 00:00:00 +0000 GitHub GitLab Azure DevOps Two-way tag ↔ label sync used to require an email to our support team to configure. Now it lives directly in your Git-Zen settings — set up as many pairings as you need, on your own schedule.

  • Create, edit, and remove bidirectional tag/label pairs from the Git-Zen admin panel.
  • Tags applied in Zendesk propagate to the linked issue — and vice versa.
  • Any existing one-way pairings you had set up continue to work without changes.

Read the docs: GitHub · GitLab · Azure DevOps

]]> Auto-retry on transient failures — no more empty dropdowns when the network hiccups https://git-zen.com/new/#auto-retry-transient-failures git-zen-2026-04-auto-retry-transient-failures Mon, 14 Apr 2026 00:00:00 +0000 Reliability When GitHub, GitLab, or Azure DevOps has a network blip or rate-limit moment, Git-Zen now quietly retries behind the scenes instead of leaving you staring at an empty Repos or Labels dropdown. You'll rarely need to hit refresh again.

  • Automatic retry with backoff on transient failures when fetching repos, labels, projects, and fields.
  • When retries are exhausted, you get a clear error with a one-click retry button instead of a broken UI.
  • Authentication errors still surface immediately — those need you, not a retry.

Live for every customer — no setup required.

]]>