Skip to content

Sorting by SLA does not work in some cases since 77d6bdd0 changeΒ #13766

@pna-nca

Description

@pna-nca

Bug description
When a product has an SLA profile assigned which defines certain expiration days for certain vulnerabilities, SLA counter starts. Some findings may expire, some may not. It is important to have those which close to expiration sorted on top.

This worked previously (although, on client side).

After change the 77d6bdd , sorting the list of open findings in a product view ( defectdojo.host/product/{ID}/finding/open?o=sla_age_days ) does not work anymore.

However:

  • in some cases it works;
  • clicking SLA column changes the order of findings, but the pattern is unclear.

Steps to reproduce
Unfortunately, the main problem is to define the situation when the sorting breaks.

In our case, we have some products where it works, and some where it does not.

Can you advice on what to look for to provide you with more information? Which product or finding properties are essential for SLA sorting?

Expected behavior
List of open findings in product view can be sorted by SLA counter.

Deployment method (select with an X)

  • Docker Compose
  • Kubernetes
  • GoDojo

Environment information
DefectDojo: 2.52.2
Helm chart: 1.8.2

Logs
N/A

Sample scan files
N/A

Screenshots
Sorting by SLA:
Image

Additional context (optional)
N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions