All Projects → microsoft → Vsts Work Item Migrator

microsoft / Vsts Work Item Migrator

Licence: mit
WiMigrator is a command line tool for migrating work items between VSTS/TFS projects

Projects that are alternatives of or similar to Vsts Work Item Migrator

Azure Devops Migration Tools
Azure DevOps Migration Tools allow you to migrate Teams, Backlogs, Tasks, Test Cases, and Plans & Suits from one Project to another in Azure DevOps / TFS both within the same Organisation, and between Organisations.
Stars: ✭ 218 (+75.81%)
Mutual labels:  microsoft, tfs
Jplogistics c152
A MSFS Addon to improve the Cessna C152
Stars: ✭ 118 (-4.84%)
Mutual labels:  microsoft
Recommenders
Best Practices on Recommendation Systems
Stars: ✭ 11,818 (+9430.65%)
Mutual labels:  microsoft
Xiaoai
a tiny&smart AI & Repo for work for AI Survey百度云资源持续更新中,欢迎点赞star Min's blog 欢迎访问我的博客主页!(Welcome to my blog website !)https://liweimin1996.github.io/
Stars: ✭ 111 (-10.48%)
Mutual labels:  microsoft
Microsoft Authentication Library For Android
Microsoft Authentication Library (MSAL) for Android
Stars: ✭ 103 (-16.94%)
Mutual labels:  microsoft
Msphpsql
Microsoft Drivers for PHP for SQL Server
Stars: ✭ 1,570 (+1166.13%)
Mutual labels:  microsoft
Microsoft 365 Community
Microsoft 365 community contributed documentation https://docs.microsoft.com/microsoft-365/community/
Stars: ✭ 94 (-24.19%)
Mutual labels:  microsoft
Docx
Easily generate .docx files with JS/TS with a nice declarative API. Works for Node and on the Browser.
Stars: ✭ 2,150 (+1633.87%)
Mutual labels:  microsoft
O365 Moodle
Office 365 and Azure Active Directory plugins for Moodle
Stars: ✭ 117 (-5.65%)
Mutual labels:  microsoft
Azops
This container image can be used to deploy ARM templates at Tenant, Management Group, Subscription and Resource Group scope and export current Azure configuration hierarchy in Git repository.
Stars: ✭ 109 (-12.1%)
Mutual labels:  microsoft
Chakracore Delphi
Delphi and Free Pascal bindings and classes for Microsoft's ChakraCore library
Stars: ✭ 109 (-12.1%)
Mutual labels:  microsoft
Libmspack
A library for some loosely related Microsoft compression formats, CAB, CHM, HLP, LIT, KWAJ and SZDD.
Stars: ✭ 104 (-16.13%)
Mutual labels:  microsoft
Psadhealth
A toolkit of AD specific health checks that you can run in your environment to ensure your Active Directory is running optimally.
Stars: ✭ 114 (-8.06%)
Mutual labels:  microsoft
Tfs
Microsoft TFS API Python client
Stars: ✭ 101 (-18.55%)
Mutual labels:  tfs
Tfsnotificationrelay
An extensible plugin for TFS that sends notifications to Slack, HipChat and IRC
Stars: ✭ 120 (-3.23%)
Mutual labels:  tfs
Blazor Blogs
Simple blogging application written in Microsoft Server Side Blazor
Stars: ✭ 95 (-23.39%)
Mutual labels:  microsoft
Gis
gis (go image server) go 实现的图片服务,实现基本的上传,下载,存储,按比例裁剪等功能
Stars: ✭ 108 (-12.9%)
Mutual labels:  tfs
Bingmapsv8codesamples
This is a collection of over two hundred code samples an growing for the Bing Maps V8 web control.
Stars: ✭ 111 (-10.48%)
Mutual labels:  microsoft
Azure Event Hubs For Kafka
Azure Event Hubs for Apache Kafka Ecosystems
Stars: ✭ 124 (+0%)
Mutual labels:  microsoft
Jira Azuredevops Migrator
Tool to migrate work items from Atlassian Jira to Microsoft Azure DevOps/VSTS/TFS.
Stars: ✭ 120 (-3.23%)
Mutual labels:  tfs

Introduction

WiMigrator is a command line tool designed with the following goals in mind:

  • Migrate work items from one Azure DevOps/TFS project to another
  • Real world example of how to use the WIT REST APIs
  • Cross platform support

Build Status

Features

  • Migrate the latest revision of a work item or set of work items based on the provided query, including:
    • Work item links (for work items within the query results set)
    • Attachments
    • Git commit links (link to the source git commit)
    • Work item history (last 200 revisions as an attachment)
    • Tagging of the source items that have been migrated

Getting Started

Requirements

  • Source Project on Azure DevOps or TFS 2017 Update 2 or later
  • Target Project on Azure DevOps or TFS 2018 or later
  • Personal access tokens or NTLM for authentication
  • Bypass rules or Project Collection Administrator permissions required on target project
  • Process metadata should be consistent between the processes
    • Limited field mapping support is provided to map fields from the source to target account
    • Area/Iteration paths can be defaulted to a specific value when they don't exist on the target

Running

WiMigrator supports the following command line options:

  • --validate validates that the metadata between the source and target projects is consistent
  • --migrate re-runs validation and then migrates the work items

Migration runs in two parts:

  • Validation
    • Configuration settings
    • Process metadata is consistent between projects
    • Identifies any work items that were previously migrated
  • Migration
    • Phase 1: Work item fields
    • Phase 2: Attachments, links, git commit links, history, target move tag
    • Phase 3: Source move tag

A sample configuration file is provided with documentation of all the settings.

Execution example:

dotnet run --validate configuration.json

HOWTO Video

Limitations:

  • Artifact links (other than git) are not migrated
  • Board fields are not migrated
  • Test artifacts (e.g. test results) are not migrated

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].