Connectors

/

BugHerd

/

BugHerd bug fix progress digest for Azure DevOps
Report
Cross-Connector

One digest of how critical bugs are being fixed

For managers who want BugHerd bug reports tracked against their Azure DevOps work item states, by asking their AI assistant.

Try PopdockAI free
Get a live demo
BugHerd bug fix progress digest for Azure DevOps
Give me a progress digest of the critical bugs in the Northwind website BugHerd project and where they stand in Azure DevOps.
14 critical bugs in Northwind website: 6 closed, 5 in progress, 1 new, 2 not linked. - In progress: 5 work items, 2 overdue - Closed: 6 work items - Not linked: 2 tasks, 118 and 131, have no work item id - Broken link: task 127 points to work item 9999, which was not found Want the overdue ones listed with their owners?
BugHerd
Sample figures. Your results come from your own account.
bugherd-get-tasks
azure-devops-get-work-item

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

BugHerd

BugHerd
Run it on your own BugHerd data.

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

Try PopdockAI free

The problem

No single view of how critical bugs are moving

Critical bugs reported in BugHerd are worked as Azure DevOps work items, but there is no single view of their progress. A manager has to open each task, find its work item and check its state and due date.

Without PopdockAI

  • Filter BugHerd for bugs of one severity
  • Open each task to find its work item id
  • Look up every work item in Azure DevOps
  • Lose track of overdue and unlinked bugs

With PopdockAI

  • Tasks of the chosen severity are read in one pass
  • Each linked work item is looked up for its state
  • Tasks are grouped by state, overdue ones flagged
  • Unlinked tasks and broken links are reported, not dropped

The prompt

Use this prompt

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

Prompt
**Objective:** Produce a progress digest of BugHerd tasks of severity `{severity}` (default critical) in project `{project-id}`, joined to Azure DevOps work item state.

**Step 1: Read the tasks (BugHerd server)**

Call `bugherd-get-tasks` with project-id `{project-id}` and severity `{severity}`. Drop tasks with status closed.

**Step 2: Read the work items (Azure DevOps server)**

For each remaining task with an external-id, call `azure-devops-get-work-item` with id set to the external-id. Take state, priority, assigned-to and changed-date.

**Step 3: Report**

Group by work item state (and a group "not linked" for tasks with no external-id). For each: task-number, title, due-date, work item id, assigned-to. Call out tasks past due-date whose work item is not Done, and tasks not linked at all.

**Rules & Guidelines:**

* `bugherd-get-tasks` is on the BugHerd server; `azure-devops-get-work-item` is on the Azure DevOps server.
* Read only. Never call any BugHerd tool that adds, moves or updates records.

**Validation:**

* If no tasks match the severity, say so and stop.
* If a work item cannot be found for an external-id, list it under "broken link".

Who it's for

One answer, three teams that use it

Engineering directors

See where critical bugs stand

Get a digest of critical bugs grouped by delivery state without asking each team for an update.

Where do the critical bugs in the Contoso Portal BugHerd project stand in Azure DevOps?

Delivery managers

Catch overdue fixes early

See which bugs are overdue or never got a work item, so you can chase the right people.

Which important bugs in the Fabrikam Shop BugHerd project are overdue or have no Azure DevOps work item?

Client services leads

Report fix progress to clients

Turn the state of every serious bug into a client update you can trust.

Give me a progress digest of critical bugs in the Northwind Traders website BugHerd project for this week's client call.

How it works

What PopdockAI does when you ask

You choose a BugHerd project and severity, and your AI assistant follows each bug to its Azure DevOps work item. Both systems are only read.

01

Ask

You choose the BugHerd project and the severity.

Your AI tool

02

Read

It reads the matching BugHerd tasks and their linked work item ids.

bugherd-get-tasks

03

Look up

It reads each work item in Azure DevOps for its state.

azure-devops-get-work-item

04

Report

You get tasks grouped by state, with overdue, unlinked and broken links flagged.

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-tasks

Returns tasks from BugHerd projects: title, description, status, severity, assignee, requester, page, tags, due date and external ID. Filter by project, task number, title, status, severity, assignee, requester email, external ID and due or created date.
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.
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.

How Popdock AI secures your data

The outcome

Critical bug progress in one digest

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