ShivamSharma43 opened a new issue, #9380: URL: https://github.com/apache/devlake/issues/9380
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened The Zentao bug converter (`plugins/zentao/tasks/bug_convertor.go`) sets the domain `issues.severity` like this: ```go Severity: string(rune(toolEntity.Severity)), ``` `toolEntity.Severity` is the numeric Zentao severity (1 to 4). `string(rune(3))` is the control character U+0003, not `"3"`. Every Zentao bug ends up with an unreadable control character in `issues.severity`, so it can't be shown or filtered on. The e2e snapshots `issues_bug.csv` and `issues_bug_for_due_date.csv` contain raw `\x03` bytes in the severity column. The tool table `_tool_zentao_bugs.csv` has `severity = 3` for the same rows. ### What do you expect to happen `issues.severity` should hold the decimal value (`"3"`), the same way `priority` is built from `pri` with `getPriority` (`fmt.Sprintf("%d", pri)`). ### How to reproduce Collect a Zentao product with bugs, then run `SELECT HEX(severity) FROM issues WHERE id LIKE 'zentao:ZentaoBug:%'`. It returns `03` instead of `33`. ### Anything else Proposed fix (I have a PR ready): convert with `strconv.Itoa` through a small `getSeverity` helper next to `getPriority`, add a unit test, and replace the `\x03` bytes in the two e2e snapshots with `3`. ### Version main ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
