/
/
Map your Azure DevOps team to Jira accounts
For IT and integration admins who want Azure DevOps team members matched to Jira users by email, by asking their AI assistant.
On this page
Connector
Connect Azure DevOps, pick your AI tool and paste the prompt.
The problem
User mapping between trackers is done by eye
Admins match Azure DevOps team members to Jira accounts by eye. Names differ, emails change and some people have left, so work assignments cannot be carried across reliably.
Without PopdockAI
- List team members in Azure DevOps
- Search Jira for each by name or email
- Guess when names differ
- Carry assignments to the wrong account
With PopdockAI
- Team members and their emails are listed
- Each member is looked up in Jira by email
- Name only and multiple matches are flagged as unconfirmed
- Inactive accounts and missing users are listed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** For the Azure DevOps team `{team}` in project `{project}`, find each member's Jira account and report who is missing or mismatched.
**Step 1: Read the team on Azure DevOps**
Call `azure-devops-get-team-member` (Azure DevOps server) with `team-name` set to `{team}` and `project-name` set to `{project}`. If nothing comes back, report that the team was not found and stop. For each member, call `azure-devops-get-user` (Azure DevOps server) with `display-name` set to the member's `display-name` to read `mail-address` and `principal-name`.
**Step 2: Find the Jira account**
For each member with an email, call `jira-get-user` (Jira server) with `email` set to that address. If no result, retry with `name.contains` set to the display name and mark the match as Name only. Keep `user-account-id`, `name` and `active`.
**Step 3: Report**
Produce a table with one row per member: display name, Azure DevOps email, Jira name, `user-account-id`, active flag and a Match column holding Email, Name only, Inactive in Jira or Not found. Under the table list the members with Not found or Inactive in Jira, since work assigned to them cannot be carried across.
**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-assign-issue`, `jira-add-issue-watcher` or any other write tool.
* An email match is the only reliable match. Report a name-only match as unconfirmed.
**Validation:**
* If a member has no email on Azure DevOps, record No email and do not search Jira by a guessed address.
* If several Jira users match one address, list them all and do not choose one.Who it's for
One answer, three teams that use it
Integration admins
Map users before syncing trackers
Email matches you can trust, with doubtful ones marked, before assignments are carried across.
Map the Mobile team in Azure DevOps to Jira users by email.
IT administrators
Find inactive and missing accounts
See who has no Jira user or an inactive one, so access can be sorted out.
Which Platform team members in Azure DevOps have no Jira account or an inactive one?
Migration leads
Prepare a tracker migration
A clean user map is the first step in moving work between Azure DevOps and Jira.
List name only matches between the Data team in Azure DevOps and Jira.
How it works
What PopdockAI does when you ask
You name a team and your AI assistant maps its members to Jira accounts. Only email matches are trusted, and nothing is changed.
01
Ask
You name the Azure DevOps team.
02
Read
It lists the team members and their emails.
03
Look up
It finds each member in Jira by email.
04
Report
You get matches, name-only matches, inactive accounts and missing users.
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-team-member
azure-devops-get-user
jira-get-user
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
A user mapping you can trust
Related use cases
More ways to put this data to work
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.

.webp)
