<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=520591) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=520591) </details> <!--IssueSummary end--> ### About A customer reports that after importing projects through Direct Transfer, their burnup/burndown charts are incorrect. The issue count is correct, but issue weight is a flat line. Viewing issues, the weight is shown correctly. When unsetting and resetting issue weight, weight appears in the chart, but manually settings weights for all issues is unfeasible for thousands of issues. This affects all projects imported via Direct Transfer, but does not affect pre-existing or "native" projects that were not imported. The customer states that the time and date on the server are correct with running date or timedatectl. This is a GitLab 17.8.1 self-managed airgapped instance, single-node Omnibus installed via RPM. ### Proposed solution The properties mentioned in https://gitlab.com/gitlab-org/gitlab/-/issues/520591#note_2427184671 are already exported - see `import_export.yml`. Proposal is to export and import `resource_weight_events` as described in George's comment in https://gitlab.com/gitlab-org/gitlab/-/issues/520591#note_2393240550