Integrating Jira Server (On-Prem) into LinearB – LinearB Support

This integration allows LinearB to analyze Git activity alongside Jira Server (On-Prem) issues, delivering deep insights into project progress, sprint efficiency, and developer productivity.

To complete this setup, you must be both a Jira Admin and a LinearB Admin.

Project Management integrations are available only on the Enterprise tier.

Overview

Connect Jira Server (On-Prem) to LinearB using OAuth.
Whitelist LinearB IP addresses in your firewall.
Create a Jira Application Link (Generic Application).
Authorize LinearB and allow initial data sync (up to 2 hours).

Steps to Connect Jira Server to LinearB

Step 1: Connect Jira Server to LinearB

Log in to LinearB.
Go to Company Settings.
Select a team from the dropdown.
Open the Project Management tab.
Click Connect next to Jira Server (On-Prem).
Enter your Jira Server URL (for example, https://your-jira-server.com).
Click Test Connection.
Ensure your firewall allows communication with LinearB:
- Inbound: 18.118.232.229, 52.15.80.85
- Outbound: 35.226.140.92

If the connection fails, verify server accessibility and confirm that LinearB’s IPs are allowlisted.

Supported Jira versions: Jira Server 7.0 and later.

Step 2: Configure OAuth authentication in Jira

After the Jira URL is validated, complete the OAuth setup.

Click Connect to start OAuth configuration.
Jira opens in a new browser tab (disable pop-up blockers if needed).
In Jira, go to Application Links and click Create New Link.
Enter https://app.linearb.io as the application URL, then click Continue.
Select Generic Application as the application type.
Ensure Create Incoming Link is enabled.
Exchange credentials between LinearB and Jira:
- Copy values from Step 2 in LinearB into Jira.
- Copy values from Step 3 in LinearB into Jira.
Click Continue in Jira, then Approve in LinearB.

Once authorized, LinearB begins syncing Jira data. Initial backfill may take up to 2 hours.

Step 3: Configure rate limiting (if enabled)

If rate limiting is enabled on your Jira Server, LinearB recommends the following minimum settings:

Requests per user: 120 requests per minute
Maximum concurrent requests: 120

These settings help prevent throttling and ensure uninterrupted data synchronization.

Benefits of connecting Jira Server to LinearB

Track development progress across Git and Jira.
Identify bottlenecks impacting sprint velocity.
Optimize sprint planning with actionable insights.
Monitor task switching to improve developer focus.

Branch and PR Naming Conventions

To enable Iterations to recognize and match Git work to Jira issues, the Jira issue key (e.g., PROJ-123) must be present in branch names and pull requests (PRs).

Recommended Format <Jira-issue-key>-<descriptive-title>

Example Naming Conventions

Jira Issue Key	Task Description	Branch Name
LINB-397	Add repository backfill status	`LINB-397-add-repository-backfill-status`
LINB-603	Improve Dockerfiles for better layering	`LINB-603-improve-dockerfiles-layering`
LINB-775	Fix API response handling	`LINB-775-fix-api-response-handling`

For pull requests (PRs), the Jira issue key should also be included:

Example PR Title: Add repository backfill status (LINB-397)

How Iterations Matches Git Work to Jira Issues

Iterations automatically scans Git branches, PR titles, and commits for Jira issue keys. The matching algorithm follows these rules:

Branch Names
- If the branch name includes a valid Jira issue key, Iterations will automatically associate it with the correct Jira issue.
Pull Request (PR) Titles
- If the PR title contains the Jira issue key, Iterations will match the PR to the issue—even if the branch name does not follow the convention.
Commit Messages
- Including the Jira issue key in commit messages adds an additional reference for tracking but is not required.

Example Matching Scenario:

Jira Issue: "Repository selection - backfill and statuses"
Jira Issue Key: "LINB-397"
Matching Branch Names:
- LINB-397-add-repository-backfill-status
- LINB-397-repository-status-enrichment

Both of these branches (even from different repositories) will be linked to LINB-397 in Iterations.

Handling Issues with Subtasks

If a parent Jira issue has multiple subtasks, Iterations will associate branches and PRs with either:

The parent issue key, or
The subtask issue keys

Example:

Parent Jira Issue: "Improve Dockerfiles for better layering"

Parent Issue Key: LINB-603
Subtasks:
- LINB-775 (Optimize Docker image size)
- LINB-776 (Improve build caching)

Branch Matching Rules for Subtasks:

Branch Name	Linked Issue in Iterations
`LINB-603-improve-dockerfiles-layering`	LINB-603 (Parent Issue)
`LINB-775-optimize-docker-image-size`	LINB-775 (Subtask)
`LINB-776-improve-build-caching`	LINB-776 (Subtask)

Iterations will match both the parent and subtask issue keys to the parent Jira issue in Iterations view.

Benefits of Using Naming Conventions

Automatic Issue Linking – No need for manual tracking in Iterations.
Improved Iterations Tracking – Ensures all relevant work is reflected in LinearB’s Iterations view.
Better Collaboration – Teams can quickly identify which Git branches and PRs relate to specific Jira issues.
Consistent Workflow – Standardized naming reduces confusion and enforces best practices across repositories.

Best Practices

✔ Always include the Jira issue key when creating a branch.

✔ Use clear, descriptive titles to specify the task being worked on.

✔ Ensure the PR title contains the Jira issue key if the branch name does not follow conventions.

✔ Maintain consistency across teams and repositories.

✔ Educate developers on the importance of naming conventions to ensure Iterations tracks work accurately.

Troubleshooting

Confirm Generic Application is selected in Jira.
Verify Create Incoming Link is enabled.
Ensure firewall rules allow LinearB IP addresses.
Confirm Jira Server version is 7.0 or later.
Retry setup after disabling pop-up blockers.

For additional assistance, please contact support .