[JENKINS-58403] Issue marked as new when the issue did exist in a previous build but on a different line

We have an issue which existed for a while, which is logged as which shows the issue is 24 days old:

In the next build, a change has been made to this file which moved this method to a new line, but the method remained unchanged. It is now logged as:

Are the new issues identified by line number or the line of code? The latter would be better as it is not a new issue even though it has moved lines.

This issue is a check style issue but this probably applies to all plugins.

duplicates

JENKINS-6675 Invalid number of new warnings detected

relates to

JENKINS-5935 Improve equals method for warnings

Julie Shamji created issue - 2019-07-09 11:35

Ulli Hafner made changes - 2019-07-10 10:06

Link

New: This issue duplicates JENKINS-6675 [ JENKINS-6675 ]

Ulli Hafner made changes - 2019-07-10 10:07

Link

New: This issue relates to JENKINS-5935 [ JENKINS-5935 ]

Ulli Hafner made changes - 2019-07-10 10:08

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Julie Shamji made changes - 2019-07-10 10:12

Comment

[ This has been marked as a duplicate, Could you tell me which record this is a duplicate of so I can keep track of its progress please? ]

Jenkins