Hey @Mada_B, it seems there might be a few different issues at play here! Let’s go one by one:
1. Security Hotspots were reopened after review
We have seen some users experience this in the past because of an incomplete analysis (for example a shallow checkout or non-clean build) which temporarily closes existing hotspots and then re-creates them in a later full analysis, losing the previous review state. To try to understand if this was the case, could you go to Project > Activity > Measures for the affected branch > check for sudden dips/spikes in Lines of Code, Issues, or Security Hotspots around June 17?
2. Security findings appear inconsistent
There is no inconsistency here. Vulnerabilities and Security hotspots are different things. And by the way, we will soon decommission hotspots in favor of vulnerabilities (although no action has been taken yet, so in principle I have no reason to suspect your issue is related with this).
3. Previously fixed issues are being reported again
The same answer I gave for point 1 applies here, could you please do the same check?
4. Issue assignment appears to have been recalculated
I would treat it as the same: issues could have been re-opened by incomplete analysis or missing SCM data (which is related to incorrect issue authorship detection).
5. Issue status actions appear unavailable
6. As project administrators/owners, we are unable to change the status of some Code Smell issues.
7. The “Change” action opens a dialog but contains no available actions and the Apply button remains disabled.
This sounds like a permissions issue. The permission that enables you to change hotspot statuses is “Administer Issues”. Do you have this permission on this project?