/
/
See where Azure DevOps and Jira disagree
For project managers who track work in both Azure DevOps and Jira and want state and assignee drift found, by asking their AI assistant.
On this page
Connector
Connect Azure DevOps, pick your AI tool and paste the prompt.
The problem
Done in one tracker, still open in the other
Teams that track work in both Azure DevOps and Jira compare states and assignees by hand. An item marked done on one side and still open on the other goes unnoticed until a status meeting.
Without PopdockAI
- Filter Azure DevOps work items by state
- Find each linked Jira issue
- Compare state and assignee by hand
- Find the drift in the status meeting
With PopdockAI
- Work items in the state are read and matched to Jira issues
- A stated state mapping is applied
- State and assignee differences are tabulated
- Ambiguous matches are listed apart, never guessed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Reconcile Azure DevOps work items in project `{project}` with state `{state}` (default: Active) against the Jira issues that track the same work, using at most `{max-records}` work items (default 25).
**Step 1: Read the work items on Azure DevOps**
Call `azure-devops-get-work-item` (Azure DevOps server) with `project` set to `{project}`, `state` set to `{state}` and `max-records` set to `{max-records}`. Keep `id`, `title`, `work-item-type`, `state`, `assigned-to` and `changed-date`. If nothing comes back, say so and stop.
**Step 2: Find the Jira counterpart of each work item**
For each work item, call `jira-get-issue` (Jira server) with `summary.contains` set to the work item `title`. If the title is longer than 60 characters, use its first 60 characters. Also check whether the title or the work item already contains something shaped like a Jira key (letters, a dash and digits); if it does, call `jira-get-issue` with `issue-key` set to it instead. Accept a match only when the summary is the same or clearly the same piece of work. If several issues match, list them and do not pick one.
**Step 3: Compare and report**
Produce a table with one row per work item: work item id, title, Azure DevOps state, Jira key, Jira status, and a Verdict column holding Match, State differs, Assignee differs, Ambiguous or No Jira issue. Treat Azure DevOps Closed or Done as agreeing with Jira Done, and Active or In Progress as agreeing with In Progress. Compare assignees by display name and mark them as a difference only when both sides are set. Finish with counts per verdict.
**Rules & Guidelines:**
* `azure-devops-*` tools are on the Azure DevOps server and `jira-*` tools are on the Jira server.
* This prompt is read only. Never call `jira-add-issue`, `jira-update-issue`, `jira-assign-issue`, `jira-add-issue-comment` or any other write tool on either server.
* Do not guess a match from a loose keyword.
**Validation:**
* If Jira returns nothing for a work item, record No Jira issue and continue with the next one.
* State names differ between the two systems, so list the mapping you used under the table.Who it's for
One answer, three teams that use it
Project managers
Fix status drift before the meeting
A table of state and assignee differences shows exactly what to correct.
Reconcile Resolved work items in Fabrikam Mobile with Jira issues in FAB.
Delivery leads
Keep partners and teams in step
When one team uses Jira and another Azure DevOps, see where they disagree on shared work.
Where do Active Azure DevOps items in Northwind Commerce differ from Jira project NWC on assignee?
Scrum masters
Report one version of the truth
Know the drift before you report sprint progress from either tool.
Which Closed work items in Contoso Platform are still open in Jira project CON?
How it works
What PopdockAI does when you ask
You give a project, a state and a Jira project, and your AI assistant finds where the trackers disagree. Both systems are only read.
01
Ask
You give the Azure DevOps project, the work item state and the Jira project.
02
Read
It reads the work items and finds the matching Jira issues.
03
Compare
It applies a stated state mapping and compares assignees.
04
Report
You get a table of differences and a list of ambiguous matches.
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.
azure-devops-get-work-item
jira-get-issue
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.
The outcome
Tracker drift in one table
Related use cases
More ways to put this data to work
Map Azure DevOps users to Jira users
Ask your AI to map an Azure DevOps team to Jira users and it matches by email, flagging name-only matches, inactive accounts and missing users.
Learn More
Audit Azure DevOps branch hygiene
Ask your AI to audit a repository and it lists stale, locked and diverged Azure DevOps branches with a suggested action for each. Nothing is deleted or locked.
Learn More
Audit stale Azure DevOps work items
Ask your AI to audit a project and it flags unassigned, untouched and neglected priority 1 work items grouped by area. Nothing is reassigned or closed.
Learn More
Check Azure DevOps pull request readiness
Ask your AI if an Azure DevOps pull request is ready and it checks reviewer votes, comment threads and merge status, then gives a verdict. It never merges or approves.
Learn More
Compare Azure DevOps and GitHub CI health
Ask your AI to compare CI health for a branch and it lines up recent Azure DevOps builds with GitHub workflow runs, flagging where they disagree.
Learn More
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.