I'm trying to do the migration from our TFS 2013 to VS Team Services but I'm facing one issue which is because of the process templates.
I got the error "Template Customization or Template Mismatch Error". Then I have the list of fields in my templates that are not "supported". (The two errors are with "Description HTML" and "Sprint")
To make sure everything works properly, I downloaded the process templates from Visual Studio Team Services and apply it to my TFS. I should have the same Process Templates on both sides.
But when I re-validate the migration summary, it keeps failing for the same reason.
Do you have any idea that would help me moving forward?
Thanks in advance!
You need to completely remove the fields using the command outlined here: http://msdn.microsoft.com/en-us/library/ms404864(v=vs.100).aspx
Related
We are in the process of migrating from TFS 2013 to TFS 2017 and for most parts it went really well.
We took a copy of the VM, reinstated it under another server name. I then ran the upgrade over the test server and followed all the prompts, and noted that this was a test machine. So it changes the configs etc, as it needs to.
We then ran into issues. It seems as though it did not upgrade the work item templates properly. Has anyone gone through the migration and had similar issues? Also more importantly how did you solve it.
There are two things that don't quite work. They are the Testing module and reporting. I suspect because there are some work items that are missing.
It appears that the tests were not migrated (although I believe they are in the database). It may just be that they are just not appearing because the WIT are not defined properly.
Can someone please tell me what we can do to migrate the tests across?
Error that we get when trying to add a new test plan
Seems you are just missing the test plan and test suit. You could go through this topic -- Update a team project manually to support test management
This topic applies to a team project that is defined on an on-premises
Team Foundation Server (TFS)and was created using a process template
that doesn't have test plans and test suites work item types.
wondering if anyone else has experienced anything similar and has overcome it. I am using OpsHub to migrate from an on premise 2012 TFS to VSOnline. I've set up my project with perms according to the instructions provided by Opshub. I ran a dry run of the migration to a personal instance of VSOnline in early December. Now I am trying to follow the same migration steps to our company's vsonline instance. I've set up everything the same. I am receiving an error that sure seems like a false positive. The utility is reporting that the WIT for Code Review Response has been customized. Specifically the field Reviewed By has been customized. I've opened up both WIT's and compared them. The only thing that is different is that on the 2012 WIT it didn't contain the rules ALLOWEXISTINGUSER and VALIDUSER and the Reportable field was blank. I tried adding them to the 2012 WIT but that didn't alleviate that problem and I set to the Reportable field to Dimension to match the 2015 WIT. I've checked the spelling on the 2012 WIT, it is the same. This has not alleviated the issue. Has anyone experienced and better yet, solved this? If so, would you mind sharing?
You need to restore the WIT definition to the original 2012 template rather than update it to match 2015 template. To do this, download the original process template used to create your team project and import the WIT XML definition files for Code Review Response using witadmin importwitd.
Refer to this link for details: https://www.visualstudio.com/en-us/get-started/setup/migrate-team-projects-vs
I am trying out Enterprise Architect integration with Team Foundation Server using EA trial version. I was able to create a model with several sub packages using DBMS based and TFS 2013 as a version control system. I was able to check out a package successfully from TFS via EA. However I could not check in that same package, EA keeps showing me the error message:
You cannot check-in package ‘blahblah’.
The associated file ‘blahblah.xml’ is not currently checked-out by you.
I double checked the xml file from TFS Source Control via Visual Studio, it showed that the xml file was “lock, edit” under my same credentials that was used in EA Version control settings.
Interestingly, I was able to Undo check out successfully.
Any help is appreciated.
I remember having this issue at work a couple of months ago. I don't have access to Enterprise Architect at the moment, nor am I in a position to recreate the problem to verify this solution, but I do remember how our team solved it:
The missing assumption to solving this, which may or may not be true in your case, is that your team went from the standard authentication method in the TFS settings, to SCC(or possibly the other way around). Now, assuming your credentials are the same in either method, you won't get an issue in Visual Studio, and can do everything apart from checking in in Enterprise Architect until you update your TFS settings in Enterprise Architect. Heck, everything will seem correct everywhere as your files IS checked out to you (no idea why this is permitted) but you cannot check in through the standard authentication method.
I had the same problem which I was able to solve only by resynchronizing the status with the version control.
Right click on Model, click on "Package Control", click on "Re-sync status with VC provider".
In TFS I have a started a Scrum project, but I want to add some fields to a Work Item.
So I'm following this tutorial on how to add Estimate and Completed work hour fields to a Work Item.
I added one field in the layout, like shown in the tutorial. But when I try to save it I then get the following error:
TF237113: You don't have enough permissions to complete the import operation.
I think I have all the needed permissions. I changed all my user permissions and also the permissions I have in the TFS project that I'm working on.
But so far no luck. Even when I try to add a field in the Layout tab that already exists, then it still gives me that error. Anyone any idea what I can try to solve this error?
It looks like you're using Visual Studio Online (Since I can see that you have a Windows Live ID), Visual Studio Online doesn't support process template customization at all at the moment. This is due to the fact that they release new versions of the service every 3 weeks or so, and having to consolidate and test all customization across all projects would be a major pain.
I'm working with TFS 2010 and Project 2010 Feature Integration pack and the Scrum for Team System v3 process template. Within the Project Server tab, I'm trying to set the default value for "Submit to Project Server" and "Enterprise Project" (which works fine), but when the Project Backlog Item is created/saved, it always fails when trying to sync with Project Server with the error message in the title of this post: TF285017: The Assigned To field cannot be blank.
I've Googled the error code, and it seems like there is no documentation for it anywhere. Can someone help?
Ultimately I fixed by adding the Assigned To field to the template and making it required. This probably isn't the best way to solve this issue, but does get around the error (and making the field required was something I was going to do anyway).
As the error states, in the TFS process template for the backlog item, the Assigned To field is mandatory. It needs to be filled before it can be synced with the other system.
You might try to remove the required flag from the Assigned To field in the workitem by using the TFS Power Tools process editor.