[chaosk]

Linear and GitHub issues now publish the same ticket.* events. Every event carries one set of ticket keys, whatever the tracker: source, ticket_id, identifier, title, url, project_name, labels, team, and actor_id. A key the tracker has no value for is null. A consumer subscribes once and filters on source; Software Factory already does that for ticket.transitioned.

ticket_id is the tracker's own id. identifier changes when a Linear issue moves to another team or a GitHub repository is renamed; ticket_id does not. A payload carries the ticket as it is after the change, not what changed; a reader reads the ticket for its description or body.

Linear. Until now, everything except a status change or a new comment fell through to ticket_change, which has no handler, so a new Linear issue published nothing.

• ticket.created for an Issue create.
• ticket.updated for an Issue update whose updatedFrom names title, description, labelIds, or projectId. Linear sends an update for every change, including a drag on the board or a priority change; those still publish nothing.
• team is the team's id. Linear can leave out the team object, but always sends teamId.
• A status change still publishes only ticket.transitioned, including when the same update also changes the title.
• ticket.commented adds comment_id and parent_id. A comment's issue has no project or labels, so both are null. A comment on a project or a document publishes nothing.

GitHub. This replaces the issue.opened, issue.edited, and issue.reopened events from #1066, which nothing subscribes to.

• Opening an issue publishes ticket.created. Editing or reopening it publishes ticket.updated: GitHub's open and closed states aren't tracker statuses, because under Software Factory's GitHub tracker the labels are.
• A comment on an issue, from any sender, publishes ticket.commented, with comment_id and a null parent_id. A pull-request comment doesn't. A person's comment still publishes issue.commented for the GitHub chat channel, unchanged.
• project_name is the issue's repository, and team is null.
• issue.labeled also carries issue_id, so Software Factory's label-to-status translation publishes ticket_id.

Jira and the Software Factory board. Their ticket.transitioned adds ticket_id and a null team, so every ticket.transitioned carries the same keys.

The author guide's GitHub section now describes issue.commented, and a new "Tracker events" section lists the ticket.* events and their keys.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
druks	🟢 Ready	View Preview	Nov 4, 2026, 5:50 AM

💡 Tip: Enable Automations to automatically generate PRs for you.