BoardBridge
Demo with sample data. This is a fictional company's Azure DevOps project. Click through freely: nothing is read from or written to Azure DevOps or GitHub.

✓ Connect Azure DevOps → Review the mapping → Dry run preview → Migrate

Online Store → contoso-retail/online-store

57 work items · project: new "Online Store board" · status: draft

Field mapping

We've suggested a mapping. Review it, then run a dry run to preview exactly what will change in GitHub.

Work item types → GitHub issue types

Azure DevOps typeCountGitHub issue type (empty = use a label)
User Story21
Task20
Feature7
Bug6
Epic3

States

Azure DevOps stateCountGitHub issueProject status
Closed37
Active16
New3
Removed1

People

Azure DevOps userItemsGitHub username
Priya Patel
priya.patel@contoso-retail.com
11
Sofia Alvarez
sofia.alvarez@contoso-retail.com
11
Daniel Okafor
daniel.okafor@contoso-retail.com
8
Emma Novak
emma.novak@contoso-retail.com
8
Marcus Chen
marcus.chen@contoso-retail.com
6
Liam O'Brien
liam.obrien@contoso-retail.com
3

Unmapped people are kept as text in each issue. GitHub only assigns people who have access to the repository.

Work item fields

These become real fields you can filter, sort and report on.

Issue fields appear on every issue, in every repository and project. If the organization can't use them (for example a personal account), BoardBridge uses project fields instead and says so in the dry run.

Priority

There's no Priority field yet, so BoardBridge creates one with an option for each priority ("P1" for priority 1, and so on).

Azure DevOps priorityItemsGitHub Priority
110
239
38

Comments and tags

Attachments

Needs no extra permission. People need access to Azure DevOps to open the files.

Needs the Contents: write permission, which lets BoardBridge change files in the repositories you granted it. BoardBridge only writes to the boardbridge-attachments branch, but the permission covers all branches.
This installation hasn't granted Contents: write, so this option is off.

History for sprint reports

Keeps how state, story points, remaining work, iteration and area changed over time, so burndown and velocity charts start with your real history instead of from zero. This is the only work item data BoardBridge stores outside GitHub. It stays in BoardBridge's Azure storage until you delete it.

Run a dry run before migrating.