QA TOUCH + LINEAR
Test results in QA Touch, issues in Linear
Create Linear issues straight from a test result, link the ones that already exist, and keep priority, workflow state, assignee and labels in step between QA and engineering.
Three-part setup: API key, connection, project mapping
QA Touch finds the bug. Linear plans the fix.
Connect your Linear account to QA Touch once, map a Linear team and project to each QA Touch project, and your test results and Linear issues can refer to each other.
-
Problem: A failed result has to be re-written as a Linear issue.
With the integration: Add an issue from the test run or result page and it is created in Linear.
-
Problem: The bug already exists in Linear, but nothing connects it to the test.
With the integration: Select existing Linear issues and link them to test results, several at a time.
-
Problem: Engineering changes an issue and QA doesn’t see it.
With the integration: Priority, workflow state, assignee and labels are synced fields.
Issues
Illustrative sample data. The page shows the idea of the sync, not the exact fields QA Touch sends.
What the integration does
Five capabilities from QA Touch’s Linear guide, from the first connection to keeping issues in step.
Connect with a personal API key
Create a key under Account → Security & Access in Linear, then enter it on the Linear tab of Integration Settings. The status shows connected.
Map a team and project
In Project Integration Mapping, pick a Linear team workspace, then a project. Unlink the mapping whenever you need to point at a different project.
Create issues from results
On a test run or result page, click Add Issue, then the Add Bug icon. The issue is created in Linear.
Link existing issues in bulk
Open All Linear Issues, tick several issues and click Link. Mapped Linear Issues lets you unlink an issue or open it in Linear.
Four synced fields
Priority, workflow state, assignee and labels are synced between QA Touch and Linear, and Integration Issues → Linear Issues lets you create, link, edit and review them.
From API key to linked issue
Step through the flow. The screens are schematic, drawn from the labels in the setup guide, not screenshots.
One-time Linear → Settings → Account → Security & Access
Create a personal API key in Linear
In the Personal API keys section, click Create key, enter a name and click Create.
Copy the key when it is created. You enter it in QA Touch next.
QA Touch Administrator → Administration → Integration Settings
Connect Linear in QA Touch
An Administrator opens the Linear tab, enters the key and clicks Submit. The status shows connected.
QA Touch Projects → Project Integration Mapping
Map a Linear team and project
Select a Linear team workspace, select a project and click Submit. To change it later, unlink the current mapping first.
QA Touch Test run or result page → Add Issue
Post an issue from a test result
Click Add Issue, then the Add Bug icon. The issue is created in Linear.
QA Touch More Action → Linear Integration
Link issues that already exist
In All Linear Issues, select one or more issues and click Link. Mapped Linear Issues lists what is linked, with Unlink and View.
Illustrative sample data. Team, project and issue names are examples.
What changes for your QA team
Testing stays in QA Touch. Linear stays where engineering plans. Each can point at the other.
Less duplicate work
Testers add the issue from the result instead of retyping it in Linear, and no second issue is needed when one already exists.
Traceability from test to issue
Linked issues sit against the test results they relate to, so you can see which issue belongs to which failure.
QA sees ownership and state
Assignee, workflow state, priority and labels are synced fields, so QA isn’t left guessing who owns an issue or where it stands.
Link many issues at once
Bulk linking lets you tie several existing Linear issues to results in one go instead of one by one.
Who uses it, and for what
Choose a role to see a scenario the integration supports.
Engineering plans in Linear
The team already works in Linear and wants QA Touch connected before testing starts.
What they do
- Create a personal API key in Linear.
- Enter it on the Linear tab under Administration → Integration Settings.
- Map a Linear team workspace and project to each QA Touch project.
Result: the account is connected and each project has a Linear project to work with.
A checkout test fails
You are working through a test run and one result needs an issue for the team.
What they do
- Click Add Issue on the result, then the Add Bug icon.
- Fill in the details.
- Carry on with the run.
Result: the issue is created in Linear.
The issues were raised before the run
Engineering has already logged several Linear issues that relate to this release's test results.
What they do
- Open More Action → Linear Integration.
- Select the issues in All Linear Issues.
- Click Link.
Result: the issues are mapped to the results in one step, and appear under Mapped Linear Issues.
You work from Linear
You want QA findings in the tool you already plan with.
What they do
- Pick up the issues created from QA Touch.
- Set the assignee, priority, workflow state and labels as usual.
- Let QA review the update.
Result: those four fields are synced, so QA sees the same ownership and state.
Set it up in three parts
These steps follow QA Touch’s guide to the Linear integration: first in Linear, then in QA Touch, then per project.
Before you start
- A Linear account that can open Settings and create personal API keys.
- A QA Touch Administrator login for the global configuration.
- A Linear team and project to map to a QA Touch project.
- Log in to Linear.
- Click your profile icon or workspace name in the upper-left corner and select Settings.
- In the left sidebar, go to Account → Security & Access.
- In the Personal API keys section, click Create key, enter a name and click Create.
- Copy the key.
Keep the key private. The guide doesn't describe what permissions it needs or whether it is tied to one user.
- Log in to QA Touch as an Administrator.
- Go to Administration → Integration Settings and open the Linear tab.
- Enter the key you created.
- Click Submit.
connectedThe status changes to connected when the configuration succeeds.
- Go to Projects → Project Integration Mapping.
- Select a Linear Team Workspace, then a project, and click Submit.
- To change the mapping, click Unlink and map a different project.
- To post an issue, click Add Issue then the Add Bug icon on a test run or result page.
Project mapped? See how an issue reaches Linear.
Questions about the Linear integration
Answers are based on QA Touch’s guide to integrating Linear.
What does the QA Touch Linear integration do?
It connects QA Touch to Linear so you can create Linear issues from test results, link existing Linear issues to results, and sync priority, workflow state, assignee and labels.
How do I connect Linear to QA Touch?
Create a personal API key in Linear under Account → Security & Access. Then, as an Administrator, go to Administration → Integration Settings, open the Linear tab, enter the key and click Submit. The status should show connected.
How do I map a Linear project, and can I change it later?
Go to Projects → Project Integration Mapping, select a Linear team workspace and a project, and click Submit. To change it, click Unlink to remove the current mapping and then map a different project.
How do I create a Linear issue from a test result?
On a test run or result page, click Add Issue and then the Add Bug icon. The issue is created in Linear.
Can I link issues that already exist in Linear?
Yes. Click the More Action icon, choose Linear Integration, select issues in All Linear Issues and click Link. You can link several at once. Under Mapped Linear Issues you can unlink an issue or view it in Linear.
Which fields sync, and in which direction?
Priority, workflow state, assignee and labels are the synced fields, and the guide describes the integration as two-way. It doesn’t say which direction each field syncs in, so test with your own workflow.
How often does it sync, and what permissions does the key need?
The guide doesn’t state a sync frequency, how conflicts are handled, or what permissions the personal API key requires. Ask QA Touch support if that matters for your setup.
Connect Linear to QA Touch
Create your key, connect once, map a Linear project to your first QA Touch project, and post your next issue from a test result.