/
/
See all the GitHub code behind a Jira issue
For developers who want every branch, commit and build for an issue key in one view, by asking their AI assistant.
On this page
Connector
Connect Jira, pick your AI tool and paste the prompt.
The problem
Finding the code behind an issue means searching all of GitHub
Answering what code exists for a Jira issue means searching GitHub branches, commits, issues and workflow runs for its key, then checking who wrote it. Partial matches and a Done issue with a failing build are easy to miss.
Without PopdockAI
- Search branches and commits for the key
- Check GitHub issues and workflow runs
- Discard partial key matches by eye
- Work out who wrote the code
With PopdockAI
- The Jira issue is read first
- Branches, commits, issues and runs with the exact key are found
- Commit authors are mapped to Jira users
- Mismatches are flagged, and nothing is changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Trace Jira issue `{issue-key}` into GitHub and report every branch, commit, GitHub issue and workflow run that references it, reading from repository `{repository}` (if blank, use the connector's default repository).
**Step 1: Establish the Jira issue**
Call `jira-get-issue` with `issue-key` set to `{issue-key}`. If nothing comes back, report that the issue does not exist in Jira and stop. Note its summary, status, assignee, project-key and updated-date.
**Step 2: Find the code that references it**
On the github server, with `company` set to `{repository}` when it is given:
1. Call `github-get-branch` with `name.contains` set to `{issue-key}`.
2. Call `github-get-commit` with `message.contains` set to `{issue-key}`.
3. Call `github-get-issue` with `title.contains` set to `{issue-key}`.
4. For each branch found in step 1, call `github-get-workflow-run` with `branch` set to that branch name and `max-records` 5, to get its latest runs.
Match the key exactly as Jira spells it (uppercase project key, hyphen, number). A commit that mentions `ABC-12` does not reference `ABC-123`; discard partial matches.
**Step 3: Map commit authors to Jira users**
For each distinct `author-email` on the matching commits, call `jira-get-user` with `email` set to it. Record the Jira display name, or "no Jira user" when nothing matches.
**Step 4: Report**
* **Jira:** key, summary, status, assignee.
* **Branches:** name, protected, latest run conclusion and url.
* **Commits:** short sha (first 7 characters), date, author (with Jira user), first line of the message, url. Newest first.
* **GitHub issues:** number, title, status, issue-url.
* **Findings:** call out any mismatch, for example the Jira issue is Done but its branch's latest run failed, the Jira issue is To Do but commits exist, or the commit authors do not include the Jira assignee.
**Rules & Guidelines:**
* `jira-get-issue` and `jira-get-user` are on the jira server; every tool whose name starts with github- is on the github server.
* This prompt is read-only. Do NOT call `jira-update-issue`, `jira-add-issue-comment`, `jira-add-issue-remote-link`, `github-add-issue-comment`, `github-update-issue` or `github-rerun-workflow-run`.
**Validation:**
* If GitHub returns nothing on every read, report the issue as having no code references in this repository. Do not treat that as an error.
* If a GitHub read fails as an unknown tool, tell the user the github server is not connected in this client.Who it's for
One answer, three teams that use it
Developers
See what has been done on an issue
Find every branch and commit for an issue before you pick it up or review it.
What code exists in GitHub for API-219?
Engineering managers
Catch Done issues with failing builds
A Done issue whose branch build is failing is called out before release.
Is WEB-1107 done in Jira while its GitHub branch build is failing?
Code reviewers
Check who actually wrote the code
Commit authors are mapped to Jira users, with a flag when the assignee is not among them.
Who committed code for MOB-88, and does it include the Jira assignee?
How it works
What PopdockAI does when you ask
You give the Jira issue key and your AI assistant finds every exact reference in GitHub. You get the code in one view with mismatches flagged, and nothing is changed.
01
Ask
You give the Jira issue key.
02
Read
It reads the issue in Jira.
03
Find
It finds GitHub branches, commits, issues and workflow runs with that exact key.
04
Report
You get the code with authors mapped and mismatches flagged, changing nothing.
What PopdockAI provides
The tools behind the answer
Ready made tools for Jira and one secure connection to your AI tool. No code, no exports.
jira-get-issue
github-get-branch
github-get-commit
github-get-issue
github-get-workflow-run
jira-get-user
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
All the code behind an issue in one view
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)
