-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Jenkins 2.19 Jira-plugin 2.2.1
-
-
pacific
Downstream builds set to "Update relevant Jira Issues" don't update the JIRA ticket with the build number.
Using fingerprinting, this works in Jenkins 1.631 and Jira-plugin 2.0.2, but not on the latest version of Jenkins which only allows Jira-plugin 2.2.1
[JENKINS-38140] Update relevant Jira issues doesn't work on downstream builds
Jason Davis
added a comment - The break occurred between version 2.1 (working) and 2.2 (feature broken). Rolling back to 2.1 helps with using fingerprints to mark issues from upstream jobs, but then we lose the built-in ability to mark JIRA issues with pipelines. 
I tested with Jenkins 2.30, but assume it would work with 2.19
Jason Davis
added a comment - The break occurred between version 2.1 (working) and 2.2 (feature broken). Rolling back to 2.1 helps with using fingerprints to mark issues from upstream jobs, but then we lose the built-in ability to mark JIRA issues with pipelines.
I tested with Jenkins 2.30, but assume it would work with 2.19 
Anyone happen to know if this is working in current builds of Jenkins? I have 2.25 asnd 2.30 in place with JIRA plugin 2.2.1 and I've noticed that downstream builds that used to rely and mark JIRA issues based on fingerprinted files are no longer marking the issues as they used to. This is a pretty serious problem for my group - we have rollup packages that pull built components and this feature helps announce to folks what's been fixed in those rollup packages.