We upgrade our TFS test environment from 2015.1 to 2017.3 .
We have Multi Value control in our Work Items, after the upgrade the Work Item form was empty (unless the tags), and the error on the console was about the multi value control. I downloaded the Multi Value extension from the market place, but is only for the new form (WebLayout), and we not want to move to the new form yet.
I go to Legacy Extensions and disable the old multi value control extension, and now we the work item is appear, unless the fields with the multi value ("Cannot create work item control of type "MultiValueControl"). I saw on the old extension website that have a newer version of this (1.3.2.5) but I didn't find a download to this file anywhere. Is there a way to make the multi value work on the old form? or we must to use the new form?
Try this control: https://marketplace.visualstudio.com/items?itemName=ms-devlabs.vsts-extensions-multivalue-control
Customize for xml: https://github.com/Microsoft/vsts-extension-multivalue-control/blob/master/xmldetails.md
Related
I am working with TFS 2018 where I modify the templates of the work items so that they have the data that I need, that is, add new fields.
I need these fields to be synchronized to Project in a particular field, what happens to me is that they are not impacting on project.
Is it possible to do this?
If you mean Synchronize Team Foundation Server with Project Server, then TFS 2018 no longer support native integration with Office Project Server. You need to find the third-party support.
TFS 2017 and later versions no longer support native integration with
Office Project Server. If you upgrade to TFS 2017 or want to use a
third party option, see Synchronize TFS with Project Server.
If you mean Synchronize data between work item fields, then you can apply Assign value rules to a filed, e.g COPY rule : Copies a specified value to a field when a user creates or modifies a work item.
I have a request to add a new field to a work item and we are using TFS 2017. My organization has done this before in previous versions of TFS. However, I remember customizing any process template to add new fields causes headaches when upgrading to the next version of TFS.
My question is if this is still a concern? If so, is there a work-around for this issue?
Thanks!
Tim
Basically, you would have the same procedure if you want to upgrade a on-premises TFS with customizations.
So, before you customize, you should understand which customizations support an easy update path and which do not.
Recommended practices:
Identify the best options for customizing WITs that support your
tracking requirements. When you change objects that track work items,
you should identify how these changes will affect existing and future
team projects.
Put processes and all XML definition files under version control. Do
not deploy objects that you define but have not stored in a
repository.
Test your customized objects just as you would test your software.
Minimize the number of custom fields that you introduce. Minimize the
number of fields that you make reportable.
Please refer to the link below for more information:
https://learn.microsoft.com/en-us/vsts/work/customize/on-premises-xml-process-model#before-you-customize
Is it possible to reset the work item type history that is proposed to a user who creates a new WorkItem query?
We have some TeamProjects that went through two Process-Template customizations including localization and WorkItem form layout optimizations.
With TFS 2015 we're finally moving to the Agile process template. The problem is that somewhere the TFS stores the WorkItem-Types you have ever used and displays them in the WorkItem query designer.
The values in the Work Item Type are mixed both german and english and are picked from all of the past process templates the team project has ever been configured to use.
Is it possible to reset that list and if so, how?
The scope of the query editor is for all projects in a give collection. When you open the dropdowns, it thus shows all work item types in any of the projects in the collection.
In TFS 2015 we have added a checkbox to scope your query to the existing project. This checkbox is off by default because the majority of the queries run in the scope of a project. When the checkbox is unchecked, the dropdowns are limited to show only the states, fields and work item types that are in use by the existing project.
If you don't need these work item types and the work items, you can use witadmin destroywitd to destroys the work item types, after running the destroy command, the work item types will disappear from the drop-down. But please notice this will also destroy every work item of that type permanently without recovery.
witadmin destroywitd /collection:CollectionURL /p:Project /n:TypeName [/noprompt]
How does your team differentiate TFS work items that are "done" (development/testing complete) vs. "deployed" (live in Production)?
My first option would be to use a Tag to mark this. You can query and filter through them.
Another option would be to customize the work item types with an additional field, but this route is a bit more complex.
Change your Definition of Done to include: Deployed. Doing that you will have code working in production. If is needed more work, is not done.
But I guess you´re asking about how to have a new status. You can modify the workflow template to include this new state. In older versions of TFS you only can do that before to create the project, not in an started project. I don´t know in the latest version.
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.