Table of Contents
Filtering Team Insights With Git Scope
Refine your dashboards and reports with Git Scope Filtering, ensuring your team’s data remains focused, relevant, and actionable.

Overview
The Git Scope Filtering feature enable team leaders to define which repositories and services their team work on, automatically filtering insights across LinearB. Once configured, all relevant data in Dashboards, Metrics, and Activity pages is automatically filtered. This ensures that insights remain accurate, team-specific, and relevant.
Key Benefits
- Focused Insights – View data relevant to your team’s repositories and services.
- Automated Filtering – Dashboards, reports, and activity pages automatically update based on the configured Git Scope.
- Enhanced Transparency – A Git Scope Banner indicates which data is included or excluded.
- Flexible Management – Team leaders can update or disable Git Scope filters as needed.

Configuring Git Scope for a Team
Step 1: Navigate to Team Settings
1. Click Team Settings in the sidebar menu.
2. Open the Git tab.
Step 2: Assign the Git Scope
1. A list of available repositories and services is displayed.
2. Select the relevant services and repositories your team works on using the checkboxes.
3. Click Save to apply the selected Git Scope across all dashboards and reports.

Managing Git Scope Filtering
Git Scope Banner
• Home, Goals, and Team Activity pages automatically filter data based on your configured Git Scope.
• A Git Scope banner appears to indicate that filtering is enabled.
Banner Details
The banner provides:
- A list of selected repositories and services.
- A button to edit the Git Scope (Admins and Editors only).
- An option to disable Git Scope Filtering.
Filtering in the Metrics and Activity Page
• The Metrics and Activity Pages (Branches, PRs, Releases, Incidents) are filtered in accorsadance to your team’s Git Scope.
• The selected repositories and services are pre-set in the filters.

FAQs
Can I override Git Scope filtering?
What happens if a contributor works outside the selected Git Scope?
Who can modify the Git Scope?
How did we do?