DependencyTrack / DependencyTrack/frontend

Handling of Latest Version for Snapshots

Open
#323 0 comments 0 reactions 0 assignees View on GitHub
in triage
Dominant language
Vue
Stars
171
Forks
250
Avg merge
11h 12m
Merged PRs (30d)
82

Description

### Current Behavior:
Dependency-Track displays a yellow (warning) icon when a component is not the latest version. This icon is also displayed for a snapshot version of a component that is more recent than the "latest version"

![image](https://user-images.githubusercontent.com/4938718/200204012-6502db50-b783-4ec9-b37e-894865265340.png)

### Steps to Reproduce:

This should be easy to reproduce by uploading a BOM from a feature/dev branch of a multi-module maven project... the modules should all then be snapshot versions that will have a later version number than the latest release for the project.

### Expected Behavior:
When latest > release, then do not indicate that the component is out of date. Indicate something else.
Ideally I would like to see an entirely different icon displayed. Per #311... different colour and different shape.

If this could be applied to snapshots generically then it would also capture a use case that I have seen: where project X has component X.Y that is used in project Z. A developer makes changes to X.Y and then "tries out" the snapshot in project Z (possibly X has rubbish tests and Z has excellent tests). Then they do a release of Z forgetting to include a release version of X.Y. Having a unique "version status" icon and being able to sort by "version status" (logged as #322) would make it easy to see when a project has this kind of problem.

## Environment:

- Dependency-Track Version: 4.6.1 (although I tested using 4.7 SNAPHOT due to authentication fix).
- Client Browser: N/A
- Client O/S: N/A

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.