Jesús:
(Copy-pasted the ú from a Windows-1252 list so I hope this website doesn’t mess it up…)
Does the file with the new-but-actually-old issues happen to have new code in the same file that was recently committed? I reported an issue (Configure SQ to give more weight to block move info?) where recently-committed code was doing the same thing as older code with issues already raised, such that the hashes of the flagged code matched. The code was inserted in the middle of a method, and it pushed everything else down, so that the SQ analysis got confused about which issue was which, and misaligned them. Therefore, it thought that the new code was an old issue, and so it was like “musical chairs” where the last issue didn’t correspond to any existing issue, and so SQ said it was a new issue – even though the code was actually several years old.