I have just started using a plugin to update JIRA with build status comments. Sometimes it will update a long list of tickets when there should only be one involved.

I think it gets the list from the changes info in Jenkins, it goes wrong when a "changes in dependency" message is displayed which seems to have the wrong last versions.

eg

Job A (builds triggered on SCM change)

• #821 - dependency on Job A #810 to #820
• #822 - no changes in dependency: build failed
• #823 - no changes in dependency
• . . .
• #826 - no changes in dependency
• #827 - dependency on Job A #820 to #826
• #828 - dependency on Job A #826 to #827 
• #829 - no changes in dependency
• #830 - dependency on Job A #827 to #829  
• #831 - no changes in dependency
• . . .
• #837 - no changes in dependency
• #838 - dependency on Job A #829 to #837

There is not a paste error here, Job A is reported to depend on Job A.

It seems to be occasionally deciding it needs to pull some token up to the current build, but I cannot work it out.

I set the component as jira-plugin (from the very extensive list), but I think the problem is in jenkins/svn.

This issue is similar, but not the same as JENKINS-16034.