/
/
Spot BugHerd tasks and GitHub issues that disagree
For project leads who want to know which linked bugs are closed in one tool and open in the other, just by asking their AI assistant.
On this page
Connector
Connect BugHerd, pick your AI tool and paste the prompt.
The problem
Linked tasks and issues drift out of step
Once BugHerd tasks and GitHub issues are linked, they drift. An issue is closed while the task stays open, or the task is signed off while the issue lingers, and finding these means checking every pair by hand.
Without PopdockAI
- Find every BugHerd task that references an issue
- Open each linked GitHub issue
- Compare open and closed states by hand
- Miss links that point nowhere
With PopdockAI
- Links are collected from both sides, archived tasks included
- Each pair is checked for open or finished
- Drifted pairs and broken links are listed
- Pairs in step are counted, nothing changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Find every link between the BugHerd project `{project-name}` and the GitHub repository `{repository}` created in the last `{lookback-days}` days (default 90), and report where the two disagree.
How the two systems are linked: a BugHerd task created from a GitHub issue carries "<repository>#<issue number>" in its external-id. A GitHub issue created from BugHerd starts its title with "[BugHerd <project name> #<task number>]".
**Step 1: Links from BugHerd**
Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If several match, list their names and project-id values and ask which one; do not guess. Then call `bugherd-get-tasks` and `bugherd-get-archived-tasks` with `project-id`, `created.from` set to the start of the period and `max-records` 500. Keep tasks whose external-id starts with "{repository}#".
**Step 2: Links from GitHub**
Call `github-get-issue` with `company` set to `{repository}`, `title.contains` set to "[BugHerd" and `created-date.from` set to the start of the period. Read the task number from each title prefix.
**Step 3: Pair them up**
For each link, read the other side: `github-get-issue` with `company` and `issue-number`, or `bugherd-get-tasks` (then `bugherd-get-archived-tasks`) with `project-id` and `task-number`. A task is finished when its status is done or closed or it is archived; an issue is finished when its status is closed.
* **In step:** both open or both finished.
* **Closed on GitHub, open in BugHerd:** the fix may be ready to check on the site.
* **Done in BugHerd, open on GitHub:** the issue is probably stale.
* **Broken link:** the number points at nothing.
**Step 4: Report**
One table per class except "in step" (give that as a count): task number, task title, BugHerd status, issue number, issue status, closed-date, issue-url.
**Rules & Guidelines:**
* Tools named bugherd-... are on the bugherd MCP server; tools named github-... are on the github MCP server. Every GitHub tool takes the repository as its `company` parameter. If either set of tools is missing, say which server is not connected and stop.
* This prompt is read-only. Do not call any BugHerd write tool (`bugherd-add-task`, `bugherd-add-feedback`, `bugherd-update-task`, `bugherd-move-task`, `bugherd-add-comment`, `bugherd-add-attachment-from-url`, `bugherd-add-project`, `bugherd-update-project`, `bugherd-add-project-member`, `bugherd-add-guest-to-project`) or any GitHub write tool (`github-add-issue`, `github-update-issue`, `github-add-issue-comment`, `github-update-issue-comment`, `github-add-issue-assignee`, `github-add-issue-label`, `github-lock-issue`, `github-unlock-issue`, `github-add-milestone`, `github-update-milestone`, `github-enable-workflow`, `github-disable-workflow`, `github-rerun-workflow-run`, `github-cancel-workflow-run`). To act on the result, use `sync-bugherd-github-status`.
**Validation:**
* If there are no links on either side, say so and stop.Who it's for
One answer, three teams that use it
Project managers
Know which fixes need sign off
Find issues closed on GitHub whose BugHerd task is still open, so the client can check them.
Reconcile the Contoso Portal BugHerd project with contoso/portal for the last 30 days.
Developers
Clear out stale GitHub issues
See issues still open on GitHub after the web team signed the task off.
Which GitHub issues in fabrikam/shop are still open while their BugHerd task is done?
QA leads
Fix broken links between tools
Find task references that point at missing issues, before they cause confusion.
List broken links between the Northwind Traders site BugHerd project and northwind/web.
How it works
What PopdockAI does when you ask
You name the BugHerd project and GitHub repository, and your AI assistant checks every linked pair. It only reads, so you decide what to change.
01
Ask
You name the BugHerd project, GitHub repository and how far back to look.
02
Collect
It finds links from BugHerd task references and GitHub issue titles.
03
Compare
It reads both sides of each link and checks whether each is open or finished.
04
Report
It lists drifted pairs and broken links, and counts the pairs in step.
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.
bugherd-get-projects
bugherd-get-tasks
bugherd-get-archived-tasks
github-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
A clear list of drifted pairs to act on
Related use cases
More ways to put this data to work
Send a BugHerd task to a GitHub issue
Ask your AI to send a BugHerd task to GitHub and it opens one linked issue with the page, severity and reporter after you confirm, never a duplicate.
Learn More
Sync BugHerd task and GitHub issue status
Ask your AI to sync BugHerd and GitHub and it proposes status changes for drifted pairs, then applies only the rows you approve, with a comment on each.
Learn More
Check a BugHerd fix has shipped on GitHub
Ask your AI whether a BugHerd task is fixed and it traces the GitHub issue, fixing commits and deploy run to give a clear shipped or not yet verdict.
Learn More
Check BugHerd bugs after a GitHub deploy
Ask your AI what has been reported since the last deploy and it lists new BugHerd bugs and feedback, links likely regressions to GitHub commits, and gives a verdict.
Learn More
BugHerd project status report
Ask your AI for a BugHerd project status report and it summarizes the board, new and archived tasks, the inbox and what is at risk.
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.