GitHub Issues – Do you sync to Azure DevOps?

If you store all your code in GitHub, why not create all your issues there too?

You might be reluctant to move your backlog to GitHub from Azure DevOps as you don’t want to lose the metrics functionality.

But you can easily sync all your GitHub Issues to Azure DevOps automatically to have the best of both worlds.

Here's a quick guide in setting it up for your GitHub Repository and Azure DevOps.

Install the Azure Boards App from the GitHub Marketplace
Create the GitHub Action secrets
ADO_PERSONAL_ACCESS_TOKEN (Azure DevOps | User settings | Security | Personal access tokens)
The Azure Personal Access Token requires "read & write" permission for Work Items.
GH_PERSONAL_ACCESS_TOKEN (GitHub | Personal settings | Developer settings | Personal access tokens)
The GitHub Personal Access Token requires "repo" permissions.
ADO_ORGANIZATION (https:// ssw .visualstudio.com/SSW.Rules)
The Organization name is in your Azure DevOps URL.
ADO_PROJECT (https://ssw.visualstudio.com/ SSW.Rules)
The Project name can also be found in your Azure DevOps URL.
Create the following GitHub Action

E.g. SSW uses this template for their projects, you may need to change the new and closed states depending on your environment.

name: Sync issue to Azure DevOps work item
on:
  issues:
    types:
      [opened, edited, deleted, closed, reopened, labeled, unlabeled, assigned]

jobs:
  alert:
    runs-on: ubuntu-latest
    steps:
      - uses: danhellem/github-actions-issue-to-work-item@master
        env:
          ado_token: "${{ secrets.ADO_PERSONAL_ACCESS_TOKEN }}"
          github_token: "${{ secrets.GH_PERSONAL_ACCESS_TOKEN }}"
          ado_organization: "${{ secrets.ADO_ORGANIZATION }}"
          ado_project: "${{ secrets.ADO_PROJECT }}"
          ado_wit: "Product Backlog Item"
          ado_new_state: "New"
          ado_close_state: "Done"
          ado_bypassrules: true