CodeArts Check code checking service user feedback collection (5)

Author: gentle_zhou

Original link: CodeArts Check code inspection service user feedback collection (5) - Cloud Community - Huawei Cloud


CodeArts Check (formerly CodeCheck) is a self-developed code checking service. Based on Huawei's 30 years of automated source code static inspection technology accumulation and enterprise-level application experience, it provides users with rich inspection capabilities such as code style, general quality and network security risks, comprehensive quality reports, and convenient closed-loop problem processing. Help companies effectively control code quality and help companies succeed: interested partners can experience the service .

5 user voices in this issue:

21. The problem has been assigned a "resolved" status, but why is the problem still displayed in the second scan result?
22. Then I confirm that I don’t want to modify this defect anymore. How can I block the problem?
23. What is the code health indicator on the right side of the repo code warehouse? Is it provided by Check?
24. Can the Check code inspection service support exporting defects?
25. Can relevant personnel be notified of scanned BUGs?

“Listening to customers and taking action to solve their problems is the first step to customer success. That’s why the Voice of the Customer (VoC) is a critical component in driving company-wide delivery of value to customers and customer satisfaction. This includes aiming to gain customer insights, close the customer feedback loop, and prioritize product improvements to make customers successful and satisfied.”

VOC Highlights Series

Collection of voice feedback from users of CodeArts Check code checking service (1) Collection of
voice feedback from users of CodeArts Check code checking service (2) Collection of voice feedback from
users of CodeArts Check code checking service (3) Collection of voice feedback from
users of CodeArts Check code checking service (4)

21. The problem has been assigned a "resolved" status, but why is the problem still displayed in the second scan result?

The user just changed the defect status to "resolved" in the interface, but the defect has not actually been fixed at the code level, and the defect will still be displayed during the next scan.

image.png

22. Then I confirm that I don’t want to modify this defect anymore. How can I block the problem?

As shown in the figure above, select "Ignore problem" in the corresponding defect status.

23. What is the code health indicator on the right side of the repo code warehouse? Is it provided by Check?

It is provided by the Check service; this is a unified indicator that represents the healthy Chengdu represented by the current project, and is related to the impact of alarms, the number of alarms, and the amount of code.

image.png

24. Can the Check code inspection service support exporting defects?

Supports exporting corresponding defects at the task level, project level, and tenant level:

  • task level

    image.png

  • project level

    image.png

  • Tenant level

    image.png

25. Can relevant personnel be notified of scanned BUGs?

For each task, in Settings-Notification Management, you can set the form of service updates or emails, and select the corresponding role or person to accept relevant notifications.

image.png

Guess you like

Origin blog.csdn.net/hwxiaozhi/article/details/133082769