Bug-tracking system integrations
Last updated: December 30, 2025
To streamline your remediation process, Fluid Attacks integrates with popular bug-tracking systems (BTS). These integrations allow your development teams to manage vulnerabilities within their existing workflows.
While all supported platforms support issue creation, it is important to note that Jira Cloud offers additional capabilities, such as triggering reattacks directly from the ticket, that are not currently available in Azure DevOps or GitLab.
Key capabilities
Issue creation for detected vulnerabilities
All three integrations (Azure DevOps, GitLab, and Jira Cloud) support automatic issue creation from vulnerabilities reported by Fluid Attacks.
- Azure DevOps: Vulnerabilities are generated as Work Items of the “Issue” type. Specific locations or instances of the vulnerability are organized as child tasks.
- GitLab and Jira Cloud: Vulnerabilities are created as standard issues, maintaining a direct link to the findings in the Fluid Attacks platform.
Requesting reattacks
The ability to request a reattack directly from within the BTS is a feature exclusive to Jira Cloud.
- Jira Cloud: Users can click a dedicated Reattack button located directly on the Jira issue linked to a vulnerability.
- Azure DevOps and GitLab: This functionality is not currently supported. Reattacks for these platforms must be managed through the Fluid Attacks platform.
Comparative summary
The table below outlines the specific functional differences between our current integrations:
| Feature | Azure DevOps | GitLab Issues | Jira Cloud |
| Automatic issue creation | ✅ | ✅ | ✅ |
| Request reattacks via issues | ❌ | ❌ | ✅ |