Import results from third-party tools (limited availability)

• Polaris deduplicates issues captured using the same third-party tool (if you run multiple external analysis tests to import results from Clang into a project, Polaris won't duplicate the same issue found in different external analysis tests that import results from Clang).
• Polaris does not deduplicate issues imported from different third-party tools in the same project (if the same issue is captured in external analysis tests using exports from Clang and Coverity, the issue appears twice on the Issues tab).
• Polaris does not deduplicate issues captured in external analysis tests from issues captured in other test types in the same project (if the same issue is captured in a SAST test run with Polaris and an external analysis test, the issue appears twice on the Issues tab).

Where supported, triage information is included in SAST and SCA issue data imported from third-party tools. Triage information consists of changes to an issue's triage status and the addition of triage comments.

Triage information is displayed in the Issue History panel. Imported issues are attributed to a user in the third-party tool or the "System" user, if user information is unavailable. Polaris does not link usernames in imported triage information to Polaris usernames, even if names or email addresses match.

How is triage status determined?

In SAST and SCA issues imported from third-party tools, the triage status is:

• Mapped from the third-party tool to the equivalent triage status in Polaris.
• Not Triaged if triage information is unavailable to import.

The latest triage status is determined by the most recent triage event that occurred in either Polaris or the third-party tool. This means that older triage events you import from third-party tools may be added to an issue's history, without changing its most recent triage status.

See View issue history for more information about viewing triage and detection history.

In triage events imported from third-party tools, the triage status is mapped from the supported third-party tool to the equivalent status in Polaris. The following tables show the mappings used for each supported third-party tool (a hyphen indicates that an equivalent status value is unavailable or undefined in the third-party tool).