-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins: 1.651.2
tfs-plugin: 5.126.0
Steps to reproduce:
1. Create a VSTS project with a git repository
2. In VSTS project, create a Jenkins Service Hook
3. Create a pull request with an associated work item
4. Wait for the build to be triggered in Jenkins
Expected results:
The associated work item should appear in the UI of the build summary
Actual results:
The work item does not appear (see screenshot)
I also tried including the work item ID in the commit message (#1, in the screenshot below), but that did not have any effect.
- is duplicated by
-
JENKINS-48947 Work items info not include in the changeset log
-
- Resolved
-
Okay, the problem here is, that the Jenkins plugin for (legitimate?) reasons assumes, that the work item list will be sent via the Service Hook. That is why we actually have the GitPullRequestEx class. There are also some hints on the internet (here, there), that this should be the case. In fact, however, there is no sign of such information actually being sent from VSTS to Jenkins. We could probably retrieve that information via the REST API, but I am not sure if that's actually a bug on VSTS' side.