You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Be informative
ZAP Scan reports is not deduplicated in new engagement of same product,
Bug description
A clear and concise description of what the bug is. For errors include at least the exact error message you are seeing (including traceback).
Steps to reproduce
Steps to reproduce the behavior:
Create Engagment. Dedup on Engagment is disable.
Import ZAP_Scan report.(attached)
Create Second engagment. Dedup on Engagment is disable.
Expected behavior
After importing ZAP report to new engagement all findings have been deduplicated
Deployment method(select with an X)
Docker Compose
Kubernetes
GoDojo
Environment information
DefectDojo version v. 2.34.4
Logs
Use docker-compose logs (or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).
Sample scan files
If applicable, add sample scan files to help reproduce your problem.
Screenshots
First import
second import
The text was updated successfully, but these errors were encountered:
Be informative
ZAP Scan reports is not deduplicated in new engagement of same product,
Bug description
A clear and concise description of what the bug is. For errors include at least the exact error message you are seeing (including traceback).
Steps to reproduce
Steps to reproduce the behavior:
some_report.txt
Expected behavior
After importing ZAP report to new engagement all findings have been deduplicated
Deployment method (select with an
X
)Environment information
Logs
Use
docker-compose logs
(or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).Sample scan files
If applicable, add sample scan files to help reproduce your problem.
Screenshots
First import
second import
The text was updated successfully, but these errors were encountered: