Is your feature request related to a problem?
The built-in Linear destination (and the Linear step in Workflows that wraps it) only exposes four configurable fields: Linear workspace, Team, Title, and Description. There's no way to set the issue's priority, which is a core triage field. People automating Linear issue creation from PostHog (for example, a Workflow with a webhook trigger that turns external alerts into Linear tickets) want the issues to land with a priority already set, plus eventually other native Linear fields like labels, status, and assignee.
Describe the solution you'd like
Expose priority as a configurable input on the Linear destination template, passed through to the issueCreate GraphQL mutation. Ideally extend the same treatment to other commonly-needed Linear fields (labels, status, assignee) over time. Priority in Linear is a small enumerated value (0 = none, 1 = urgent, 2 = high, 3 = medium, 4 = low), so the data side is straightforward; the value of the request is having it surfaced in the destination/Workflow config UI.
Describe alternatives you've considered
- Customizing the Linear destination's source code to add a
priority input: the new input does not appear in the Workflow step config. Workflow function steps render only the global template's inputs_schema and have no source editor, so destination-level customizations aren't reflected there.
- Using a generic HTTP Webhook step to call Linear's GraphQL API directly: this can set priority, but the template parser interprets GraphQL's curly braces as Hog expressions (fails to save with
Invalid template: expected ), got Colon), so the mutation has to be brace-escaped by hand. It also can't reuse the existing Linear OAuth connection, requiring a separately-managed Linear API token in a header.
Additional context
From: https://posthoghelp.zendesk.com/agent/tickets/59667
Debug info
Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019ea994-f662-7a00-89e4-f62a657aa768?t=866
Admin (internal): http://go/adminOrgUS/019c24d9-e5f0-0000-b25c-407221bb8bf4 (project ID 305033)
Is your feature request related to a problem?
The built-in Linear destination (and the Linear step in Workflows that wraps it) only exposes four configurable fields: Linear workspace, Team, Title, and Description. There's no way to set the issue's priority, which is a core triage field. People automating Linear issue creation from PostHog (for example, a Workflow with a webhook trigger that turns external alerts into Linear tickets) want the issues to land with a priority already set, plus eventually other native Linear fields like labels, status, and assignee.
Describe the solution you'd like
Expose
priorityas a configurable input on the Linear destination template, passed through to theissueCreateGraphQL mutation. Ideally extend the same treatment to other commonly-needed Linear fields (labels, status, assignee) over time. Priority in Linear is a small enumerated value (0 = none, 1 = urgent, 2 = high, 3 = medium, 4 = low), so the data side is straightforward; the value of the request is having it surfaced in the destination/Workflow config UI.Describe alternatives you've considered
priorityinput: the new input does not appear in the Workflow step config. Workflow function steps render only the global template'sinputs_schemaand have no source editor, so destination-level customizations aren't reflected there.Invalid template: expected ), got Colon), so the mutation has to be brace-escaped by hand. It also can't reuse the existing Linear OAuth connection, requiring a separately-managed Linear API token in a header.Additional context
From: https://posthoghelp.zendesk.com/agent/tickets/59667
Debug info
Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019ea994-f662-7a00-89e4-f62a657aa768?t=866
Admin (internal): http://go/adminOrgUS/019c24d9-e5f0-0000-b25c-407221bb8bf4 (project ID 305033)