Connect Polaris to GitLab Issues via SCM integration to export issues captured in SAST and SCA tests as GitLab Issues tickets.
Prerequisites and technical requirements
The issue tracking integration for GitLab Issues requires:
- A SaaS-based GitLab project with the Issues feature enabled. Note: GitLab Self-Managed is not supported at this time.
To enable the Issues feature, in the GitLab project sidebar menu, go to , and under the Visibility, project features, permissions heading, select the Issues checkbox.
- A Personal Access Token (PAT) with the
apiscope enabled.See GitLab Tokens for SCM Bulk Integration and/or Monitoring for more information.
CAUTION:If the PAT is under-scoped, the SCM connection test still passes and a scope error will surface at issue export time. - A Polaris Organization Administrator or Organization Application Manager who is also a GitLab Project Owner, Project Maintainer, or user with the configure webhooks permission. Note: A Polaris Application Administrator cannot bulk onboard applications with an SCM integration, but can still manage SCM repository connections and issue tracking integration options. See Roles and permissions for more information.
Issue fields
Polaris creates issues in GitLab Issues with the Issue type. Each issue includes the following fields:
- Title: the format of titles varies, depending on how the ticket was created:
- Tickets for individual issues you export manually (single export):
Polaris - '<Application name>' / '<Project name>' / '<Branch name>' contains issue '<Issue type>' - Tickets created for policy violations:
Polaris - '<Application name>' / '<Project name>' / '<Branch name>' issues violating policy '<Policy name>' - Tickets for multiple issues you export manually (bulk export):
Polaris - '<Application name>' / '<Project name>' / '<Branch name>' vulnerabilities ('<Number of issues>' issues)
- Tickets for individual issues you export manually (single export):
- Description: the format of descriptions varies, depending on how the ticket was created:
- Tickets for issues you export manually: detailed information about the issue, remediation guidance, and a link to the issue in Polaris.
- Tickets created for policy violations: the name of the violated policy, the names of any violated rules, and links you can use to view violating issues in Polaris.
- Author: the user associated with the personal access token used for the integration.
- State: the status of the GitLab Issues ticket depends on the status of the Polaris issues:
openedwhen a GitLab Issues ticket is created by issue export or policy violation in Polaris.closedwhen status synchronization is enabled in Polaris and the linked Polaris issue(s) are dismissed or absent.
Connect a Polaris application to GitLab Issues via SCM bulk onboarding
Polaris returns to the Portfolio page with a loading bar at the top of the screen to indicate the progress of the SCM onboarding. The Portfolio page refreshes again once importing is finished.
Manage GitLab Issues settings for Polaris applications
The Polaris application is now configured with GitLab issue tracking integration.
Connect a Polaris project to GitLab Issues from SCM import
Polaris returns to the application's Projects page with a loading bar at the top of the screen to indicate the progress of the SCM onboarding. This page refreshes again once importing is finished. Issue tracking settings can be configured by following Manage GitLab Issues settings for Polaris projects.
Manage GitLab Issues settings for Polaris projects
The Polaris project is now configured with GitLab issue tracking integration.
Enable issue tracking for individual branches
After connecting a project in Polaris to an issue tracking instance, you can configure issue tracking synchronization (including auto-close) for individual branches.
Before you can enable issue tracking synchronization at the branch level, the project must be configured with a GitLab issue tracking integration via one of the following methods:
- Connect a Polaris application to GitLab Issues via SCM bulk onboarding
- Manage GitLab Issues settings for Polaris applications
- Connect a Polaris project to GitLab Issues from SCM import
- Manage GitLab Issues settings for Polaris projects
By default, issue tracking synchronization is only enabled on the project's default branch. You can enable or disable this setting for individual branches to control which branches participate in issue tracking synchronization. This is useful when you want to track issue resolution across multiple branches (such as feature branches or release branches) or exclude certain branches from the auto-close behavior.
The branch is now included in issue tracking synchronization. When issues linked to GitLab Issues tickets become absent or are dismissed across all synchronized branches, Polaris automatically closes the associated ticket.