search

joshjohanning / joshjohanning.github.io

josh-ops.com | a devops blog
https://josh-ops.com
MIT License
8 stars 0 forks source link

Migrate Azure DevOps Work Items to GitHub Issues | josh-ops #28

Open utterances-bot opened 10 months ago

utterances-bot commented 10 months ago

Migrate Azure DevOps Work Items to GitHub Issues | josh-ops

A PowerShell script to migrate Azure DevOps Work Items to GitHub Issues

https://josh-ops.com/posts/migrate-azure-devops-work-items-to-github-issues/

narendralucky333 commented 10 months ago

Actually I'm new to azure and migration part also regarding migration of work items from TFS azure to GitHub, give more clarity about this process please I was stuck on this process.

joshjohanning commented 9 months ago

@narendralucky333 I haven't gotten a chance to test it yet, but this PR submitted might be better to run! The tool is a command line tool that can be used to migrate to GitHub Issues. Note that Issues in GitHub are more flat by nature (no parent/child hierarchy) and there is just one work item type (Issue). Projects in GitHub help with planning, but that will have to be set up after you create/migrate Issues in.

Hopefully this helps a bit!

narendralucky333 commented 9 months ago

Hi @joshjohanning,

Thanks for reaching out my message to solve this script, I’m will make sure try this one to do this task.

Thanks, Narendra

On Sun, Sep 24, 2023 at 9:40 PM Josh Johanning @.***> wrote:

@narendralucky333 https://github.com/narendralucky333 I haven't gotten a chance to test it yet, but this PR submitted https://github.com/joshjohanning/ado_workitems_to_github_issues/pull/6 might be better to run! The tool is a command line tool that can be used to migrate to GitHub Issues. Note that Issues in GitHub are more flat by nature (no parent/child hierarchy) and there is just one work item type (Issue). Projects in GitHub help with planning, but that will have to be set up after you create/migrate Issues in.

Hopefully this helps a bit!

— Reply to this email directly, view it on GitHub https://github.com/joshjohanning/joshjohanning.github.io/issues/28#issuecomment-1732610255, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXE4NDJ4LAR4XCCOYDV6J4TX4BLOHANCNFSM6AAAAAA327UO7E . You are receiving this because you were mentioned.Message ID: @.***>

riezebosch commented 6 months ago

I've created this in the past: https://riezebosch.github.io/azdev2gh/

Mudita2806 commented 4 months ago

Hi @joshjohanning,

I'm working on Migration of ADO boards to Github Issues.. Could you please help me understand what exactly is "-ado_area_path" in your script and which path should be here ?

Let's say I have ADO repo A, in which I have a project B and I have few workitems in the Azure Boards. So what would be the path for -ado_area_path ?

joshjohanning commented 1 month ago

Hi @joshjohanning,

I'm working on Migration of ADO boards to Github Issues.. Could you please help me understand what exactly is "-ado_area_path" in your script and which path should be here ?

Let's say I have ADO repo A, in which I have a project B and I have few workitems in the Azure Boards. So what would be the path for -ado_area_path ?

So sorry for the late reply @Mudita2806! This probably doesn't help you much but maybe someone else can stumble upon this and be helped.

In Azure DevOps, your work items are assigned to an "area path" when you create them. It's sort of like a folder of work items. You can create different area paths for different teams. Basically, the backlog view you're seeing is tied to an area path.

Image

You can run a query to point it at a path and see what items you return. The area path is used in part to determine which work items to migrate. Hope this helps!