Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Duplicated Engagements #71

Open
afagund opened this issue Jul 19, 2024 · 1 comment
Open

[Bug] Duplicated Engagements #71

afagund opened this issue Jul 19, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@afagund
Copy link

afagund commented Jul 19, 2024

Description

We have defectDojoEngagementName set to meta['namespace']". There are times where engagement names get duplicated instead of getting re-used. Is there a way to avoid these duplicates? Is this some sort of race condition?

image

Reproduction steps

  1. Set defectDojoEngagementName to meta['namespace']"
  2. Delete all reports from a namespace with several VulnerabilityReports
  3. Check if there are engagements with same name on DefectDojo

Current Behavior

We see 2 or more engagements with the same name.

Expected Behavior

No more than one engagement with a specific name.

Additional information

No response

@afagund afagund added the bug Something isn't working label Jul 19, 2024
@qsoul
Copy link

qsoul commented Oct 1, 2024

Faced the same behavior. I believe it happens at the moment of the initial export - when there are multiple tests for the same defectDojoEngagementName to export but there is no context (product_type/product/engagement) created yet. At that moment it pushes the first test. Then pushes the second one, but still there is no engagement with such a name created yet, so it creates a duplicate name. All the following test (and re-imports) are pushed to a single same engagement in my case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants