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.
Related
How to access Fields of workitem like Type, Category, Found in Phase,reproducible, Found in build. I have created a workitem. But I get a error work item is not saved giving All the above mentioned fields are empty. few of those fields are read only. I am not able to write to it. Please someone can help me out soon.
Thanking you in advance
An easy way is installing TFS Power Tools, which provides a Process Template Editor.
Process Template Editor is a Visual Studio add-in, located under the Tools menu. The Process Template Editor provides a graphical user interface for customizing work items (field, workflow and the form) and process templates.
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
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've seen the question related to the error message you get from TFS when a workspace is already mapped. The accepted answer for removing the workspace is alright as a workaround, but it's already getting tedious to run a delete command each time this error occurs.
What do I need to change in order to get out of having to use this workaround? I've got two builds (continuous integration and nightly deploy), and need to add at least one more build type. I followed this URL to see if there was a possible resolution there, but I'm not sure I understand it completely.
I am not sure how this is accomplished in TFS 2010, as I have not gotten to work with Team Build in 2010, yet. In 2008, though, if you expand the Builds node in the Team Project and right-right click on either of the builds, you will see a "Manage Build Agents..." option. Click into that, and it will bring up a dialog. One of the things on that dialog is an option called "Working Directory". Do you have the same hard-coded path in both of them?
By default, when you create a new build definition, it provides a calculated folder for this value. This is where the build agent will do the checkout from TFS for the build attempt. The default value is, $(Temp)\$(BuildDefinitionPath), I believe (I am not connected to TFS at the moment).
The article you link to is basically saying that you should include either that $(BuildDefinitionPath) value or the $(BuildDefinitionID) value as part of that path in that dialog so that the two builds do not try to use the same workspace. Changing the working folder to include one of those values should resolve your issue, going forward.
In VSTS 2010 – in MS Test Runner
A defect can be logged against a work item called “BUG” by default.
This bug will have all the details relevant to the test that is run like the information in the following tabs in workitem bug – details tab, System info tab , Test Cases tab, etc .,
Instead of logging defects in workitem “BUG” is it possible to log defects to any other custom workitem but still manage to hold all these details tab , system info tab , test cases tab, etc., into the custom WI.
Please refer the attachment .
You need to put your custom work item type into the Microsoft.BugCategory category. Take a look at the command line tool witadmin in %ProgramFiles%\Microsoft Visual Studio 10.0\Common7\IDE
The following blog post might help you:
VS2010 Work item categories
If you want all the controls as well (like repro steps control), then you need to make sure the appropriate fields and form controls are copied over into the work item from the Microsoft work item definitions.