Skip to content

Releases: netceteragroup/django-DefectDojo

Release helm-2.27.2-nca-ce92a759

15 Nov 09:15
Compare
Choose a tag to compare
fixed the burndown calculation ensure timestamp is used

Release helm-2.28.1-nca1

14 Nov 08:36
Compare
Choose a tag to compare
fixed the burndown calculation function to ignore duplicates and also…

Release helm-2.28.1-nca-f7505d1b

14 Nov 08:31
Compare
Choose a tag to compare
fixed the burndown calculation function to ignore duplicates and also…

Release helm-2.27.2-nca2

14 Nov 08:16
f18e2e2
Compare
Choose a tag to compare
fixed the burndown calculation function to ignore duplicates and also…

Release helm-2.27.2-nca-f18e2e2e

13 Nov 12:58
f18e2e2
Compare
Choose a tag to compare
fixed the burndown calculation function to ignore duplicates and also…

Release helm-2.27.2-nca1

20 Oct 12:22
Compare
Choose a tag to compare
new notifications type: SLA breach combined (per product)

This commit introduces a new type of notifications: SLA breach combined.

The main difference is that notification is produced per product.
Original SLA breach notifications are generated for each applicable
findings. This may result in hundreds of messages (e-mail, slack or
teams messages) for large products. Such alerts are hardly manageable
and in the end not of much use.

With SLA breach combined notifications being enabled a user receives a
message per product with a list of findings which breach their SLA. It
can be summarized in the following manner:

subject: <SLA breach kind> <product type> <product>

body: <product summary> <list of findings>

Release helm-2.27.2-nca-0456bbe1

20 Oct 12:15
Compare
Choose a tag to compare
new notifications type: SLA breach combined (per product)

This commit introduces a new type of notifications: SLA breach combined.

The main difference is that notification is produced per product.
Original SLA breach notifications are generated for each applicable
findings. This may result in hundreds of messages (e-mail, slack or
teams messages) for large products. Such alerts are hardly manageable
and in the end not of much use.

With SLA breach combined notifications being enabled a user receives a
message per product with a list of findings which breach their SLA. It
can be summarized in the following manner:

subject: <SLA breach kind> <product type> <product>

body: <product summary> <list of findings>

Release helm-2.26.4-nca1

27 Sep 14:10
Compare
Choose a tag to compare
new notifications type: SLA breach combined (per product)

This commit introduces a new type of notifications: SLA breach combined.

The main difference is that notification is produced per product.
Original SLA breach notifications are generated for each applicable
findings. This may result in hundreds of messages (e-mail, slack or
teams messages) for large products. Such alerts are hardly manageable
and in the end not of much use.

With SLA breach combined notifications being enabled a user receives a
message per product with a list of findings which breach their SLA. It
can be summarized in the following manner:

subject: <SLA breach kind> <product type> <product>

body: <product summary> <list of findings>

Release helm-2.26.4-nca-0217ed77

27 Sep 14:04
Compare
Choose a tag to compare
new notifications type: SLA breach combined (per product)

This commit introduces a new type of notifications: SLA breach combined.

The main difference is that notification is produced per product.
Original SLA breach notifications are generated for each applicable
findings. This may result in hundreds of messages (e-mail, slack or
teams messages) for large products. Such alerts are hardly manageable
and in the end not of much use.

With SLA breach combined notifications being enabled a user receives a
message per product with a list of findings which breach their SLA. It
can be summarized in the following manner:

subject: <SLA breach kind> <product type> <product>

body: <product summary> <list of findings>

Release helm-sla-combined

08 Sep 16:53
Compare
Choose a tag to compare