none
Associating Build Number with TFS Work Items after build using vNext RRS feed

  • Question

  • Hi Team,

    We have a requirement of associating work items with TFS Builds. Generally, this is possible (or we can say 'natural') while using XAML Build Templates in TFS (via Integration Build field of WorkItem. In the below screenshot it was mentioned as 'Integrated In'). We are currently trying to migrate from XAML Build Templates to vNext version of VSTFS 2015 and further to integrate with Octopus Deploy for CI/CD practices.


    We are now half the way in the migration because we are stuck up making this vNext templates to associate TFS WorkItems with their Build numbers. Without doing this step, if we complete this migration, it will be difficult to get associated build numbers for each Work Items delivered in that build.

    When we searched MSDN blogs, we got a post (link given below) similar to our requirement but I tried that and ended up with no luck. Search blogs with the tag - 'build-association-with-work-items-in-vnext'

    So, please suggest the ways which can resolve our requirement.

    Thank you,

    Jayganesh Sambath

    Thursday, November 28, 2019 4:34 AM

All replies

  • Hi Jayganesh Sambath,

    Welcome to MSDN forum.

    For your requirement, I found a blog which is about updating the work items with build number during vNext build, hope it could help you.

    https://www.stevefenton.co.uk/2016/10/update-work-items-with-build-number-during-vnext-builds/

    BTW, since the tfs forum is locked, we recommend you could redirect to stackoverflow with tfs and vNext tag, where you could get dedicated support for it.

    Thank you for understanding.

    Best Regards,

    Dylan 


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, November 28, 2019 6:33 AM