Linear & Jira

Link pull requests to issues and group them by feature

Issue Tracker Integrations

Connect Linear or Jira Cloud to link pull requests to issues automatically. Coderbuds syncs your projects, epics and issues, then groups pull requests by Linear project or Jira epic on the Shipped tab. You can see which features shipped in each period.

What Connecting Gives You

Automatic PR Linking

Issue keys like ENG-123 or PROJ-456 in PR titles and descriptions link the PR to that issue.

Background Sync

Coderbuds syncs your projects, epics and issues in the background. You choose what to track and can re-sync at any time.

Changelog Grouping

The Shipped tab groups pull requests under their Linear project or Jira epic. You get a feature-level view of what shipped.

Setup Guide

The steps are the same for both tools. Linear asks you to pick teams; Jira asks you to pick projects.

1

Open the Connections tab

Go to your team's settings page and open the Connections tab. Find the Linear or Jira section and its "Connect Linear" or "Connect Jira" button.

2

Authorize Coderbuds

Click the button to start the OAuth flow. You're redirected to Linear or Atlassian to give Coderbuds read access.

3

Choose what to sync

After connecting, you see a list of your Linear teams or Jira projects. Check the ones to sync and click Save & Sync.

4

Wait for the initial sync

The initial sync runs as a background job. The sync status and last synced timestamp update automatically. Existing PRs are scanned and linked during this sync.

Linear

  • Connects with Linear OAuth and gets read access to your Linear workspace.
  • You choose which Linear teams to sync. Coderbuds syncs their projects and issues.
  • Issue keys start with your Linear team prefix, such as ENG, CORE or FE, followed by a number.
  • Pull requests are grouped under their Linear project in the Projects section of the Shipped tab.

Jira

Jira Cloud only: This integration works with Jira Cloud (*.atlassian.net). Jira Server and Jira Data Center are not currently supported. If you need self-hosted Jira, please reach out to our team.

  • Connects with Atlassian OAuth and gets read access to your Jira Cloud site.
  • You choose which Jira projects to sync. Coderbuds syncs their epics first, then all issues.
  • Issue keys start with your Jira project key, such as PROJ, TEAM or INFRA, followed by a number.
  • Pull requests are grouped under their Jira epic in the Epics section of the Shipped tab.
  • Tokens are refreshed automatically through Atlassian's refresh token mechanism.

How PRs Get Linked

Coderbuds scans pull request titles and descriptions for issue keys matching [A-Z][A-Z0-9]+-\d+. Each match is linked to its Linear or Jira issue.

Example PR titles that will be linked:
ENG-123: Add user authentication
Fix login bug (resolves ENG-456)
Bug fix for checkout (closes TEAM-789)
[INFRA-123] Update deployment pipeline
feat: add search - MOBILE-42

Tip: Put the issue key anywhere in the PR title or description.

Where It Shows Up

Once connected, the Shipped tab groups each period's pull requests by feature:

  • Projects section (Linear) and Epics section (Jira) group PRs by project or epic, showing which features progressed
  • Standalone issues are listed separately when they aren't part of a project or epic
  • AI-generated summaries describe what each project or epic delivered in that period

Using Linear and Jira together

You can connect both at the same time. Pull requests can link to issues from either tool, and the Shipped tab shows groupings from both. This helps teams moving between tools, or using different tools for different workstreams.

Managing Your Connection

Re-syncing

Trigger a manual re-sync at any time from Team Settings. It fetches the latest projects, epics and issues, and links any new PRs.

Changing what's synced

Check or uncheck Linear teams or Jira projects at any time, then save.

Disconnecting

Click "Disconnect" in Team Settings. This deletes the stored token and all synced data for that tool from Coderbuds, including the links between pull requests and issues. It does not revoke access on the provider's side. To do that, remove Coderbuds from your Linear workspace's authorized applications, or from your Atlassian account's connected apps.

Troubleshooting

PRs aren't being linked

Check that the PR title or description contains a valid issue key. The prefix must match a synced Linear team or Jira project. Make sure the issue exists and has been synced.

Sync seems stuck

Syncing runs as a background job and can take a few minutes for large workspaces or projects. If the last synced timestamp hasn't changed after several minutes, trigger a manual re-sync from Team Settings.

Connection expired

Coderbuds refreshes OAuth tokens automatically. If the connection still shows as expired, disconnect and reconnect from Team Settings.

Data & Privacy

Coderbuds requests read-only access. We sync Linear team and project names, Jira project and epic names, and each issue's key, summary and status. No issue descriptions, comments or attachments are stored. OAuth tokens are encrypted, and disconnecting from Team Settings deletes the token from Coderbuds. See our Security documentation for more details.