Connectors

/

BugHerd

/

A person's open work in BugHerd and Jira
Report
Cross-Connector

See one person's real workload across BugHerd and Jira

For project leads who want a person's open BugHerd tasks and Jira issues in one view, just by asking their AI assistant with an email address.

Try PopdockAI free
Get a live demo
A person's open work in BugHerd and Jira
What does priya.shah@contoso.com have open in BugHerd and Jira project WEB right now?
Priya Shah has 14 open items across both systems, 2 of them overdue. - BugHerd: 6 open tasks - Jira WEB: 10 open issues - Linked pairs counted once: 2 - Overdue: WEB-318 Checkout button misaligned, BugHerd task #412 Broken footer link Want the full table of all 14 items?
BugHerd
Sample figures. Your results come from your own account.
bugherd-get-users
jira-get-user
bugherd-get-tasks
jira-get-issue

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

Nobody can see what one person really has on

To see someone's workload you filter BugHerd and Jira separately and add the two lists together. Items sent from one tool to the other count twice, and overdue work on either side is easy to miss.

Without PopdockAI

  • Find the person in BugHerd, then again in Jira
  • Filter each tool to their open items
  • Add the lists by hand and double count linked items
  • Miss overdue work hidden in one of the tools

With PopdockAI

  • The person is found in both tools by email
  • Open tasks and issues are read together, closed work dropped
  • A linked task and issue are counted once
  • Overdue items on either side are flagged, nothing 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:** Show everything open and assigned to the person with the email `{email}`, in BugHerd and in Jira (project `{jira-project-key}` when given, all projects when empty).

**Step 1: Find the person on both sides**

* Call `bugherd-get-users` with `email` set to `{email}`. Take the user-id; if there is no match, note "not a BugHerd user".
* Call `jira-get-user` with `email` set to `{email}`. Take the name; if there is no match, note "not a Jira user".
* If neither matches, say so and stop.

**Step 2: Read open work**

* BugHerd: call `bugherd-get-tasks` with `assignee` set to the user-id and `max-records` 200. Drop done and closed tasks.
* Jira: call `jira-get-issue` with `assignee.contains` set to the person's Jira name, plus `project-key` when given, and `max-records` 200. Drop issues with a Jira status such as Done, Closed or Resolved.

**Step 3: Remove double counting**

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. Count a linked task and issue once, as one item of work.

**Step 4: Report**

1. **Totals:** open items in BugHerd, in Jira, and combined after removing duplicates.
2. **Overdue:** items on either side whose due date has passed.
3. **All open work:** one table with system, key or task number, title or summary, project, severity or status, due date.

**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`).

**Validation:**

* If the person has nothing open in either system, say so.

Who it's for

One answer, three teams that use it

Project managers

Check capacity before you assign more

See everything a person already has open across BugHerd and Jira before handing them another bug, with linked items counted once.

How much open work does sam.patel@fabrikam.com have across BugHerd and Jira? I want to give them the checkout bugs.

Engineering managers

Spot overload before work slips

Find people with overdue items in either tool during one on ones or planning, without opening two dashboards.

Show me the overdue BugHerd tasks and Jira issues for dana.whitfield@contoso.com in project PORTAL.

Team leads

Rebalance work from one table

Get a single table of a person's open work so you can move items to someone else with the full picture in front of you.

List everything open for alex.kim@northwindtraders.com in BugHerd and Jira project NW in one table.

How it works

What PopdockAI does when you ask

You give an email and your AI assistant reads that person's open work in BugHerd and Jira. It only reads, so nothing is changed in either tool.

01

Ask

You give the person's email and, if you like, a Jira project key.

Your AI tool

02

Find

It looks the person up by email in both BugHerd and Jira.

bugherd-get-users
jira-get-user

03

Read

It collects their open tasks and issues and counts linked pairs once.

bugherd-get-tasks
jira-get-issue

04

Report

You get totals, overdue items and one table of all open work.

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

jira-get-user

Returns Jira users with their display name, email address and active status. Use it to resolve a person's name to the account id an assignment needs.
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

jira-get-issue

Returns Jira issues with their project, issue type, status, assignee, reporter, dates and estimates. Filter by project, status, assignee or date range to pull a backlog, a sprint or one person's open work.
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

One honest workload, across both tools

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