Generating list of changesets and updating work items
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!
When using Git repos in TFS, and you use the Git integration in Visual Studio you have the same functionality that lets you associate a work item to a commit, either by using a work item query or by specifying a work item ID.
Stakeholders often include people who just want to track progress or file a bug or a suggestion occasionally.
Buying a CAl for every person in this role usually ends up being way to expensive and not really worth it.
For the development team this is usually not a problem, often they already have a Visual Studio with MSDN subscription in which a TFS CAL is included.
We also have the ability to use Gated Builds, which allows us to make sure that a changeset is not checked in unless an associated build definition is executed successfully.
These features have gradually been added to Visual Studio Online and is now part of TFS 2015 as well.
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.
And unfortunately, it is not possible to export work item queries to Excel as easily from the web as it is from Visual Studio.
But, we can update multiple work items in TFS web access as well.
They obviously can’t use Visual Studio for committing their changes to TFS.