Linear & Jira: Turn Feedback Into Tickets

Both trackers connect with a key you make in the tracker. There is no app to install. A project can have Linear, Jira, or both. Only owners can connect, disconnect or change a tracker; members see “Only the project owner can connect a tracker.”

Connect Linear

1. Make a key in Linear

   In Linear’s settings, create a personal API key. It starts with lin_api_.

2. Check it in Qaid

   Open the project’s Settings, click Trackers, paste the key under Linear and click Validate.

3. Pick the team

   Choose the team new issues go to from Select a team…, then click Connect Linear.

The card then reads Connected and “Issues go to” the team. A bad key fails at Validate with “Could not connect” and the reason, before anything is saved.

Connect Jira

1. Make a token

   Create an API token in your Atlassian account’s security settings.

2. Check it in Qaid

   Under Jira, enter your site address (https://your-site.atlassian.net), the email of your Atlassian account and the token. Click Validate.

3. Pick the project

   Choose the Jira project from Select a project…, then click Connect Jira.

Either key reaches everything its owner can reach in that tracker. Connect with an account whose reach you are happy to share with the project.

Create an issue from one item

Open an item and look under Integrations. Each connected tracker has a button, such as Create Linear Issue. Anyone on the project can use it. When it is done, the button becomes a link to the issue, Linear ENG-42 or similar. An item gets one issue per tracker.

What goes into the issue:

1. Title: a priority and a title Claude wrote, such as [HIGH] Card payment fails at checkout. If Claude doesn’t answer, [MEDIUM] Feedback on and the page path.
2. Description: the page, the time, the message, the element, the console lines, a link to any recording, the screenshot, a link back to the item, and “Claude’s Analysis”.
3. Priority: Linear gets Urgent, High, Medium or Low. Jira gets Highest, High, Medium or Low. If your Jira project rejects the value, the issue is filed without one.
4. Labels, on Jira only: qaid-feedback, the item’s type, a severity, and priority- with the level.

Issues are filed with the key the owner connected, so the tracker shows that person as the author.

Link an item to an existing issue

When the bug already has an issue, click Link existing Linear issue (or Jira) under Integrations and paste the key, ENG-123, or the issue’s address. Qaid looks the issue up first, so a typo links nothing. Unlink takes the link off; the issue stays in the tracker.

Many items can share one issue. The link then says how many, such as 3 reports, in the inbox and on each item. Status changes and comments on the issue reach every item linked to it.

Find a matching issue

Find a matching issue asks Claude whether the item reports the same problem as one of the project’s open linked issues. It only runs when you click it. If it finds one, it says “Looks like ENG-12” with a short reason and offers Attach to ENG-12. It only searches trackers the item is not linked to yet.

On Jira the screenshot arrives as a link rather than a picture, and every issue is a Task, so a Jira project with no Task type turns them all down.

Create issues in bulk

Tick items in the inbox and click Create issues in the bar above the list, then pick the tracker. The button appears once a tracker is connected. A note reports how many were created, skipped and failed. Items that already have an issue in that tracker are skipped.

File escalations automatically

Tick Auto-create an issue when feedback is escalated, either while connecting or later on the tracker’s card. The first time one of your escalation rules flags an item, Qaid files it in every tracker with the box ticked. Keyword rules count too: they flag an item when its message arrives, and the issue follows.

A failed auto-create shows nowhere in the dashboard. If an escalated item has no issue, file it by hand.

Keep status in sync

Sync runs the other way too. The item shows the issue’s status, assignee and priority as the tracker has them. Closing the issue archives the feedback behind it, and reopening the issue brings the feedback back. Each archive or restore adds a note to the item from “Linear sync” or “Jira sync”.

Tracker	Counts as closed
Linear	Any Done or Canceled state
Jira	Any status in the Done category

Notes and comments go both ways. A note added to an item is posted as a comment on its issue, once per issue even when you note many items at once. A comment made in the tracker arrives as a note on every linked item.

When you connect, Qaid tries to add its webhook to the tracker for you. If that works, the card says “Status sync is on”. If it can’t, Qaid tells you why and the card shows the address to add by hand. Linear only lets an admin’s key add webhooks; Jira only lets a site admin. Then:

1. Linear: in the API settings, add a webhook with the address and subscribe it to issue and comment events.
2. Jira: in the system settings, create a webhook with the address and select the issue updated and comment created events.

Tell the reporter

When an issue closes as Done (not Canceled), Qaid records a “fixed” notice for the person behind each linked item. An embed can show it to them later; the notices are kept by the visitor id the embed already sends.

Tick Email the reporter when their issue is done on the tracker’s card to send an email too. It goes only when your app passed the person’s email with the feedback, as user.email or email in the metadata. The email names your project and quotes their message; it never shows the issue. The box is off until you tick it.

Close the issue when the fix merges

Tick Mark the issue done when an AI PR fix for it merges on the tracker’s card. When an AI PR fix is merged on GitHub, Qaid moves the item’s linked issue to Done. The issue’s own webhook then archives the feedback and tells the reporter, as if you had closed it by hand.

The address carries a secret. Anyone holding it can archive and restore this project’s feedback, so treat it like a password. To change it, Disconnect the tracker and connect it again, then give the tracker the new address.

For a Slack ping or your own endpoint instead, see webhooks and Slack. For GitHub, see GitHub issues and AI fixes.