Reviewed/Acknowledged Hotspots from a PR should not be reopened when merged

Description

Current Situation

Developers do an effort to review or acknowledge Security Hotspots raised on Pull Requests. When they do that, they get a PASSED/GREEN Quality Gate. This is great and this is what we expect all the developers to do on PRs to make sure no security-sensitive code is merged.

Today, there is a problem. When the Security Hotspots are merged from the PR to the target Branch, Security Hotspots are reopened and the comments the developer took time to put on the Hotspots are lost.

Expected Behavior

Similar to what is done for Issues, the "issue tracking" should be turned on for Security Hotspots, and statuses and comments should be kept from the PR to the target Branch.

Activity

Not A Bug
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Edition

Community

Components

Priority

Sentry

Created June 27, 2022 at 8:07 AM
Updated December 3, 2024 at 10:25 AM
Resolved November 23, 2022 at 3:44 PM