/
/
Find BugHerd bugs out of step with their tests
For QA and development teams who want BugHerd tasks checked against the latest Ghost Inspector results, just by asking their AI assistant.
On this page
Connector
Connect Ghost Inspector, pick your AI tool and paste the prompt.
The problem
Bugs closed while tests still fail
BugHerd tasks raised from failing Ghost Inspector tests are easy to lose track of. A test passes but its task stays open, or a task is closed while the test still fails, and nobody notices until a client reports it again.
Without PopdockAI
- Open each BugHerd task raised from a test
- Find that test's latest run
- Compare status and result by hand
- Hear about it again from the client
With PopdockAI
- Open and archived tasks raised from tests are read
- Each test's latest result is checked against its task
- Fixed but open, closed but failing and orphaned are listed
- Pairs in step are counted, and nothing is run or changed
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 BugHerd project `{project-name}`, compare every task raised from a Ghost Inspector test with that test's latest result.
A BugHerd task raised from a failing test carries "ghost-inspector:<test id>" in its external-id, so one test never gets two tasks.
**Step 1: Read the linked tasks**
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` and `max-records` 500. Keep tasks whose external-id starts with "ghost-inspector:".
**Step 2: Read each test's latest result**
For each, call `ghost-inspector-get-test-result` with `test-id` and `max-records` 1 (latest first). Note passing and date-created.
**Step 3: Classify**
* **Fixed but open:** the test passes and the task is still open. It can probably be closed.
* **Closed but failing:** the task is done, closed or archived and the test still fails. It was closed too early, or it regressed.
* **In step:** both open and failing, or both closed and passing.
* **Orphaned:** the test no longer exists.
**Step 4: Report**
One table per class except "in step" (give that as a count): task number, title, task status, test name, latest result, result date.
**Rules & Guidelines:**
* Tools named bugherd-... are on the bugherd MCP server; tools named ghost-inspector-... are on the ghost-inspector MCP server. 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 Ghost Inspector tool that runs, changes or comments (`ghost-inspector-execute-test`, `ghost-inspector-execute-suite`, `ghost-inspector-execute-on-demand-test`, `ghost-inspector-add-test-result-comment`, `ghost-inspector-add-suite-result-comment`, `ghost-inspector-update-test`, `ghost-inspector-update-suite`, `ghost-inspector-duplicate-test`, `ghost-inspector-duplicate-suite`, `ghost-inspector-accept-screenshot`, `ghost-inspector-cancel-test-run`, `ghost-inspector-cancel-suite-run`, `ghost-inspector-create-suite`, `ghost-inspector-create-folder`, `ghost-inspector-update-folder`, `ghost-inspector-create-data-source`, `ghost-inspector-update-data-source`). To close a fixed task, use `retest-bug-with-ghost-inspector`.
**Validation:**
* If no task links to a test, say so and stop.Who it's for
One answer, three teams that use it
QA engineers
Reopen bugs that still fail
Closed tasks whose test still fails are listed with the latest result date.
Which closed BugHerd tasks in Contoso Web are for Ghost Inspector tests that still fail?
Project managers
Close bugs that are fixed
Open tasks whose test now passes are ready to close, so the board reflects reality.
Which open BugHerd tasks in Fabrikam Store have a passing Ghost Inspector test now?
Developers
Clear out orphaned tasks
Tasks whose test no longer exists are listed so you can decide what to do with them.
Find BugHerd tasks in Northwind Store raised from Ghost Inspector tests that no longer exist.
How it works
What PopdockAI does when you ask
You name the BugHerd project, and your AI assistant compares every test raised task with its test's latest result. It is read only.
01
Ask
You name the BugHerd project.
02
Collect
It reads open and archived BugHerd tasks raised from Ghost Inspector tests.
03
Compare
It reads each test's latest result and checks it against the task status.
04
Report
It lists fixed but open, closed but failing and orphaned tasks, and counts the rest.
What PopdockAI provides
The tools behind the answer
Ready made tools for Ghost Inspector and one secure connection to your AI tool. No code, no exports.
bugherd-get-projects
bugherd-get-tasks
bugherd-get-archived-tasks
ghost-inspector-get-test-result
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
Bug status that matches the tests
Related use cases
More ways to put this data to work
Log failing Ghost Inspector tests as BugHerd bugs
Ask your AI to log failing tests and it creates one BugHerd task per failing Ghost Inspector test, with the failed step and console errors, after you confirm.
Learn More
Pre-release check with Ghost Inspector and BugHerd
Ask your AI if the site is ready to release and it runs your Ghost Inspector suite after you confirm, checks open BugHerd bugs, and gives go, go with care or hold.
Learn More
Annotate a failed Ghost Inspector suite run
Ask your AI to annotate a failed Ghost Inspector suite run and it finds the latest failed run, checks existing comments, and posts your note once after you confirm.
Learn More
Audit Ghost Inspector test organization
Ask your AI to audit a Ghost Inspector organization and it checks folders, suites, tests and data sources against housekeeping rules, then names the three fixes to make first.
Learn More
Clone a Ghost Inspector test for another environment
Ask your AI to clone a Ghost Inspector test for another environment and it duplicates it once, edits only the copy after you confirm, and reads the settings back.
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.