Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Is it possible to copy a Work Item Template from one project to another?

Tags:

The two projects in question were created from the same base template. Essentially I've stripped out a bunch of stuff that we don't need in several of the Work Item Templates, and deleted a few others. I'd like to copy these template changes to another project, instead of redoing all the work I just did.

like image 562
David Avatar asked May 05 '09 18:05

David


People also ask

How do I bulk update work items in Azure DevOps?

To change the type of cards from tasks to issues: select change type. To change the parent item of a task/s or child item of an issue/s: select Link to an existing work item. To bulk update items in backlog then select backlog on the left navigation bar and there will be an option to multi-select.

How do I create a bug template in Azure DevOps?

Create a TemplateClick the Project Settings wheel in the bottom left-hand corner. Under Boards, select Team configuration. In the menu that appears, click the Template tab. In Bug templates, click the + New Template button.

How do I export Azure DevOps to excel?

A: If you want to export a query to Excel, you can do that from Excel or Visual Studio/Team Explorer. Or, to export a query directly from the web portal Queries page, install the Azure DevOps Open in Excel Marketplace extension. This extension adds an Open in Excel link to the toolbar of the query results page.


1 Answers

If the other project is already created on the Server you can use the Team Foundation Server Power Tools. The Tool you want is the Process Editor.

After you install. Fire up Visual Studio and connect to Team Explorer. Then go to Tools | Process Editor | Work Item Types | Import WIT

Select the Work Item Type template and the project you want to install it to.

or if you prefer command line solutions use witimport:

witimport /f file /t TeamFoundationServer /p teamproject [/v] [/e encoding]

/f Specifies the work item type XML definition file to be imported.

/t Specifies the name of the Team Foundation Server. This can also be a fully specified URL such as http://server:8080.

/p Specifies the Team Project on the Team Foundation Server to which the file is imported.

/v Validates the XML without importing the work item type.

/e Specifies the name of the .NET Framework 2.0 encoding used to import the work item type XML. For example, /e utf-7 will use Unicode (UTF-7) encoding. Encoding is auto-detected by default where possible. If unavailable, encoding defaults to UTF-8.

like image 84
Robert Kozak Avatar answered Oct 05 '22 13:10

Robert Kozak