Skip to main content
Connect Odin to GitLab to push security findings into your GitLab issue tracker and, optionally, to grant Mjolnir read access to your projects for whitebox pentesting.

​
Connecting

1

Open Integrations

Go to Management > Integrations in the sidebar.
2

Connect GitLab

Click Connect next to GitLab and authorise the Odin app via GitLab’s OAuth flow.
3

Select your project

Choose the GitLab project where issues should be created.

​
Pushing a finding

On any finding, click Push to GitLab. Odin creates a GitLab issue with:
  • Finding title and severity as the issue title
  • Description, reproduction steps, and suggested fix in the issue body
  • A link back to the finding in Odin
You can push multiple findings at once using the bulk action toolbar on the Findings page.

​
Settings

The GitLab integration has a few toggles on the GitLab card in Management > Integrations.
  • Issue tracking: when on, vulnerability findings are tracked as GitLab issues. When off, GitLab is used only for project access (e.g. for Mjolnir whitebox pentesting).
  • Auto-create tickets: when on, GitLab issues are created automatically as new findings are reported. When off, you can still create issues manually from each finding.
  • Minimum severity: only findings at or above this severity trigger automatic issue creation. Defaults to Medium.
Set the minimum severity to High or Critical if you want to keep your GitLab issues focused on the most urgent findings and handle lower-severity issues manually.

​
Customising synced issues

With a target project selected, the Issue customization panel on the GitLab card shapes the issues Odin opens. GitLab supports the shared default assignee and labels: pick a project member to assign every synced issue to, and choose labels to add on top of the ones Odin already applies. Both lists are read from the target project.

​
Status sync

A finding’s status and its linked GitLab issue’s odin:* label stay in sync, in both directions, along with its open/closed state for some statuses. A newly added odin:* label always takes priority over a close/reopen on the same event. Closing or reopening an issue that already carries odin:fixed, odin:acknowledged, or odin:needs-revision is ignored, so it can’t downgrade a Borg-set or Borg-staff-only status.

​
Notes

  • Issues are created in the project you selected during setup
  • You can switch to a different project at any time from the Integrations page
  • Multiple issue trackers can be active at the same time. When you connect a second one (for example GitLab and Linear together), Odin keeps new findings and status changes in sync across all active trackers.