As I understand it there is currently no reporting available on Visual Studio Team Services however looking at the source control history it shows the changeset history. Can additional columns be added here like number of changes, etc. so we can try and use this to understand the history of changes for our source control?
An even better solution would be to get real reporting from visual studio Team Services.
You're right, there are is not a comparable reporting set of capabilities in Visual Studio Team Services that Team Foundation Server on-premises currently has. The data all exists though in the Visual Studio Team Services account and there many ways of getting to that data:
Work Item Queries
Work Item Charts
REST APIs in Visual Studio Online
Team Foundation Server SDK (making calls against Visual Studio Team Services)
I imagine for your particular scenario, you'll want to use either option #3 or option #4 for querying version control information.
Update: We are currently working on an Analytics Service for Visual Studio Team Services data that will work with multiple reporting platforms like PowerBI and many others.
Related
Is there a way to use TFS Documents feature in VSTS (Visual Studio Team Services previously known as Visual Studio Online or Team Foundation Service)
If so, how?
That's only available in an on-premise TFS installation, because it has a requirement to link up with a Sharepoint server. You can't use VSTS with Sharepoint, and it's increasingly uncommon to find people using Sharepoint in conjunction with on-premise TFS, because the only real thing Sharepoint provides at this point is document management.
In Visual Studio Online, I don't have the Mapping On/Off option for mapping a feature to a product backlog item. MS says that you do it this way:
http://www.visualstudio.com/get-started/create-your-backlog-vs
relevant screenshot from instruction link below:
I do not have that Mapping On/Off option. Anyone know why?
Update: The backlog hierarchy features in Visual Studio Online were moved down to the Basic level and every account includes five
free basic licenses. This should now start showing up for everyone.
Is your user account assigned a Visual Studio Online Advanced user plan or an eligible MSDN Subscription? At the current time, to access the Agile Portfolio Management features in Visual Studio Online or Team Foundation Server, you will need access to the advanced capabilities by making sure your account is tied to one of the following:
Visual Studio Online Advanced user plan
Visual Studio Premium with MSDN
Visual Studio Ultimate with MSDN
Visual Studio Test Professional with MSDN, or
MSDN Platforms
Here are a couple of links to help get you going:
Assign licenses to users in Visual Studio Online
Change Access Levels (for TFS/Visual Studio Online which lists all of the features by access level)
We are attempting to migrate from one Visual Studio Online account to another Visual Studio Online account. This is different from an on-premise TFS to Visual Studio Online migration. Most articles explain a migration using the on-premise to VSO approach, only.
Accounts
https:\vsoaccount1.visualstudio.com\DefaultCollection
https:\vsoaccount2.visualstudio.com\DefaultCollection
For TFS to VSO, we found a solution by using OpsHub Visual Studio Online Migration Utility.
We also tried to use the same tool to point to another Visual Studio Online account as a source, but it fails stating that we can only point to a TFS instance.
Can this be done via scripting? If so, how? If there is a tool available, that would be great also. This should be a one time migration.
Update:
We need code only, including changesets, no work items. The project is using TFVC.
You can consider using TFS Integration Platform
For others that stumble across this thread, I have found this - the Visual Studio Team Services Sync & Migration Engine an open source project that appears to do TFS-TFS, TFS-VSTS, VSTS-TFS and VSTS-VSTS migration. It is an open source project initiated with the same purpose as the TFS Integration Platform, but to address some of the complexities (and the fact that it is now deprecated).
From the web site:
Visual Studio Team Services Sync & Migration Engine allows you to bulk edit data in Microsoft Team Foundation Server (TFS) and Visual Studio Team Services (VSTS). Supports both migration and bulk update scenarios.
I'd like to take advantage of Visual Studio Online but I have been using Team Foundation Server on-premises and would like to migrate my data (version control, work items, test cases, and test results) to get my team started with our history. How do I do that?
The Team Foundation Server Integration Platform is available as a free platform for migrating/synchronizing data between TFS servers and with Visual Studio Online.
The ALM Rangers have an article in MSDN Magazine with a walkthrough: http://msdn.microsoft.com/en-us/magazine/jj130558.aspx
There are a couple of limitations from what I understand:
Takes some work to get up and going but the walkthrough helps out a lot
This tool does migrate test cases but you need to run the UpdateSharedSteps tool from the product team.
Not actively invested in as new features in Team Foundation Server and Visual Studio Online lights up
Another option is to build your own migration utility using the Team Foundation Server SDK. You can use the Client Object Model to read data from your TFS server and then write it to your Visual Studio Online account.
There is a free migration utility from migrating data from Team Foundation Server on-premises to Visual Studio Online available from OpsHub: http://aka.ms/OpsHubVSOMigrationUtility.
It allows you to migrate team project(s) from TFS 2010, TFS 2012, and TFS 2013 including the history of:
Version Control
Work Items
Test Cases
It handles the most common scenarios by making smart assumptions that are good for most scenarios. For those with more advanced scenarios, the OpsHub Integration Platform is commercially available and helps with synchronizations, custom business rules during migrations including customized process templates, and migration/integrating with other ALM platforms like IBM, Atlassian, HP, etc.
I am currently looking to migrate an existing TFS2008 server to a new VS2012 server.
A major part of the reason behind this is that we want to be able to use the Microsoft Visual Studio Scrum template, however I am struggling to determine whether VS2008 is able to manipulate work items created using this template (according to all of the blogs and/or other information I can find, the templates can only be installed to a VS2010 or VS2012 server, but there is nothing clear about Visual Studio clients). I believe that both VS2010 and VS2012 can access an manipulate items based upon these templates.
Note: We HAVE to use VS2008 at the moment as some of the projects are for mobile devices (Windows/CE, Windows Mobile) and, as I am sure you will be aware, these projects are not supported by VS2010 or VS2012).
I am aware of the compatibility GDR's for both VS2008 and VS2010, but again they mention nothing specific about the scrum templates.
So, my question is simple...
Can I access and manipulate (add new work items, update existing items, create a sprint etc) a TFS project that is based upon one of the Microsoft Visual Studio Scrum templates on Team Foundation Server 2012 from Team Explorer 2008/Visual Studio 2008.
Work Item process templates (e.g. VS Scrum) have nothing to do with the version of the client used to connect to TFS, which means that any version of Visual Studio (2008, 2010, or 2012) will work with TFS 2012, regardless of the process template (Scrum, Agile MSF or CMMI).
Furthermore, the forward compatibility GDR provides the team explorer extension (window) that will give VS 2008 the ability to use the new functionality of TFS 2012 (e.g. start and end dates for iterations, capacity planning, etc.).
The process template (i.e. Visual Studio Scrum 2.0) is nothing but a set of XML documents detailing which work item types you will have, what fields they contain, some reports, SharePoint settings, security settings, etc. None of these affect or are affected by the version of Visual Studio.