Allow Hierarchical Library/Application model about dependency-track HOT 4 CLOSED

Closing issue. Work is partially complete - see 31d9263 . UI support for parent/child projects and components will be in a future release. Refer to #84

from dependency-track.

So if I understand correctly, you'd leave the components functionality in place but the grouping of those components (library in the data model) you'd prefer to have an unrestricted hierarchical relationship instead of a top-level application with a flat component structure?

If this were implemented it would allow an org to use DT in it's current manner (flat relationship) which would allow for an automated upgrade path, as well as more complicated parent-child tracking.

Do you have a vision for the UI? I've always found that web-based hierarchies typically have a lot of usability issues. I would want to stay away from a treeview for example, they're complicated to implement correctly and they're not designed for mobile use.

from dependency-track.

This feature is partially complete in 3.0 31d9263. The concept of 'Application' has changed to 'Project'. A project contains a hierarchy of components. When importing a DC scan, it will be flat. But the object model supports this now. The UI will have to take this into consideration once I start writing it.

from dependency-track.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from dependency-track.