Skip to content

Commit 02ee542

Browse files
committed
added release notes
1 parent 52a4850 commit 02ee542

1 file changed

Lines changed: 25 additions & 0 deletions

File tree

  • docs/content/releases/os_upgrading
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
title: 'Upgrading to DefectDojo Version 2.58.x'
3+
toc_hide: true
4+
weight: -20260504
5+
description: Breaking change: parsers no longer set Finding.service directly
6+
---
7+
8+
## Breaking Change: Parsers No Longer Set `Finding.service`
9+
10+
Starting with DefectDojo 2.58.x, parsers no longer set the `service` field directly on findings.
11+
12+
### Why this is a breaking change
13+
14+
Whenever parsers set the `service` field on findings, this breaks `close_old_findings` functionality.
15+
16+
The reason is that import and reimport differ in a way that import uses the `service` field, however reimport does not include a `service` value. The `close_old_findings` feature only closes findings that match the service value provided in the request. As a result, findings with a non-empty parser-populated service value are not closed.
17+
18+
Also, if the application name changes, findings in the reimport report are no longer matched against existing findings.
19+
20+
### Required actions
21+
22+
- If your integrations relied on parser-populated `service` field, update your workflow to pass service explicitly at import/reimport time when needed.
23+
- Review automation that depends on `close_old_findings` behavior and verify expected closure scope after upgrading.
24+
25+
For more information, check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.58.0).

0 commit comments

Comments
 (0)