GitHub Integration
Connect ProductBridge to GitHub to link feedback posts with issues, create GitHub issues directly from feedback, and automatically update post status when linked issues are closed or reopened.
Overview
The GitHub integration is a two-way tracker link between ProductBridge feedback and GitHub issues. It does not import issues as feedback — instead, it gives your product and engineering teams a clean handoff once a piece of feedback is ready to be acted on.
Once connected, you can:
-
Search GitHub issues from any feedback post and link them in one click
-
Create a new GitHub issue directly from a feedback post — complete with a repository picker
-
Auto-sync post status — when a linked issue is closed or reopened in GitHub, ProductBridge updates the corresponding post status based on rules you define
-
Notify voters automatically when a post status changes because of a linked issue update
The sync runs in real time over webhooks. There is nothing to poll, no manual refresh.
The integration works with GitHub.com accounts and organizations via a GitHub App installation.
Prerequisites
-
A GitHub account that can install apps on the target account or organization — installing into an organization may require an organization owner's approval
-
A ProductBridge organization with at least one feedback board and configured post statuses
-
A user with Owner-level admin permissions in ProductBridge to install integrations
Connect GitHub
Open the Integrations page
Sign in to your ProductBridge dashboard and click Connect Sources in the sidebar, then select GitHub from the Project Management section.
Click Connect GitHub
On the GitHub integration page, click Connect GitHub. ProductBridge redirects you to GitHub to install the ProductBridge GitHub App.
Install the app and choose repositories
Pick the account or organization to install into, then choose All repositories or Only select repositories. ProductBridge can only see and work with the repositories you grant here.
Start with only the repositories your engineering team files feedback-related issues in — you can adjust repository access later from GitHub's app settings.
Confirm the connection
After you authorize, GitHub redirects you back to ProductBridge. The integration status updates to Connected and the page shows the connected account and the disconnect option.
Behind the scenes, ProductBridge verifies and stores the app installation — access uses short-lived tokens, and GitHub delivers issue updates to ProductBridge in real time.
Link a feedback post to a GitHub issue
Once connected, every feedback post in your dashboard gets a GitHub Issues section in the post detail view.
Open a feedback post
Click any post in the Feedback view to open the post detail panel. Scroll the right sidebar to find the GitHub Issues section.
Click Link
Click the Link button next to GitHub Issues. A dialog opens with two tabs: Search and Create.
Choose how to link the issue
Use the tab that fits how you usually work in GitHub.
Type any text to search across the repositories the app can access. Each result shows the issue number (for example #142), its repository, and title. Click any result to link it instantly.
Only open issues can be linked. To link a closed issue, reopen it in GitHub first.
Pick a repository, then fill in a title and description. ProductBridge creates the issue in GitHub and links it to the post in one step.
Verify the link
The linked issue appears in the post's GitHub Issues section with its number, repository, and current state. From there you can open it on GitHub or unlink it.
Status sync rules
Linking is most powerful when GitHub issue changes flow back into ProductBridge automatically. Status sync rules translate GitHub issue states into ProductBridge post statuses.
A rule answers three questions:
-
When a linked GitHub issue changes to state X
-
Should the post change to a specific ProductBridge status (for example, In Progress → Complete)?
-
And should we notify everyone who voted for this post?
If a post has multiple linked issues, you also pick whether the rule fires when any issue reaches the trigger state, or only when all issues do.
Create a rule
Open the GitHub settings page
Go back to Connect Sources > GitHub. Below the connection details, you'll see the Rules section.
Click Create New Rule
Click Create New Rule. A sentence-style builder appears so you can read the rule in plain English as you build it.
Build the rule
Pick the values left to right:
| Field | What it does |
|---|---|
| any / all | Whether the rule fires when any linked GitHub issue hits the trigger state, or only when all do |
| GitHub state | The issue state that triggers the rule — GitHub issues have exactly two: open and closed |
| Post status | The ProductBridge feedback status the post should change to |
| Notify / Do not notify voters | Whether to send in-app and email notifications to voters when the rule fires |
Unlike Jira or Linear, GitHub has no custom workflow states — an issue is either open or closed. The most common rule is: when any linked issue becomes closed, mark the post Complete and notify voters.
Save the rule
Click Create. The rule appears in the list and is active immediately. New GitHub issue changes that match it start syncing right away.
How rule evaluation works
When a linked issue is closed or reopened in GitHub:
-
GitHub sends an issue webhook to ProductBridge
-
ProductBridge finds every feedback post that links to that issue
-
For each rule on the integration, it checks whether the any/all condition is satisfied
-
If a rule matches, the post status is updated and (optionally) voters are notified
Rules are evaluated independently per post, so closing a single GitHub issue can update many posts at once.
Behavior to expect
| Action in GitHub | Effect in ProductBridge |
|---|---|
| Close or reopen a linked issue | Linked issue badge on the post updates; rules evaluated; notifications fired if configured |
| Action in ProductBridge | Effect in GitHub |
|---|---|
| Link an existing issue | A reference is stored on the feedback post; nothing changes inside GitHub — no comments added |
| Create an issue from a post | A new issue appears in the chosen repository with the title and description you provided |
| Unlink an issue | The reference is removed; the GitHub issue itself is not deleted or modified |
| Disconnect the integration | Syncing stops; existing post-issue links remain on the post but stop receiving status updates |
Disconnect GitHub
To stop syncing:
Go to the GitHub integration page
Open Connect Sources > GitHub and click Disconnect.
Confirm disconnection
ProductBridge marks the integration as disconnected so no new syncs run, and leaves the existing per-post issue links in place — your feedback posts keep their reference to the GitHub issue even after disconnect, so you don't lose history. They simply stop receiving status updates.
To revoke ProductBridge's repository access as well, uninstall the app from GitHub under Settings > Integrations > Applications on the account or organization where you installed it.