Latest Updates

What's New in Git-Zen

Cleaner tickets, quieter syncs, and fewer things for your team to babysit. Here's what shipped in the latest round of updates — all live for every customer, no upgrade required.

Route new issues straight into your GitHub roadmap

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

Give developers the ticket context they actually need

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

Strip noisy comment content before it reaches your repos

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

Pair Zendesk tags to git labels without opening a support ticket

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

No more empty dropdowns when the network hiccups

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.

Have a feature request of your own?

Every update on this page started as a customer asking for it. If something is missing from your Git-Zen workflow, we want to hear about it — and we ship fast.

  Email Support Browse Documentation