Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clone Audit History #66

Closed
Jonas-vdb opened this issue Dec 20, 2021 · 2 comments
Closed

Clone Audit History #66

Jonas-vdb opened this issue Dec 20, 2021 · 2 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@Jonas-vdb
Copy link

Issue - Feature Request
When publishing a new version to Dependency Track of an existing project, the audit history is not cloned. When you add a new version in the UI you have the option to clone various data. Are there properties available to enable this using the Jenkins plugin? (Could be that I overlooked this in the documentation)

image

Use case:
Project v1.0.0 has 15 vulnerabilities. Various audit trails and statuses have been added to the project version. New version Project v1.0.1 is published but all the auditing info needs to be re-added.

Used Versions
Dependency-Track v4.3.6
OWASP Dependency-Track Plugin v4.0.0

@Jonas-vdb Jonas-vdb added the enhancement New feature or request label Dec 20, 2021
@sephiroth-j sephiroth-j added the wontfix This will not be worked on label Jan 8, 2022
@sephiroth-j
Copy link
Member

For cloning, the ID of the project to be cloned is required. In DT there is no predecessor relationship. The DT frontend knows which project to clone because it uses the currently open project. The Jenkins plugin would either need the ID of the project to clone or would have to look up all the versions with the same project name, sort them somehow, and then make the clone call. This would make things too complicated. Therefore, I reject this feature request.

@dormine
Copy link

dormine commented Aug 23, 2023

Can we not just provide the ID of the project we want to clone ? exacly like we provide the ID of the project when we want to push a bom.xml in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants