Phase 5 — Verify Your Setup
In this final phase, confirm that LinearB Essentials is correctly ingesting data, attributing activity to users and teams, and producing insights and automation. Goal of this phase: Validate that the…
In this final phase, confirm that LinearB Essentials is correctly ingesting data, attributing activity to users and teams, and producing insights and automation.
Goal of this phase: Validate that the platform is operational and ready for daily use.
Step 1 — Verify Git Activity
Confirm that LinearB is receiving repository activity from your Git provider.
- Go to Dashboards.
- Select a team dashboard.
- Review recent activity.
Expected result:
- Recent pull requests appear
- Commit activity appears for developers
- Repository names match your Git provider
Verify that the correct repositories are selected under Settings → Integrations → Git.
Step 2 — Verify Users and Teams
Confirm that user activity is attributed to the correct users and teams.
- Go to Settings → Users & Teams.
- Review the user list.
- Confirm users belong to the correct teams.
Expected result:
- Developers appear once in the Users list
- Users are assigned to teams
- Activity is attributed to the correct developers
If duplicate users appear, merge them to ensure metrics remain accurate.
Step 3 — Verify AI Insights
If AI Services and AI tools were enabled, confirm that AI insights are appearing.
- Go to AI Insights or AI dashboards.
- Review developer activity.
Expected result:
- AI usage appears for supported tools (Copilot or Cursor)
- Pull requests show AI contribution indicators
- AI insights begin populating dashboards
AI metrics may take time to populate as developer activity is detected.
Step 4 — Verify gitStream Automation
If gitStream automation is enabled, confirm that automation rules are running.
- Create or review a recent pull request in a connected repository.
- Check whether automation actions trigger.
Expected result:
- AI Review or other configured automation appears
- Labels or automation actions apply automatically
- Automation rules run without errors
Step 5 — Verify DORA Metrics (Optional)
If you configured release detection or incident tracking, verify that DORA metrics are populating.
Metrics to confirm:
- Deployment Frequency
- Lead Time for Changes
- Change Failure Rate (optional)
- Mean Time to Restore (optional)
Expected result:
- Deployments appear in LinearB
- Deployment metrics begin populating
- Incident-linked metrics appear if incident data is configured
What Success Looks Like
- Git activity appears in dashboards
- Users and teams are correctly configured
- AI insights appear (if enabled)
- gitStream automation runs on pull requests
- Optional DORA metrics populate if configured
Your organization can now begin using dashboards, AI insights, and automation to improve development workflows and delivery performance.
Next Steps
- Explore Dashboards and team insights
- Expand gitStream automation
- Configure deployment or incident APIs for deeper DORA metrics
- Visit the Learning Hub for additional guides
How did we do?
Phase 4 — Configure DORA Metrics (Optional)