Report

Cross-Connector

Match BugHerd members to Azure DevOps users

For IT and integration admins who want BugHerd users matched to Azure DevOps identities by email, by asking their AI assistant.

Map BugHerd users to Azure DevOps users

Match the members of the Northwind website BugHerd project to users in Azure DevOps.

8 of 10 BugHerd members match an Azure DevOps user by email. - Matched by email: 8 members - Suggestion, name only: 1, Sam Patel - No match: 1, an external reviewer Nothing was added or changed in either system. Want the matched pairs as a table?

BugHerd

Sample figures. Your results come from your own account.

bugherd-get-users

azure-devops-get-user

On this page

The problem

The prompt

Who it's for

How it works

Tools used

Connector

BugHerd

Run it on your own BugHerd data.

Connect BugHerd, pick your AI tool and paste the prompt.

The problem

Matching users between tools by name sends bugs astray

Matching BugHerd members to Azure DevOps identities by hand is slow, and name only matches are error prone. A wrong match sends a bug to the wrong person.

Without PopdockAI

List the BugHerd project's members
Search Azure DevOps for each person
Match on names that may not be unique
Send bugs to the wrong person after a bad match

With PopdockAI

Members are matched to Azure DevOps users by email
Name only matches are shown as suggestions
People with no match are listed
No members are added and no assignees changed

The prompt

Use this prompt

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

Prompt

**Objective:** Match BugHerd users to Azure DevOps users by email address, optionally limited to names containing `{name-filter}`.

**Step 1: Read BugHerd users (BugHerd server)**

Call `bugherd-get-users` (use display-name.contains `{name-filter}` when it is given). Note display-name and email for each.

**Step 2: Look up each email (Azure DevOps server)**

For each BugHerd user with an email, call `azure-devops-get-user` with mail-address set to that email. If nothing comes back, retry with display-name set to the BugHerd display name.

**Step 3: Report**

A table: BugHerd display name, email, Azure DevOps display name, principal-name, match type (email, name only, none). List BugHerd users with no Azure DevOps match, since they cannot be assigned consistently on both sides.

**Rules & Guidelines:**

* `bugherd-get-users` is on the BugHerd server; `azure-devops-get-user` is on the Azure DevOps server.
* Read only. Never call `bugherd-add-project-member`, `bugherd-add-guest-to-project` or `bugherd-update-task`.

**Validation:**

* Treat a name-only match as a suggestion, not a confirmed match.
* If a BugHerd user has no email, report "no email" and do not guess.

Who it's for

One answer, three teams that use it

Integration engineers

Map identities before you sync

Get a reliable member mapping before you connect BugHerd tasks to Azure DevOps work.

Match the members of the Contoso Portal BugHerd project to Azure DevOps users by email.

IT administrators

Find people missing on one side

See who is in BugHerd but has no Azure DevOps account, so you can fix access.

Which members of the Fabrikam Shop BugHerd project have no matching Azure DevOps user?

Delivery managers

Assign bugs to the right person

Know which BugHerd member is which developer in Azure DevOps before you route bugs.

Show me the BugHerd to Azure DevOps user mapping for the Northwind Traders site project, with name only matches marked.

How it works

What PopdockAI does when you ask

You name the BugHerd project and your AI assistant matches its members to Azure DevOps users. It only reads and keeps uncertain matches apart.

Ask

You name the BugHerd project.

Your AI tool

Read

It lists the BugHerd members and the Azure DevOps users.

bugherd-get-users

azure-devops-get-user

Match

It pairs them by email and treats name-only matches as suggestions.

No items found.

Report

You get matched users, suggestions and anyone with no match.

Your AI tool

What PopdockAI provides

The tools behind the answer

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

get-data

bugherd-get-users

Returns the members of the BugHerd organization with their display name and email. Filter by email or name.

get-data

azure-devops-get-user

Returns users records from the Azure DevOps connector. Use it to read and filter users across your Azure DevOps projects.

Read only.Nothing in BugHerd 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.

The outcome

A user mapping you can trust

Related use cases

More ways to put this data to work

BugHerd bug fix progress digest for Azure DevOps

Ask your AI for a progress digest of BugHerd bugs of a chosen severity and it groups them by Azure DevOps work item state, flagging overdue and unlinked ones.

Learn More

Find BugHerd bugs without Azure DevOps work items

Ask your AI which BugHerd bugs have no Azure DevOps work item and it lists them with suggested matches by title. Suggestions are never presented as confirmed.

Learn More

Reconcile BugHerd bugs with Azure DevOps work items

Ask your AI to reconcile BugHerd bugs with Azure DevOps work items and it reports where statuses disagree. Read-only on both, nothing is guessed.

Learn More

Trace a BugHerd bug to Azure DevOps code changes

Ask your AI to trace a BugHerd bug and it follows the task to its work item, pull requests and builds, then reports a timeline.

Learn More

Add an update to a BugHerd task

Ask your AI to add a note to a BugHerd task by its number, with an optional file from a link, and it posts the update only after you confirm.

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.