Linear and Jira
Turn an issue into one ticket in Linear or Jira Cloud, and keep the two in sync until the bug is fixed.
When runs find a problem in your product, Autonomy keeps it as an issue in the project, and links every run that sees it again to the same issue. Linear and Jira Cloud turn that issue into one ticket in your tracker, and keep the two in step for the life of the bug.
What you get
| Event | What happens |
|---|---|
| You click Create in Linear or Create in Jira on an issue (or auto-filing is on) | One ticket is created with the issue's title, details, expected and actual result, environment, and links to the issue and to each run that showed it. |
| A later run sees the same issue | One comment on the ticket: "Seen again. Seen in N runs now." Never a second ticket. |
| A run sees the issue after it was resolved | The issue reopens, and the ticket gets "Seen again after being resolved. Seen in N runs now." |
| You close or cancel the ticket | The issue becomes Resolved. |
| You reopen the ticket | The issue becomes Open again. |
| You delete the ticket | The issue is unlinked, keeps its status, and can be filed again. |
Only status comes back. Assignee, priority, labels and title stay in the tracker. Ignored issues are never changed by the tracker, and a ticket never changes a run or its result.
A ticket shows what the issue page shows. It never contains prompts, AI model details, cost, raw page trees or credentials.
Connect
Each tracker is connected once for the organization. Owners and admins only.
Linear
- Open Organization → Integrations → Linear and sign in to Linear. Tickets and comments are posted by the Autonomy app, not by the person who connected it.
- Choose the teams to share, then choose each project's team.
Status sync from Linear works on its own. There is nothing to add in Linear.
Jira Cloud
- Open Organization → Integrations → Jira and sign in to Jira. Pick the site.
- Choose the Jira projects to share, then choose each project's Jira project. Tickets use the Jira project's Bug issue type, or its first issue type if it has no Bug.
- Set up status sync. In the Status sync row, "Add a webhook in Jira so ticket status changes come back to issues.", click Show setup. It shows a URL and a secret, and Open Jira opens your site's webhooks page.
- In Jira, create a webhook with that URL and secret, tick Issue: updated and Issue: deleted, and save. This needs a Jira administrator.
Without step 4, creating tickets and comments still works; only status changes made in Jira don't come back. Reconnecting Jira keeps the same secret, so the webhook keeps working.
Choose where tickets go
Tickets go to the destination of the issue's project:
- Linear: a team.
- Jira: a Jira project.
Choose it in either place:
- Organization → Integrations → Linear or Jira: a table of every project and its team or Jira project. Choose Not used for a project that shouldn't file there.
- The project's Settings → Integrations: the Linear and Jira rows.
Choosing a destination needs an owner or admin. If an environment had its own team or Jira project before projects existed, it keeps it: tickets from that environment's issues still go there.
Create a ticket from an issue
- Open the issue on the project's Issues page.
- Under Linked tickets, click Create in Linear · TEAM or Create in Jira · KEY.
The ticket appears under Linked tickets with its status. If the project has no destination yet, the row says so and admins get a link to choose one in project settings.
You can also paste a link to an existing ticket with Link a ticket. A pasted link is for reference only: it hides that tracker's Create button, and its status doesn't sync.
File tickets automatically
By default nothing is filed until someone clicks Create. To file without anyone clicking:
- Open the project's Settings → Integrations.
- Turn on File tickets for new bugs automatically, under the Jira row.
"When a run finds a new bug, a ticket is created in the team or project above. Off by default: otherwise someone creates it from the issue." The switch needs a Linear team or Jira project first ("Choose a Linear team or Jira project above first."), and only owners and admins can change it.
With it on, each new Bug a run finds becomes a ticket in every connected tracker the project has a destination for. Risks are never filed automatically. A run that sees an existing bug again still only adds a comment. Turn it off and runs keep finding issues; they just aren't filed.
If only some environments file automatically, for example from an older setup, the row says "On for Production and Staging only. Switch it off and on again to use it in every environment."
Troubleshooting
The tracker shows Connect again
The tracker revoked or expired Autonomy's access, for example because the person who connected it left or the app was uninstalled. An admin connects it again; existing ticket links keep working.
Connecting fails
"Couldn't connect Linear: access wasn't allowed." means the sign-in was declined: try again and choose Allow. Otherwise, try again or ask an admin of your Linear or Jira workspace.
There's no Create button on an issue
The project has no team or Jira project for that tracker, or the issue already has a ticket in it, created or pasted. Choose a destination, or remove the pasted link.
Closing the Jira ticket doesn't resolve the issue
Check the webhook in Jira: it must use the exact URL and secret from Status sync, with Issue: updated ticked.
The issue stayed ignored after the ticket was reopened
That's on purpose. An Ignored issue is known and accepted, and the tracker never changes it.
Didn’t find it?