Connectors

/

GitHub

/

Find GitHub commits with no Jira issue
Report
Cross-Connector

Find GitHub work that never reached Jira

For project managers who want every commit traced to a real Jira issue, by asking their AI assistant to check the keys.

Try PopdockAI free
Get a live demo
Find GitHub commits with no Jira issue
Which commits in contoso/web from the last 14 days do not reference an issue in the WEB Jira project?
58 commits checked: 47 tracked, 9 untracked and 2 dangling. - Untracked: 5 by Jordan Lee, 4 by Sam Patel - Dangling: WEB-9999 in commit c7d8e9f does not exist - Dangling: WEB-1404 in commit a9b8c7d does not exist Want the untracked commits listed by author?
GitHub
Sample figures. Your results come from your own account.
github-get-commit
jira-get-issue
jira-get-user

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

GitHub

GitHub
Run it on your own GitHub data.

Connect GitHub, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Work that lands in GitHub but never reaches Jira

Work that lands in GitHub without a Jira key is invisible to planning, and commits citing a key that does not exist mislead everyone. Checking means reading every commit message and validating each key by hand.

Without PopdockAI

  • Read every commit message
  • Pull out Jira keys by hand
  • Check each key exists in Jira
  • Miss untracked work in reports

With PopdockAI

  • Commits are read, ignoring merges, and keys extracted
  • Each key is checked against the Jira project
  • Tracked, untracked and dangling commits are separated
  • Untracked commits are grouped by author, and 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.

Prompt
**Objective:** Find the commits in repository `{repository}` (if blank, use the connector's default repository) from the last `{lookback-days}` days (default 14) that reference no existing issue in Jira project `{project-key}`.

**Step 1: Read the commits**

Call `github-get-commit` with `commit-date.from` set to today minus `{lookback-days}` days and `max-records` 500 (pass `company` = `{repository}` when given). If nothing comes back, report that there were no commits in the window and stop.

**Step 2: Pull the keys out of each message**

A Jira key is `{project-key}`, a hyphen and a number, for example ABC-123, in uppercase. Ignore merge commits whose message starts with Merge.

**Step 3: Confirm the keys exist in Jira**

Call `jira-get-issue` with `project-key` set to `{project-key}` and `max-records` 1000, once. A key found in a commit but absent from that list is a dangling reference. For a single dangling key you want to double-check, call `jira-get-issue` with `issue-key` set to it.

**Step 4: Map authors**

For each distinct `author-email` among the untracked commits, call `jira-get-user` with `email` set to it.

**Step 5: Report**

* **Untracked commits:** grouped by author (with Jira user, or "no Jira user"), each with short sha, date, first line of the message and url.
* **Dangling references:** commits naming a key that does not exist in Jira.
* **Totals:** commits in window, tracked, untracked, dangling.

**Rules & Guidelines:**

* `github-get-commit` is on the github server; `jira-get-issue` and `jira-get-user` are on the jira server.
* This prompt is read-only. Do NOT call `jira-add-issue` to create issues for untracked work; offer to run the escalate-github-issue-to-jira prompt instead.

**Validation:**

* If `jira-get-issue` returns exactly `max-records` rows, the key list may be incomplete. Verify each dangling key individually before reporting it.
* If no commit in the window carries any key, say the team may not reference Jira keys in commit messages rather than listing every commit as untracked.

Who it's for

One answer, three teams that use it

Project managers

Find untracked work

Commits with no Jira key are listed by author, so planning sees all the work.

Which commits in fabrikam/app this month have no APP Jira key?

Tech leads

Fix broken Jira references

Commits citing keys that do not exist are flagged as dangling.

Do any commits in contoso/api reference Jira issues that do not exist in API?

Engineering managers

Check the team follows the process

Untracked commits by author show where the commit convention is slipping.

Group untracked commits in northwind/web from the last 30 days by author, using the WEB project.

How it works

What PopdockAI does when you ask

You name the repository, the Jira project and a period, and your AI assistant checks every commit's Jira reference. If no commit has a key it says the team may not use them.

01

Ask

You name the repository, the Jira project and a lookback period.

Your AI tool

02

Read

It reads commits, ignoring merges, and pulls out the Jira keys.

github-get-commit

03

Check

It confirms each key exists in Jira and maps authors to Jira users.

jira-get-issue
jira-get-user

04

Report

You get tracked, untracked and dangling commits, and nothing is created.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for GitHub and one secure connection to your AI tool. No code, no exports.

get-data

github-get-commit

Returns GitHub commits from a repository. Filter by SHA, author name, message text and commit date range.
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.
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.
Read only.Nothing in GitHub 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

Planning that reflects what was built

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