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
Open Integrations
Go to Management > Integrations in the sidebar.
Connect GitLab
Click Connect next to GitLab and authorise the Odin app via GitLab’s OAuth flow.
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.
Notes
- Issues are created in the project you selected during setup
- Odin does not update or close GitLab issues automatically. Status management stays in Odin.
- 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.