Startrekzky opened a new issue, #6830: URL: https://github.com/apache/incubator-devlake/issues/6830
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened A user reported that the value of incidents `priority` is P2, but shown in `High` in DevLake  ### What do you expect to happen This is based on an early decision to map 'URGENCY' in PagerDuty to 'Priority' in DevLake, but it now seems to be confused here. The logic behind that decision was the values of PagerDuty urgency were more like the values we understood for priorities. But never mind, I think we need to a few changes to address this: - [ ] Convert PagerDuty's issue priority to DevLake's issue priority. Don't capitalize the letters. - [ ] Add a column `urgency` in table.issues. Convert PagerDuty's issue urgency to DevLake's issue urgency. Don't capitalize the letters. - [ ] Update the domain layer schema doc accordingly. ### How to reproduce Install DevLake and collect PagerDuty data. ### Anything else _No response_ ### Version main ### Are you willing to submit PR? - [ ] 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]
