Dark mode for the sidebar
Toggle a dark theme directly from your Git-Zen sidebar settings. The preference is saved and takes effect instantly — no page reload needed.
- Live preview on the settings page — flip it and see the change immediately.
- Light mode is the default and completely unchanged for anyone who doesn't opt in.
Live for every customer — no setup required.
Export your Git-Zen configuration
Download a full JSON snapshot of your Git-Zen settings from the sidebar in one click.
Useful for auditing your setup, onboarding new Zendesk instances, or just keeping a backup before
making bulk changes.
- Export Config downloads all user-configurable settings as a JSON file.
- Export Tag Mappings separately exports your full tag ↔ label pairing table.
- Both exports live in the settings panel, below Save and Cancel.
Live for every customer — no setup required.
Re-authorize is now admin-only
When Zendesk OAuth needs to be re-authorized, non-admin agents now see a prompt to contact their
administrator instead of an OAuth popup. This stops agents from accidentally saving their own
limited-scope tokens as the shared connection — a pattern that caused repeated auth failures
in multi-agent teams.
- Dead-token banner, Re-Authorize button, and the OAuth popup are all restricted to Zendesk admins.
- Non-admins see a clear message explaining who to contact.
- Hard guard in the auth function prevents any direct or programmatic bypass.
Live for every customer — no setup required.
Screenshots stay inline in your issues
When a customer pastes a screenshot into a Zendesk ticket, Git-Zen can now carry that image
inline into the new GitHub, GitLab, or Azure DevOps issue body — not banished to a flat
attachments list at the bottom.
- Opt-in setting: "Embed inline images in new issue" in sidebar settings.
- Non-inline file attachments still appear in the appended list as before.
- Works across GitHub, GitLab, and Azure DevOps.
Live for every customer — turn it on in sidebar settings.
No more auth loops from parallel token refreshes
When two server processes tried to refresh the Zendesk OAuth token at the same moment, only one
could win — but the loser was incorrectly marking the token as dead, triggering a cascade
that forced every agent through a re-auth. That loop is fixed.
- Timestamp-based winner detection replaces the previous encrypted-value comparison that silently failed.
- The losing process polls for the winner's write and recovers in ~100–200 ms instead of always waiting 500 ms.
- Disabled and cancelled plans are skipped entirely to avoid filling logs with error spirals.
Live for every customer — no setup required.
Git-Zen for Jira is here
Connect Jira Cloud to Zendesk with the same two-way sync depth as our GitHub, GitLab, Azure DevOps, and Linear integrations.
Support agents create and update Jira issues directly from Zendesk tickets — no Jira seat required.
- One-click Jira issue creation from Zendesk — 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.
Git-Zen for Linear is here
Connect Linear to Zendesk 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 — 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.
Self-hosted GitLab is now supported on the Enterprise plan
Run GitLab on your own infrastructure? Git-Zen now connects to your self-hosted GitLab instance with the same workflow as gitlab.com.
Provide your Base URL, allowlist our outbound IP, and you're live.
- Two-way ticket ↔ issue and comment sync, same as gitlab.com.
- Commits, merge requests, labels, milestones, weight.
- Custom fields, tag/label pairs, role permissions.
- Works with GitLab CE and EE; webhooks reach Git-Zen via your firewall allowlist.
GitHub Enterprise Server (GHE) is now supported on the Enterprise plan
Connect Git-Zen to your on-premise GitHub Enterprise Server. Same workflow as Git-Zen for GitHub.com,
with your Base URL and firewall allowlist configured during onboarding.
- 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.
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.
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.
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.
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
Git-Zen