Linear Event Types

This page lists the Linear webhook events that Git-Zen receives and what it does with each one.

Resource types

Resource type	What Git-Zen does
Issue	Reads the gz# reference tags in the description. Adds a comment to each linked ticket and updates the issue details on the ticket.
Comment	Looks up the issue, reads the reference tags in the issue description, and copies the comment to each linked ticket.
IssueLabel	Nothing. Label changes on an issue arrive as Issue updates.

Issue events

A new issue shows as Issue created in the Zendesk comment. A removed issue shows as Issue removed. Each issue comment also shows the team, the issue link, who made the change, the labels, the state, and the priority.

For an Issue update, Linear sends the issue and an updatedFrom object with the fields that changed. Git-Zen names these changes in the Zendesk comment:

Linear field	Comment text
stateId	Issue state changed to …
assigneeId	Issue assigned to …, or unassigned
labelIds	Issue labels updated
priority	Issue priority set to …
title	Issue title changed to …
projectId	Issue moved to project … or Issue removed from project
cycleId	Issue moved to cycle … or Issue removed from cycle

Any other change, such as the due date, estimate, or description, shows as Issue updated.

When stateId changes to a state of type completed or canceled, Git-Zen also applies the closed-issue tags and auto-solve settings.

Comment events

For a Comment event, Git-Zen:

1. Stops if the comment has the Git-Zen watermark. This is a comment that Git-Zen posted from Zendesk.
2. Stops if the comment contains gz#skip.
3. Reads the issue description to find the reference tags.
4. Stops if the comment filters exclude the comment.
5. Adds the comment to each linked ticket, up to 20 tickets.

Linear sends create, update, and remove actions. Git-Zen posts each one with a header: Comment on Linear issue, Comment edited on Linear issue, or Comment deleted on Linear issue. The comment shows the Linear author’s name as text. A deleted comment may arrive without its text. Git-Zen then shows (comment body unavailable).

Events Git-Zen does not receive

The Git-Zen webhook does not subscribe to other Linear resource types, such as projects, cycles, reactions, or attachments.

Check that events arrive

In Linear, open the Git-Zen webhook in the API settings of your workspace. Linear shows recent deliveries and whether Git-Zen accepted them.

If Linear delivers events but tickets do not update, check that:

1. The issue description has the reference tag, for example gz#12345.
2. The issue is in a public team.
3. The ticket is not closed. See Updates to closed tickets.

If you still need help, contact support.