Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48032

Linked work items do not appear in Jenkin's build summary

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: tfs-plugin
    • Labels:
      None
    • Environment:
      Jenkins: 1.651.2
      tfs-plugin: 5.126.0
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            fbaeuerle Florian Bäuerle added a comment -

            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.

            Show
            fbaeuerle Florian Bäuerle added a comment - 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.

              People

              • Assignee:
                redsolo redsolo
                Reporter:
                pjquirk Patrick Quirk
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: