/
/
Catch serious website bugs that never reached Jira
For project leads who want to know which critical and important BugHerd bugs have no Jira issue yet, just by asking their AI assistant.
On this page
Connector
Connect BugHerd, pick your AI tool and paste the prompt.
The problem
Serious website bugs never reach the developers
Serious bugs reported in BugHerd are supposed to reach developers in Jira, but the hand off depends on someone remembering. Checking means searching Jira for every critical task, and bugs logged under a different title are easy to miss.
Without PopdockAI
- Open every critical and important BugHerd task
- Search Jira for a matching issue
- Miss bugs logged by hand under another title
- Find out when the client chases
With PopdockAI
- Open critical and important tasks are read
- Jira is checked for a linked issue, then a task reference
- Similar titles are reported as possible matches, not links
- It only reads, so nothing is created
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Find open critical and important tasks in the BugHerd project `{project-name}` that have no matching issue in the Jira project `{jira-project-key}`.
How the two systems are linked: a BugHerd task created from a Jira issue carries the issue key (e.g. WEB-123) in its external-id. A Jira issue created from BugHerd starts its summary with "[BugHerd <project name> #<task number>]" and has a remote link to the task.
**Step 1: Read the serious bugs**
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` with `project-id`, once with `severity` critical and once with `severity` important. Drop tasks whose status is done or closed.
**Step 2: Check each one against Jira**
* If its external-id starts with `{jira-project-key}-`, it is linked: call `jira-get-issue` with `issue-key` to confirm the issue exists.
* Otherwise call `jira-get-issue` with `project-key` and `summary.contains` set to "[BugHerd" plus the project name and " #" plus the task number.
* If neither finds an issue, call `jira-get-issue` with `project-key` and `summary.contains` set to two or three distinctive words from the task title, to catch issues logged by hand. Report those as "possible match", not as linked.
**Step 3: Report**
1. **Not in Jira:** task number, title, severity, created, assignee, admin-link, sorted by severity then age.
2. **Possible matches:** the task and the Jira issue key and summary that may cover it.
3. **Linked:** a count.
**Rules & Guidelines:**
* Tools named bugherd-... are on the bugherd MCP server; tools named jira-... are on the jira 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 Jira write tool (`jira-add-issue`, `jira-update-issue`, `jira-assign-issue`, `jira-add-issue-comment`, `jira-update-issue-comment`, `jira-add-issue-remote-link`, `jira-add-issue-watcher`, `jira-add-issue-worklog`, `jira-add-issue-vote`, `jira-add-project`, `jira-update-project`). To send a task, use `send-bug-to-jira`.
**Validation:**
* If there are no open critical or important tasks, say so; that is a good result.Who it's for
One answer, three teams that use it
Project managers
Know which bugs still need an issue
Get the serious bugs not in Jira sorted by severity and age, ready to send.
Which critical bugs in the Contoso Portal BugHerd project are not in Jira project PORTAL?
Engineering managers
Make sure nothing serious is missed
Check the hand off from BugHerd before sprint planning, so serious bugs make it in.
Before planning, list important or critical Fabrikam Shop BugHerd bugs with no issue in Jira project SHOP.
QA leads
Catch bugs logged twice by hand
See possible manual matches, so you can link them instead of raising duplicates.
Show possible Jira matches for unlinked critical bugs in the Northwind Traders BugHerd project, Jira key NW.
How it works
What PopdockAI does when you ask
You name the BugHerd project and Jira project key, and your AI assistant checks every serious bug against Jira. It creates and changes nothing.
01
Ask
You name the BugHerd project and the Jira project key.
02
Read
It collects the open critical and important BugHerd tasks.
03
Match
It checks Jira for a linked issue, then for issues with similar titles.
04
Report
You get bugs not in Jira, possible matches and a count of linked tasks.
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
jira-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
No serious bug goes unseen by the dev team
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)
