There was an interesting discussion on Agile vs Scrum Template for TFS 2012 on LinkedIn that I was interested in however LinkedIn has a bug and will not let me comment on that open group. So I will add my answer here.
With the release of Team Foundation Server 2015 CTP you should be starting to plan your upgrade strategy. It’s going to be a tough one but you should get ready […]
I just got a question on Teams without areas using Team Field in TFS and I decided that it warranted a bigger answer. The question was around creating nested teams and how to achieve it. Now, this applies to both Visual Studio Online and Team Foundation Server if you are using area path, and only TFS if you are using Team Field.
After upgrading to TFS 2013.3 you get some reports of errors in MTM from your users. Specifically they get a “Could not find mappings for all states defined in ‘Test Suit’ work item type” error when connecting. I have also seen “TF400860: TestManagement: Version 19, MinVersion: 19” in some cases in the web access.
In TFS 2012 the product team introduced the concept of Teams into TFS. Before this many organisations created multiple Team Projects and now want to merge Team Projects into one, or at least fewer. There are many reasons you might have done this in the past but there is no reason to live with this.
There is always something new to learn with TFS and today I learned something old. I had a user today that was constantly getting the message “Access denied user needs label permission in TFS”.
Have you ever tried to push data into TFS with Excel? I have, and it can often be the opposite of sweetness and light. The idea is to import data into TFS with Excel with history.
When you use the release build plugin in Jenkins to create a new release the plugin inadvertently leaves your password in clear text in the log files. We need to be able to mask passwords in Jenkins when calling Team Explorer Everywhere (TEE) so that we meet security requirements.
When customising your process template work item tracking gives you an “ArgumentNullException: value cannot be null. Parameter name key” exception with no more details.
In TFS 2012 the product team added a way to get to the tbl_Command information without needing to connect directly to the SQL Server and having access to the tables. This was an awesome add as being able to diagnose server issues and troubleshoot user reported problems makes us a little more efficient.