Autonomy Docs
Integrations

Linear and Jira

Turn a detected bug into one ticket in Linear or Jira Cloud and keep it in sync until the bug is gone.

When a run fails because the product is broken, Autonomy opens a bug note on the Environment and links every run that hits the same failure to it. Linear and Jira Cloud turn that note into one ticket in your tracker — and keep the two in step for the life of the bug.

What you get

EventWhat happens in the tracker
You press Create in Linear / Create in Jira on a bug note (or auto-file is on)One issue is created with the summary, the failing step, occurrence count and a link to each run and to the note.
A later run hits the same bugOne comment: "Seen again. N occurrences now." Never a second ticket.
You close the issue in the trackerThe bug note becomes Resolved.
A run hits the bug again after it was closedThe note reopens and the issue gets a "Seen again after being resolved" comment.
You reopen the issue in the trackerThe note reopens.
You delete the issue in the trackerThe note is unlinked so it can be filed again.

Only status flows back. Assignee, priority, labels and title are never copied onto the note, and a hand-pasted issue link stays reference-only.

The ticket body is evidence-grade: what the user saw, which step, how often, and links. It never contains prompts, model names, raw UI trees or credentials.

Connect

Both trackers connect once per workspace under Settings → Integrations. Connecting requires a workspace admin.

Linear

  1. Settings → Integrations → Linear → Connect Linear and authorize in Linear. Issues and comments are attributed to the Autonomy app, not to the person who connected it.
  2. That is all — status sync back from Linear is built in.

Jira Cloud

  1. Settings → Integrations → Jira → Connect Jira, pick the Jira site, and accept.
  2. Press Webhook setup on the Jira card. It shows a URL and a secret, and links to your site's webhooks page.
  3. In Jira: Settings → System → Webhooks → Create a webhook. Paste the URL and secret, tick Issue: updated and Issue: deleted, save.

Without step 3, creating issues and comments still works; only closing in Jira will not reach the note.

Choose where tickets go

The destination is set per Environment, the first time you create a ticket from one of its bug notes:

  • Linear — a team.
  • Jira — a project and an issue type.

Open a bug note under Environment → Notes, and the Linked issues section shows a picker. Once chosen, every later note in that Environment gets a one-click Create in Linear · TEAM or Create in Jira · KEY / Type button. Change it any time with change team / change project. Choosing a destination requires a workspace admin.

Auto-file new bugs

By default nothing is filed until a human presses the button. To file automatically, open Environment → Settings → Issue trackers and turn on Auto-file new bugs. The toggle is available once the Environment has at least one destination.

With it on, each new bug Autonomy detects in that Environment becomes a ticket in every connected tracker with a destination — with no one clicking anything. Later runs of the same bug still only add a comment. Turn it off and detection keeps opening notes; it just stops filing them.

Troubleshooting

The card says "Connect" again after it was connected

The tracker revoked or expired the token (for example the connecting user was removed, or the app was uninstalled). Press Connect again; existing links keep working after reconnecting.

The Create button shows a team/project picker every time

The destination is stored on the Environment. If it keeps asking, the person choosing is not a workspace admin — ask an admin to pick once.

Closing the Jira issue does not resolve the note

Check the webhook in Jira: it must point at the exact URL from Webhook setup, use that secret, and have Issue: updated ticked. Reconnecting Jira keeps the same secret, so an existing webhook keeps working.

I linked an issue by hand and Create is gone

Any linked issue for a tracker hides that tracker's Create button — the note already has a home. Unlink it to file a fresh ticket.

On this page