ShivamSharma43 opened a new pull request, #9382: URL: https://github.com/apache/devlake/pull/9382
### Summary The Zentao bug converter set `issues.severity` with `string(rune(toolEntity.Severity))`. Zentao severity is a number from 1 to 4, and `string(rune(3))` is the control character U+0003, not `"3"`. Every Zentao bug got an unreadable control character as its severity. The e2e snapshots even had raw `\x03` bytes in that column, while `_tool_zentao_bugs.csv` has `severity = 3` for the same rows. Changes: - `tasks/shared.go`: new `getSeverity` helper (`strconv.Itoa`), next to `getPriority`, which already formats `pri` as a decimal string. - `tasks/bug_convertor.go`: uses `getSeverity`. - `tasks/shared_test.go`: unit test for `getSeverity`. - `e2e/snapshot_tables/issues_bug.csv`, `issues_bug_for_due_date.csv`: the `\x03` bytes in the severity column are now `3`. No other column changes. (The diff renders the control character as an invisible change.) Stories and tasks don't set severity, so their snapshots are unchanged. No migration: rows are rewritten on the next conversion. ### Does this close any open issues? Closes #9380 ### Screenshots N/A ### Other Information - `go test ./plugins/zentao/tasks/`: pass. The e2e tests need `E2E_DB_URL`, which I didn't run locally. The snapshots match the tool-layer `severity = 3` of the same bugs. - `go vet`, `gofmt` and `golangci-lint run ./plugins/zentao/...`: clean. - The only open PR touching the zentao plugin is #9216, which edits `board_issues_*.csv` only. This PR doesn't touch those files. - Suggested label: `pr-type/bug-fix`. - AI assistance disclosure: this change was prepared with the help of Claude Code (Claude Opus 5.5), and I reviewed the diff. The commit carries a `Generated-by:` trailer per the ASF generative tooling guidance. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
