Skip to main content

Phase 5 — Verify Your Setup

In this final phase, confirm that LinearB is correctly ingesting data, attributing work to teams, and producing accurate metrics. Goal of this phase: Validate that the platform is fully operational a…

Steven Silverstone
Updated by Steven Silverstone

In this final phase, confirm that LinearB is correctly ingesting data, attributing work to teams, and producing accurate metrics.

Goal of this phase: Validate that the platform is fully operational and ready for organization-wide use.

Estimated time: 5–15 minutes
Note
After connecting repositories, LinearB may take time to backfill historical data depending on repository size.

Step 1 — Verify Git Activity

Confirm that LinearB is receiving commit and pull request data from your Git provider.

  1. Go to Dashboards
  2. Select a team dashboard
  3. Confirm pull requests and commits appear

Expected result:

  • Recent pull requests appear in dashboards
  • Commit activity appears for developers
  • Repository names match your Git provider
  • Repositories show recent activity

Step 2 — Verify Work Item Linking

Confirm that work items from your project management tool are linked to pull requests.

  1. Open a pull request inside LinearB
  2. Check the associated work item or ticket

Expected result:

  • PRs show linked Jira/Azure/Shortcut tickets
  • Cycle Time metrics reflect the full development lifecycle
Tip
Ensure branch names reference issue keys (for example PROJ-123) so LinearB can correctly associate commits and pull requests with work items.

Step 3 — Verify Team Dashboards

Confirm that teams display accurate activity and metrics.

  1. Navigate to Dashboards
  2. Select multiple teams
  3. Review the metrics displayed

Expected result:

  • Teams show pull request activity
  • Metrics are populated
  • Users appear under the correct teams
  • Repositories are mapped to the appropriate teams

Step 4 — Verify Delivery Metrics

Confirm that key delivery metrics are calculated correctly.

Metrics to check

Expected result:

  • Metrics display realistic values
  • No metrics show as zero or missing
If metrics appear incorrect
Review release detection settings, branch exclusions, and team repository mappings configured in Phase 2.

Step 5 — Verify DORA Metrics (Optional)

If you configured release detection and incident tracking, verify that DORA metrics are functioning.

Metrics to confirm

Expected result:

  • Deployment events appear
  • Lead Time reflects merged-to-deploy duration

Step 6 — Verify AI Analytics (Optional)

If AI services and AI tools were enabled, confirm that AI analytics are functioning.

  1. Go to AI Analytics
  2. Check AI adoption dashboards

Expected result:

  • AI tools appear in the usage panel
  • AI metrics begin collecting data
Note
AI metrics may take time to populate as activity is detected.

Step 7 — Verify Notifications & Automation (Optional)

If WorkerB or gitStream was enabled, confirm that automation features are functioning.

WorkerB

  • Notifications appear in Slack or Microsoft Teams
  • Insights are delivered to configured channels

gitStream

  • Automation rules appear in gitStream
  • Rules trigger based on pull request conditions

What Success Looks Like

  • Git activity appears in dashboards
  • Work items link to pull requests
  • Teams show accurate activity
  • Delivery metrics are populated
  • Optional automation features function correctly
Your LinearB setup is complete.

Your organization can now begin using LinearB dashboards, insights, and automation to improve engineering productivity and delivery performance.

Next Steps

Once setup is complete, you can explore additional LinearB capabilities.

  • Explore Dashboards and delivery insights
  • Define Goals for engineering performance
  • Use Surveys to measure developer experience
  • Expand gitStream automation

How did we do?

Phase 4 — Enable Automation & Insights

Contact