Pull Request Audit for Jira
A free Jira Cloud app that finds Jira issues whose GitHub pull requests never reached Jira: GitHub has a pull request carrying the issue key, but the issue shows no pull requests at all. It reports an issue only after checking it three ways.
Before you start
- Jira Cloud, and a Jira admin to install the app.
- GitHub for Atlassian (Atlassian's own GitHub integration) connected to your site. Pull Request Audit checks its work; it doesn't replace it.
- Permission to install a GitHub app on the repositories you want checked.
Setting it up
- Install Pull Request Audit from the Atlassian Marketplace. Then open it from Apps in Jira's settings, or click Get started on its entry in Manage apps.
- Click Install on GitHub and choose the repositories that GitHub for Atlassian syncs to this site. Our GitHub app asks only for read access to pull requests and their metadata, never your code.
- Back in Jira, click Connect GitHub. Atlassian asks you to allow the app to use your GitHub sign-in, and GitHub asks you to authorise it. If you can see more than one installation, choose which GitHub account this site should audit.
- Click Run the audit. It reads the last 90 days of pull requests, then checks a second time a few minutes later, so the first result takes a few minutes.
How an issue gets reported
An issue is reported only when all of these hold:
- A pull request at least a day old carries its key in the title or branch name, and the issue exists.
- Jira's search shows no pull requests on it, on two checks some minutes apart.
- The repository is shown to be connected: pull requests from it, created before and after this one, did reach Jira.
- Atlassian's Teamwork Graph, asked when you open the app, also shows no pull requests on it. Jira's search can lag by days; Teamwork Graph settles it.
Anything the app can't be sure of is counted separately and never reported as missing: an error from Jira, a pull request that arrived during the check, one less than a day old, a project where the app can't confirm it sees development data, or a repository not shown to be connected.
Reading the report
For each issue it lists the pull request, when it was opened, the linked pull requests either side of it in the same repository, and when each check ran. It also says how many issues only looked missing because Jira's search was behind.
To bring a missing pull request into Jira, edit its title or push to its branch: GitHub then sends it to Jira again. Our guide GitHub pull requests not showing in Jira? explains why it happens and how to check by hand.
Limits
- It finds issues where Jira shows no pull requests at all. It doesn't yet find partial gaps, where one of several pull requests is missing.
- The app reruns the audit hourly in the background, but the final Teamwork Graph check runs when an admin opens the app, so open it to see current results. It doesn't send alerts.
- It confirms up to 100 suspected issues per visit.
- GitHub.com only, not GitHub Enterprise Server.
Your data
The app runs on Atlassian Forge and keeps what it holds in Forge's storage for your site. It never reads your code. Our privacy policy lists exactly what it holds and for how long, and our security page describes how we protect it.
Disconnecting and uninstalling
Disconnect GitHub on the app's page deletes the connection and stops audits. To remove our GitHub app, uninstall it in your GitHub account's or organisation's settings, under GitHub Apps. Uninstalling the Jira app deletes its storage after 28 days.
Help
Email support@quietpenguin.com. We aim to reply within one working day (Irish time).