Generating list of changesets and updating work items dating love notes
But sometimes it can be very convenient to change a file straight from the web access, and you can!
Maybe you find a configuration error when logged on a staging environment where you do not have access to Visual Studio.
Not in itself, but in the traceability that this gives us.
Without this, we would have to rely on check-in comments from the developers to understand the reason for a particular change, not always easy when you look at changes that were done a few years back!
In the days of XAML Builds in TFS, the build would rather handily update the work item with the appropriate “Integration Build” value… The good news is, we can handle this in v Next builds using the Team Services REST API for Work Items. You can generate a special token to use for this – so you don’t need to use your actual account. You’ll need to add the following Power Shell script into your code repository, so it is available during the build. Convert]:: To Base64String($token Bytes) $headers = @ [String] $collection Address = "$env: SYSTEM_TEAMFOUNDATIONCOLLECTIONURI" [String] $project = "$env: SYSTEM_TEAMPROJECT" [String] $build Id = "$env: BUILD_BUILDID" [String] $build Number = "$env: BUILD_BUILDNUMBER" Try Catch This script will dynamically obtain the base addresses of your team collection and will get the work items related to the build, and then update the “Integration Build” value.
Along came v Next builds in TFS / Visual Studio Online / Visual Studio Team Services, which solved all of the pain of setting up and maintaining builds, but which also didn’t update the “Integration Build” value on the work items.
To associate a commit with a work item in these scenarios, you can simply enter the ID of the work item with a # in front of it as part of the commit message: Here we associate this commit with the work item with ID 4321.
But a lot of developers like to use other Git tooling, such as Git Extensions, Source Tree or the command line.
NOTE: If your work items are not in the same collection as your code and build, you can still follow along using this alternate Power Shell script. Edit your v Next build and choose the “Variables” section.
param( $Username, $Password ) $token = (":" -f $Username, $Password) $token Bytes = [System. Add a variable named “Vsts Username” with your username and a variable named “Vsts Password” with your newly minted token.
From the product backlog view, we can select multiple work items and the perform different operations on them, as shown below: There are a few shortcut operations for very common tasks such as moving multiple backlog items to a iteration, or assigning them to a team member.
But then you have the Edit selected work item(s) that allows us to set any fields to a new value in one operation.