-
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
Description |
Original:
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. |
New:
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 with only allows Jira-plugin 2.2.1 |
Description |
Original:
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 with only allows Jira-plugin 2.2.1 |
New:
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 |
Sprint | New: 1.0-b07/b08 [ 101 ] |
Priority | Original: Minor [ 4 ] | New: Critical [ 2 ] |