Visual Studio Online move PBI and tasks from one project to another - azure-devops

I'm using Visual Studio Online I have created a project A with PBI's that has many tasks inside them.
I have now created a new project B and would like to move/copy/migrate the PBI's and tasks from project A to this project B.
How do I achieve this.

You can do this quite easily using the Excel integration feature.
In Project A, create a query that lists all your work items.
Open Microsoft Excel, go the TEAM tab.
Click 'New List', select your project, select 'Query List', select
the query you just created.
In the Work Items tab select the 'Choose Columns' button and select
all the columns you want to migrate.
Open another Excel Spreadsheet and create a 'New List'. This time
connect to Project B and select the 'Input List'.
Copy and paste all the work items from Project A list to the Project
B list (excluding the Id column).
Click Publish.

Using Excel won't let you copy a lot of stuff, particularly attachments.
A (slightly) better approach would be to use the OData interface at https://tfsodata.visualstudio.com/ to read work items and all their related data from project A, then insert into project B.
As of today though, the API is also quite limited (e.g. doesn't allow to create links between work items).

It's 2020 now, and the answer, with Azure DevOps is yes, you most definitely can.
See Azure boards documentation's "move work items, change work item type"

Related

Moving boards between projects

I need a little advice.
We have a few projects in Azure DevOps, and I need to move a Board and all it's work items, regardless of status, from one project into another project. So basically lifting and shifting it.
Is there an easy way to achieve this?
Moving boards between projects
You could use bulk move:
Create new query to select all work items Create and save managed queries with the query editor:
Select all work items in the query result and select move:
Select your new team project:
Save all work items.

Prebuilt Azure Devops Boards

Im happy with the Kanban side of Devops along with dashboards etc. The team is looking to try to roll out multiple projects, but all with the same Epics, Features, Backlog and Tasks etc etc ie a repeatable project. Although im fairly sure the answer is no, is there a way to build out a project with all the work items, and then copy this as a file, and when creating a new one, use this as the basis??
is there a way to build out a project with all the work items, and then copy this as a file, and when creating a new one, use this as the basis??
When you create new projects, you can use the same Process.
For copy the work items as the basis, I suggest that you can export Work items to excel , then when you can import the exported work items to new projects.
For more detailed info, you can refer to this doc: Bulk import or update work items using CSV files

Is there a possibility to create a Cross Project Roadmap in Azure DevOps?

Is there a possibility to track Work Items in Azure DevOps "Cross Project" wide?
So that I can get an overview over all e.g. Epics from all Projects and when they are due. (Cross Project Roadmap for specific work items).
I searched the extention Library and thought it might be able to do it over the API by pulling all work items and then combine it in an own tool.
Any Ideas would be appreciated.
You can create a query and and mark the "Query across projects" checkbox, then you will get a results from all the projects.
For example, a query for all done Epics in all the projects:
In this way you can query each work item field, save the queries and put the results on the dashboard, so you will have "cross projects roadmap".
Update on this Issue. The Azure DevOps Extention https://marketplace.visualstudio.com/items?itemName=ms-devlabs.workitem-feature-timeline-extension does basically what is needed. Not completely but in some sort.

Move Work Items to different project on Azure Devops

I am trying to move/copy my Work Items into a different project. I will need all the Epics, Features, User stories, Tasks, comments, links etc.
The steps given here show how to move a single work item, so my plan is to move my Epics which were only a handful and not have to move each and every user story/task. But unfortunately when the Epic is moved, the children are left behind.
Is there any other way to do this?
I saw this Excel solution, but doesn't look like its copying the comments.
You may use a bulk move:
Create new query to select your work items Create and save managed queries with the query editor:
Select all work items in the query result and select move:
Select your new team project:
Save all work items:

How do you see the changes for a version in TFS?

I'm trying to migrate to TFS from VSS and I need to be able to show what files were checked in between two releases. In VSS we would just label the code for a release and view history between labels and generate a report to show the checkins and the comments. Is there a way to get similar results with TFS? Or show the differences between two changesets or labels?
The command line tool tf.exe gives you more options than the GUI (and can either give results in a Dialogue or as standard output --- good for feeding into further processing).
E.g.
tf hist . -r /version:C10~C1000
will list all the changesets affecting this folder and content recursively between changesets 10 and 1000.
See the documentation on MSDN.
If you need maximum flexibility, you can create your own commands using the TFS client assemblies. Unfortunately documentation is somewhat sparse.
Right click on your desired folder on TFS (e.g. the root folder), you'll find following two options:
1, Apply Label - this allows you to apply label to a particular version of that folder.
2, Compare - this allows you to compare that folder between versions, and one of the choices is comparing by label.
Right click on any node in TFS Source Control and choose 'View History'
This will show you all changesets ordered by date descending.
Double click on those and you can see the detail about the change set: the comment, associated work items, and files that were changed.
As Jeff said, right-click on the project, any folder or file, and choose "View History" to see all changes. If you know when your labels were applied, it's easy to scroll down this list until you hit a particular date/time.
For an exact list between two labels or changeses, use "tf.exe history" (as Richard says) from a Visual Studio command prompt (in your start menu in the Visual Studio 2005 folder). For more info on this just execute "tf.exe help history".
For day to day changes, if you use TFS build you can see the changes since the last build at the bottom of the build information page (Double click the build name in Team Explorer, then double click the specific build. Scroll to the bottom of this page and open "associated changesets". I've set out CI build to not associate changesets, which means that our daily test build lists all changesets since the previous daily build - a great summary of the changes for our testers to get their teeth into.
I was using the command line tf hist and getting the changesets to compare by finding the highest changeset in a label or branch changeset, but having a manual process and using the command line didn't go over too well here. I used Carl Daniel's code to write a little web application that will bind the changes to a datagrid.
If you're looking for something special the standard interface doesn't give you it's fairly simple to write your own application that links into TFS. I'd definitely suggest it.