Jira Integration
Connect your Jira Cloud account to automatically link pull requests to Jira issues and group them by epic in your weekly changelogs. Coderbuds syncs your Jira projects, epics, and issues so you can see exactly which features shipped each week.
Key Features
Automatic PR Linking
Extracts Jira issue keys like PROJ-456 from PR titles and descriptions to automatically link them.
Epic Sync
Syncs your Jira projects, epics, and issues in the background. Select which projects to track and trigger re-syncs at any time.
Changelog Grouping
Pull requests are grouped under their Jira epics in your weekly changelog, giving you a feature-level view of what shipped.
How It Works
The Jira integration connects via Atlassian OAuth and syncs your project data in the background. Once connected, Coderbuds automatically matches pull requests to Jira issues by scanning PR titles and descriptions for issue keys.
Connect Jira
Authorize Coderbuds via Atlassian OAuth from your Team Settings.
Select Projects
Choose which Jira projects to sync and track issues from.
PRs Linked Automatically
Mention issue keys in your PRs and they're linked instantly.
View in Changelog
See PRs grouped by Jira epic in your weekly changelog.
Setup Guide
Jira Cloud only: This integration works with Jira Cloud (*.atlassian.net). Jira Server and Jira Data Center are not currently supported.
Navigate to Team Settings
Go to your team's settings page and open the Integrations tab. You'll see the Jira section with a "Connect Jira" button.
Authorize with Atlassian
Click "Connect Jira" to start the Atlassian OAuth flow. You'll be redirected to Atlassian to authorize Coderbuds with read access to your Jira Cloud site.
Select Projects to Sync
After connecting, you'll see a list of your Jira projects. Check the projects you'd like to sync and click Save & Sync. Coderbuds will begin syncing epics and issues in the background.
Wait for Initial Sync
The initial sync runs as a background job. Epics are synced first, followed by all issues. You'll see the sync status and last synced timestamp update automatically. Existing PRs are also scanned and linked during this process.
PR Linking
Coderbuds scans pull request titles and descriptions for Jira issue keys using the pattern [A-Z][A-Z0-9]+-\d+. Any matching keys are automatically linked to their corresponding Jira issues.
PROJ-456: Implement payment gateway Bug fix for checkout (closes TEAM-789) [INFRA-123] Update deployment pipeline feat: add search - MOBILE-42
Tip: Include the Jira issue key anywhere in your PR title or description. The key format matches your Jira project key (e.g., PROJ, TEAM, INFRA) followed by a number.
Managing Your Connection
Re-syncing
Trigger a manual re-sync at any time from Team Settings. This fetches the latest epics and issues from Jira and re-links any new PRs.
Changing Synced Projects
You can update which Jira projects are synced at any time. Check or uncheck projects and save to adjust what gets tracked.
Disconnecting
Click "Disconnect" in Team Settings to remove the Jira connection. This revokes the OAuth token and removes all synced Jira data. PR links are preserved for historical reference.
Changelog Integration
Once Jira is connected, your weekly changelog groups pull requests under their associated Jira epics. This gives you a feature-level view of what shipped each week:
- Epics tab groups PRs by their Jira epic, showing which features progressed
- Standalone issues are listed separately when they aren't part of an epic
- AI-generated summaries describe what each epic delivered that week
Using Jira with Linear
Coderbuds supports connecting both Jira and Linear simultaneously. Pull requests can be linked to issues from either tool, and changelogs will show groupings from both providers. This is useful for teams transitioning between tools or using different tools for different workstreams.
Troubleshooting
PRs aren't being linked
Check that your PR title or description contains a valid Jira issue key (e.g., PROJ-456). The key must match a project key from a synced Jira project. Make sure the issue exists and has been synced.
Sync seems stuck
Syncing runs as a background job and may take a few minutes for large projects. Epics are synced first, then issues. If the last synced timestamp hasn't updated after several minutes, try triggering a manual re-sync from Team Settings.
Connection expired
Coderbuds automatically refreshes Atlassian OAuth tokens. If your connection shows as expired, try disconnecting and reconnecting Jira from Team Settings.
Jira Server / Data Center
This integration only supports Jira Cloud (*.atlassian.net). Jira Server and Jira Data Center instances are not currently supported. If you need support for self-hosted Jira, please reach out to our team.
Data & Privacy
Coderbuds requests read-only access to your Jira Cloud site. We sync project names, epic names, issue keys, summaries, and statuses. No issue descriptions, comments, or attachments are stored. OAuth tokens are encrypted and automatically refreshed via Atlassian's refresh token mechanism. You can revoke access at any time by disconnecting from Team Settings. See our Security documentation for more details.