Skip to content

AGGREGATE_LATEST_VERSION_CHILDREN in deeper hirachies #6554

Description

@Xenira

Current Behavior

We have projects nested multiple levels deep and want to have the collection projects use AGGREGATE_LATEST_VERSION_CHILDREN.
This works for the deepest level, but all levels above that ignore the contained collection projects as they can not be marked as latest.

In the image i would expect the top level project to have a sum of all non collection projects, as they are all marked as latest.

Image

Steps to Reproduce

  1. Create collection projects multiple levels deep with collection logic AGGREGATE_LATEST_VERSION_CHILDREN
  2. Add a project with vulnerabilities to the lowest level

Expected Behavior

I would expect collection projects to be counted as well.
Not sure if it makes sense to limit to only collection projects with AGGREGATE_LATEST_VERSION_CHILDREN.

I can have a try at implementing this.

Dependency-Track Version

5.x

Browser

Other

Checklist

Metadata

Metadata

Assignees

No one assigned

    Labels

    defectSomething isn't workingp2Non-critical bugs, and features that help organizations to identify and reduce risksize/SSmall effort

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions