Niklas

Seems like a rather simple thing to fix with an additional `null` / `undefined` check. Question is, how do we handle this? I'm thinking displaying a red, or otherwise highlighted...

The main issue that was blocking this, was performance concerns of traversing project hierarchies, especially when fetching many objects at once (i.e. listing all projects), see #2407. In DT v5,...

Update on the above, we're further tweaking the approach to avoid the need for recursive queries altogether. Details about the approach here: https://github.com/DependencyTrack/hyades/blob/main/docs/architecture/decisions/005-materialize-project-hierarchies.md It is more or less what @mulder999...

> @mulder999 Any subtrees can then be extracted by a join on root_project_id and some filtering. Could you elaborate on the "some filtering" part? What I like about the separate...

Thanks @mulder999 appreciate the example. > If you need the subtree in memory and don't have too many siebling subtrees you are not interested in, this might still be a...

@mulder999 For completeness I have added your suggestion to "considered alternatives" in our docs: https://github.com/DependencyTrack/hyades/blob/main/docs/architecture/decisions/005-materialize-project-hierarchies.md#considered-alternatives

The MVP of simply storing and displaying this data is relatively trivial to do. I'll leave it as "good first issue". It this doesn't get contributed up until shortly before...

Isn't this similar to the deep link to the *Audit Vulnerabilities* tab you get by clicking on one of the *Affected Projects* in the vulnerability details view?

Could add a ⛓️ icon next to the existing dependency tree icon that copies the anchor to the user's clipboard.

This is also a breaking change, so let's include this in the next major version, together with #486.