Connectors

/

Azure DevOps

/

Reconcile Azure DevOps work items with GitHub issues
Report
Cross-Connector

Reconcile work items with GitHub issues

For project managers who track work in both Azure DevOps and GitHub and want the gaps found, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Reconcile Azure DevOps work items with GitHub issues
Reconcile open work items in Contoso Platform with the issues in contoso/web on GitHub.
31 open work items and 24 open issues. 9 work items have no issue and 4 issues have no work item. - Matched: 22 pairs - Work items with no issue: 9, for example 4790 Checkout button misaligned - Stale reference: work item 4602 points to closed issue 312 Want the 13 unmatched items listed?
Azure DevOps
Sample figures. Your results come from your own account.
azure-devops-get-work-item
github-get-issue

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Azure DevOps

Azure DevOps
Run it on your own Azure DevOps data.

Connect Azure DevOps, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

The same problem tracked twice, or not at all

Work items and GitHub issues for the same problem are tracked separately, so gaps go unnoticed. Someone compares the two lists by eye, and stale references to closed issues stay in work items.

Without PopdockAI

  • List open work items in Azure DevOps
  • List issues in GitHub
  • Match them by eye
  • Leave stale references to closed issues

With PopdockAI

  • Open work items and GitHub issues are read
  • They are paired by references and titles
  • Unmatched items on each side are listed
  • Stale references are flagged, and nothing is written

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Find which open Azure DevOps work items of type `{work-item-type}` (default Bug) in project `{project}` have a matching GitHub issue in company `{company}`, and which do not.

**Step 1: Work items**

Call `azure-devops-get-work-item` with project `{project}` and work-item-type `{work-item-type}`. Drop items whose state is Closed, Done or Removed.

**Step 2: GitHub issues**

Call `github-get-issue` with company `{company}` and status open. For each work item you may refine by calling `github-get-issue` with title.contains set to the work item id or a distinctive title phrase.

**Step 3: Match across servers**

A match is a GitHub issue whose title or body contains the work item id (for example AB#123 or the number) or whose title equals the work item title ignoring case. Mark title-only matches as probable.

**Step 4: Report**

Three lists: matched (work item id, issue number, state of each), work items with no issue, issues that mention a work item id that is closed or missing.

**Rules & Guidelines:**

* Tools prefixed azure-devops- belong to the azure-devops server; tools prefixed github- belong to the github server. Both servers must be connected.
* This prompt is read-only. Never call github-add-issue, github-update-issue, github-add-issue-comment, github-add-issue-label, github-add-issue-assignee, github-lock-issue, github-unlock-issue, github-rerun-workflow-run, github-cancel-workflow-run, github-enable-workflow, github-disable-workflow, github-add-milestone or github-update-milestone.

**Validation:**

* If no work items come back, stop and report that.
* Never treat a partial title overlap as a match without marking it probable.

Who it's for

One answer, three teams that use it

Project managers

Clean up duplicated tracking

Items with no counterpart and stale references are listed, ready to tidy.

Reconcile open work items in Fabrikam Mobile with issues in fabrikam/mobile on GitHub.

Open source maintainers

Link community issues to internal work

See which GitHub issues have no internal work item, so nothing reported is forgotten.

Which GitHub issues in northwind/portal have no Azure DevOps work item?

Engineering managers

Find orphaned work

Work items pointing to closed issues are flagged, so the team stops chasing finished work.

List Azure DevOps work items in Contoso Platform that reference closed GitHub issues.

How it works

What PopdockAI does when you ask

You name a project and a repository, and your AI assistant reconciles the two trackers. It only reads, and GitHub write actions are off limits.

01

Ask

You name the Azure DevOps project and the GitHub repository.

Your AI tool

02

Read

It reads open work items and GitHub issues.

azure-devops-get-work-item
github-get-issue

03

Match

It pairs them by references and titles.

No items found.

04

Report

You get unmatched items on each side and any stale references.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Azure DevOps and one secure connection to your AI tool. No code, no exports.

get-data

azure-devops-get-work-item

Returns work items records from the Azure DevOps connector. Use it to read and filter work items across your Azure DevOps projects.
get-data

github-get-issue

Returns GitHub issues from a repository. Filter by issue number, title text, state, labels, assignee, author, milestone, and created or updated date range.
Read only.Nothing in Azure DevOps Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

How Popdock AI secures your data

The outcome

Work tracked once, on the right side

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation