Be informative
When multiple reports are sent to DefectDojo simultaneously from different tools for the same Product, instead of creating a single Engagement and adding all reports to it, separate Engagements are created for each report. This issue only occurs when requests are sent concurrently; if reports are sent with a slight delay, they are properly aggregated into a single Engagement.
All reports share the same Engagement name, and the Engagement should dose not exist in DefectDojo, so it should be created .
Steps to reproduce
Steps to reproduce the behavior:
Send multiple reports from different tools to DefectDojo at the same time, all targeting an Engagement with the same name.
Expected behavior
A clear and concise description of what you expected to happen.
Observe that multiple Engagements are created instead of one single Engagement.
Deployment method (select with an X)
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context (optional)
Add any other context about the problem here.
Be informative
When multiple reports are sent to DefectDojo simultaneously from different tools for the same Product, instead of creating a single Engagement and adding all reports to it, separate Engagements are created for each report. This issue only occurs when requests are sent concurrently; if reports are sent with a slight delay, they are properly aggregated into a single Engagement.
All reports share the same Engagement name, and the Engagement should dose not exist in DefectDojo, so it should be created .
Steps to reproduce
Steps to reproduce the behavior:
Send multiple reports from different tools to DefectDojo at the same time, all targeting an Engagement with the same name.
Expected behavior
A clear and concise description of what you expected to happen.
Observe that multiple Engagements are created instead of one single Engagement.
Deployment method (select with an
X)Screenshots

If applicable, add screenshots to help explain your problem.
Additional context (optional)
Add any other context about the problem here.