Skip to main content
Integrations push Odin’s security findings into the issue tracker your engineers already use, so remediation work sits in the same backlog as everything else. Manage them all from Management > Integrations in the sidebar.

Supported trackers

Odin pushes findings to four trackers. Each has its own connect flow and settings.

Linear

Push findings into a Linear team
https://mintcdn.com/borgresearchas/QG7K8yi1Is1gz_Kz/images/jira-logo.svg?fit=max&auto=format&n=QG7K8yi1Is1gz_Kz&q=85&s=568eb421942944a8069f9140a43a9232

Jira

Push findings into a Jira project

GitHub

Push findings to GitHub Issues

GitLab

Push findings to GitLab Issues
GitHub and GitLab are dual-purpose: they also grant the repository access Mjolnir needs for whitebox pentesting. A connection can provide repository access without issue tracking, so turning on Issue tracking is a separate step on the integration’s card.

How findings reach your tracker

There are three ways a finding becomes an issue in your tracker.
  • Automatically: with Auto-create tickets on, Odin opens an issue as soon as a finding is reported at or above your minimum-severity threshold.
  • Per finding: open any finding and click Push to your tracker. This works whether or not auto-create is on.
  • In bulk: the Sync now banner on the Integrations page creates issues for every finding that doesn’t have one yet.

Syncing existing findings

When you connect a tracker after findings have already been reported, those earlier findings have no external issue. The same gap appears if you turn a tracker on later or push some findings manually and leave the rest. Odin counts these gaps across every fully configured tracker and shows a banner at the top of the Integrations page. The banner has three states:
1

Setup not finished

If you have unsynced findings but no tracker is fully configured yet, the banner tells you how many findings are waiting and prompts you to finish setting up a connection. There’s no sync button until a tracker is ready.
2

Sync now

Once at least one tracker is fully configured, the banner reports how many findings are missing an external issue and shows a Sync now button. Click it to create the outstanding issues across every ready tracker at once.
3

Sync started

After you sync, the banner confirms the jobs are queued. Issues are created in the background and appear in your tracker shortly.
Sync now ignores the Auto-create tickets toggle. If you run trackers in manual mode, you can still use it to backfill issues on demand without turning auto-create on.
A tracker counts as fully configured when its connection is active and its destination is set: a target repository for GitHub, a target project for GitLab, a team for Linear, or a cloud site and project key for Jira. You can dismiss the banner. It stays hidden until the set of trackers with unsynced findings changes, then comes back when a new gap appears.
Odin never closes or reopens issues in your tracker on its own. Status is managed in Odin, while the tracker holds the work item your team picks up.