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

Project cloning should provide an option to replicate history of metrics #4279

Open
2 tasks done
jimklimov opened this issue Oct 18, 2024 · 0 comments
Open
2 tasks done
Labels
enhancement New feature or request good first issue Good for newcomers p2 Non-critical bugs, and features that help organizations to identify and reduce risk size/S Small effort

Comments

@jimklimov
Copy link

jimklimov commented Oct 18, 2024

Current Behavior

With DT 4.11 and earlier (did not try 4.12 yet), when I clone a project in UI (Add version) or REST API, there are a number of options to clone and re-assign different related aspects such as the history of (manually assigned) vulnerability alert analyses, but no option to copy the history of project metrics (in database terms, the rows of PROJECTMETRICS, possibly PORTFOLIOMETRICS, VULNERABILITYMETRICS, and/or other tables with time-ranges when some metric counts applied).

As a result, the KPI history of the clone starts just when it was cloned, and forgets the quality history of the codebase before that.

Proposed Behavior

Add REST API and UI options to copy metric history if the caller wants to (not by default as this can hog storage space).

When copying, rewrite respective IDs as needed.

Code base investigation might start from where the cloning options are defined:

Checklist

@jimklimov jimklimov added the enhancement New feature or request label Oct 18, 2024
@nscuro nscuro added p2 Non-critical bugs, and features that help organizations to identify and reduce risk good first issue Good for newcomers size/S Small effort labels Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers p2 Non-critical bugs, and features that help organizations to identify and reduce risk size/S Small effort
Projects
None yet
Development

No branches or pull requests

2 participants