Managing Jira ticket duplication - Port Swigger

Summary: PortSwigger documentation explains how Burp Suite DAST tracks issues over time, classifying them as new, regressed, repeated, or resolved, and raises Jira tickets automatically based on that classification. It manages tickets per Jira project separately, so two automatic rules targeting the same issue in the same project produce only one ticket, while rules raising the same issue in different projects produce a ticket in each.
Why it matters: Duplicate-ticket logic that runs per project means the same vulnerability can generate tickets across multiple Jira projects while collapsing to one within a single project, so ticket counts are not a reliable measure of how many distinct issues your scanner actually found.

Read the original at PortSwigger Research ↗

Topics: Vulnerabilities & Patching
Related: Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026
U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026
PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026