Skip to main content
Table of Contents

LinearB Admin Post-Setup Configuration Checklist

Refine your LinearB setup with this comprehensive admin checklist, covering user access, Git and PM integrations, cycle time, and best practices to ensure data accuracy and visibility across your organization.

Steven Silverstone
Updated by Steven Silverstone

Welcome to LinearB! Now that your initial setup is complete, this checklist will help you refine your configuration for accurate metrics, actionable insights, and smooth team adoption.

You must be a LinearB Admin to complete most of the steps in this checklist. If you need help, click the Support button in the lower-right corner of the screen.

1. User and Access Management

Add Users and Contributors
  • Users can log into the LinearB platform and view dashboards.
  • Contributors have their Git activity tracked and appear in metrics.

Assign the correct roles: Admin, Editor, or Viewer

Managing Users in LinearB

User Role Permissions Matrix

Troubleshooting User Access
  • User sees incorrect data: They may have accidentally created a separate free account. Contact Support to migrate them.
  • "Account is already registered" error: The user may belong to another org. Support can merge or transfer them.
  • Duplicate contributor accounts: Merge multiple Git identities into one.
    Merge Contributor Accounts

2. Git Integration

Confirm Git is Connected
Add Repositories

If your team uses mono-repos, you may need to enable sub-path filtering. Contact Support for assistance.

Branch Filtering

3. Project Management Integration

Connect Jira or Shortcut

Only Jira Software Management (company-managed) boards are supported. Jira Work Management and Jira Service Management boards are not compatible.

For reliable issue linking, include issue IDs in branch names or PR titles. Example: feature/LB-123-fix-login.

Field Mapping and Filtering
  • Filter issues by component, label, or sprint using regex.
  • Story points default to 1.0 if unset
  • Map custom fields for investment categories.
Incident Management Setup
  • Use connected PM boards to track MTTR and CFR.
Understanding LinearB Issue Data

“This doesn’t look the same as Jira”— LinearB does not iframe Jira. It tracks status transitions and workflow activity, not just board placement.

  • Issues are shown only if they change status during the iteration.
  • Deleted or archived issues may still appear due to previously logged events.
Troubleshooting Issue Statuses
  • My issue shows as "Uncompleted" even though it’s Done: Statuses must be mapped to the Jira “Done” category. Contact Support.
  • My issue is still showing after deletion: LinearB tracks activity via status changes, not issue existence.

Most changes apply to new data only. Previous iterations are not retroactively updated.

4. Team Configuration

Team Setup
Filtering by Iteration (Regex)
  • Use regex to include only sprints relevant to your team when sharing Jira boards.

5. WorkerB Configuration

Slack / Teams Integration
  • Link WorkerB to Slack or Teams in settings.
  • Assign a dedicated channel for each LinearB team.

Slack Settings

MS Teams Settings

Customize Alerts

6. Cycle Time and Release Settings

Cycle Time Configuration
  • Default: Starts with first commit, ends with deployment.
  • Optional: Start with issue “In Progress” status (Jira-based).

Cycle Time Calculation 

Jira-Based Coding Time

Release Detection Methods

Choose how LinearB tracks releases:

  • Git tag (default)
  • Merges to release branches
  • Regex-based tag namesLinearB’s Release AP

Configure Release Detection

7. Project Delivery Trackers

8. Admin Best Practices

  • Revisit Jira filters and mappings quarterly.
  • Review duplicate contributor suggestions monthly.
  • Validate sprint setup and delivery metrics before retrospectives.
  • Encourage teams to use issue keys in branch names.

Troubleshooting Summary

Issue

Resolution

Issue appears after deletion

Status change recorded pre-deletion

Issue marked "Uncompleted"

Status not mapped to Jira Done

Wrong repo/branch

Check Advanced Git Settings

Duplicate accounts

Merge contributors in user settings

User can't see data

May have personal LinearB account

PRs not linked

Branch/PR missing issue key

How did we do?

JIRA-based Coding Time

Service Metrics

Contact