Linear & Jira: Turn Feedback Into Tickets

Feedback is only useful once it turns into work. Connect your issue tracker to a project and Qaid can open a Linear or Jira issue straight from a piece of feedback — pre-filled with the message, page, screenshot, console errors, and an AI-written summary — then keep the feedback and the issue in step as the issue moves to done and back.

▶

0:00 / 0:00

Connect a tracker

Open your project's Settings and choose the Trackers tab. Each tracker connects with an API key — no OAuth app to register.

Linear

1. In Linear, open Settings → Security & access (or Settings → API) and create a Personal API key. Copy it — it starts with lin_api_.
2. Back in Qaid, paste the key under Linear and click Validate.
3. Pick the team new issues should land in, then click Connect Linear.

Jira

1. Create an API token at id.atlassian.com → Security → Create and manage API tokens. Copy it.
2. In Qaid, under Jira, enter your site URL (https://your-site.atlassian.net), the email for your Atlassian account, and the API token. Click Validate.
3. Pick the project to file issues under, then click Connect Jira.

Validation checks the credentials by listing your teams/projects before saving, so a bad key is caught immediately. You can connect Linear and Jira to the same project at once.

Create an issue from feedback

Open any feedback item. Under Integrations you'll see a Create Linear Issue / Create Jira Issue button for each connected tracker.

Click it and Qaid builds the issue for you:

• Title & summary written by Claude from the feedback, with a priority prefix.
• Description with the message, page URL, targeted element, console errors, and a link back to the feedback — rendered as rich text in Jira.
• Priority mapped onto the tracker's own field, and labels (qaid-feedback, the feedback type, severity, priority-…) on Jira.

Once created, the button becomes a link to the issue (e.g. Linear ENG-42). Each feedback item gets at most one issue per tracker, so you can't accidentally file duplicates.

Do it in bulk

Select several items in the inbox with the checkboxes, then use the bulk toolbar's Create issues menu to file a Linear or Jira issue for each selected item at once. Items that already have an issue in that tracker are skipped.

Auto-create on escalation

On the connected tracker's card, tick Auto-create an issue when feedback is escalated. From then on, whenever feedback matches one of your escalation rules, Qaid opens an issue in that tracker automatically — no clicking required. (Escalation rules are a Pro feature.)

Keep feedback and issues in sync

Status sync closes the loop the other way: when someone marks the tracker issue Done, Qaid archives the linked feedback; reopen the issue and the feedback comes back. Each change is recorded as an admin note on the feedback.

To turn it on, copy the connection's webhook URL from the Trackers tab and add it in your tracker:

• Linear — Settings → API → Webhooks → New webhook, paste the URL, and subscribe to Issues.
• Jira — Settings → System → Webhooks → Create a webhook, paste the URL, and select the issue updated event.

The URL carries a per-connection secret, so keep it private — anyone with it can post status updates for that project. Rotating it is as simple as disconnecting and reconnecting the tracker.

Good to know

• API keys are stored per project. Only the project owner can connect, disconnect, or change a tracker; any team member can create issues from feedback.
• A key is a full-access token. A Linear personal key and a Jira API token carry your account's access — connect with an account whose reach you're comfortable with, and disconnect to revoke.
• Priority is best-effort on Jira. If your Jira project uses a priority scheme that doesn't accept the mapped value, Qaid files the issue without it rather than failing — the labels still tell you the priority.

Prefer a Slack ping or your own endpoint instead of a tracker? See Webhooks & Slack.