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
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?
Reproduction steps
Set defectDojoEngagementName to meta['namespace']"
Delete all reports from a namespace with several VulnerabilityReports
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
The text was updated successfully, but these errors were encountered:
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.
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?
Reproduction steps
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
The text was updated successfully, but these errors were encountered: