{issued}

Linear features

How Issued maps to Linear: team/project routing, default status and labels, Customer Requests, and the appended-at-submit linear_labels field.

Setup

When you create a Linear-backed project in Issued, you configure:

  • Team(required) — the Linear team issues will be created in. This is the equivalent of picking a GitHub repo. You can't change it after creation.
  • Project(recommended) — the Linear project issues will be filed under. Most devs want customer-reported bugs to land in the roadmap for the app or initiative they're building. Editable later.
  • Default status — which workflow state new issues should land in (e.g. Triage, Backlog).
  • Default labels— labels applied to every issue from this project. Always applied; you can't override them per submission — only add more with linear_labels.

Appending labels per submission

The project's default labels are always applied. Add extras per submission with the linear_labels field — useful when you have separate "Bug" and "Feature request" forms that should add different labels on top of the defaults.

js
fields: {
  subject:     { visible: true, required: true },
  description: { visible: true, required: true },
  linear_labels: {
    visible: false,
    // Comma-separated Linear label IDs (not names).
    // Find them in Linear → Team Settings → Labels, or via the Linear API.
    value: "a1b2c3d4-...,e5f6g7h8-..."
  }
}

Note the IDs, not names — Linear's API operates on label IDs.

Customer Requests (Linear-only)

When Customer Requests linking is on (the default), every submission with an email address also upserts a Linear Customer keyed by that email and attaches the issue as a Linear Customer Request. You get per-customer history, prioritization, and rollups in Linear's native UI — the same place Zendesk / Intercom / Front plug into.

Anonymous submissions (no email) skip customer linking automatically. The issue is still created.

If customer upsert failson Linear's side, the issue is still created and the submission completes normally — only the customer link is skipped.

Upsert key is externalId = submitter's email, so repeat submissions from the same person map to the same Linear Customer record over time.

Toggle per-project in the Customer Requests card on the project edit page.

The project detail page shows a stats card with unique customers, linked submissions, and skipped-anonymous counts.

Comment author filter

Not every comment on a Linear issue should go to the customer. Use the project's Comment Author Filter (allow / block lists of Linear actor usernames) to control whose comments become emails.

  • Allow list— if set, only these authors' comments become emails.
  • Block list— these authors' comments never become emails.
  • Works for webhooks from linked agents, bots, and staff alike. Configure in the project settings.

Need finer control on a single comment? Prefix it with (ignore) — see the email replies guide.

Next steps
Connect Linear, create a project, and start routing support.
Create a Linear project →