> ## Documentation Index
> Fetch the complete documentation index at: https://docs.weaveos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Filters and granularity

> Filter your data by date, team, user, and more

Filters let you focus on specific subsets of your data across all Weave reports.

## Filter types

| Filter | Description | Shortcut |
| - | - | - |
| Date | Filter by time range | `D` |
| User | Filter by team member | `U` |
| Team | Filter by team | `T` |
| Repository | Filter by repository | `R` |
| Project | Filter by Jira/Linear project (epic-level) | `P` |
| Jira Spaces | Filter by native Jira project (Jira "space") | `B` |
| AI tool | Filter by AI coding assistant | `A` |

## How to add filters

There are several ways to add filters:

1. **Click the filter bar** at the top of any report
2. **Press `F`** to open the add filter menu
3. **Use shortcuts** like `D` for date, `T` for team, etc.
4. **Use the command menu** (`⌘K`) and search for filters

## Time granularity

Control how data is grouped over time:

| Granularity | Best for |
| - | - |
| Day | Short time ranges, daily standups |
| Week | Most reports (default) |
| Month | Quarterly reviews, long-term trends |
| Quarter | Annual planning |
| Year | Multi-year comparisons |

Press `G` to change granularity, or click the granularity pill in the filter bar.

## Default date ranges

Different reports have different default date ranges:

| Report | Default range |
| - | - |
| Most reports | Last 3 months |
| Standup | Current week |
| R\&D Capitalization | Year to date |

## Combining filters

You can apply multiple filters at once. For example:

* Date: Last 30 days + Team: Backend + Repository: API

Filters are combined with AND logic—data must match all active filters.

The team filter uses each person's team history, so it includes work from people who were on the team at the time, even if they've since moved. If your organization attributes history to current members, the filter instead covers the team's current members across their whole history. See [when people change teams](/reports/team#when-people-change-teams).

## Jira Spaces filter

On Jira-connected organizations, **Jira Spaces** filters metrics to pull requests linked to tickets in the selected native Jira projects (what Jira calls "spaces"). A PR counts if any linked ticket belongs to one of those projects, even when the ticket is not under an epic.

This is separate from the **Project** filter, which targets higher-level Jira/Linear projects (epics and initiatives). Use **Jira Spaces** when you want to slice by Jira board/project keys; use **Project** for roadmap-level groupings.

On Linear-connected organizations, you can also group [code output](/metrics/code-output) by initiative on the [Overview report](/reports/overview). That initiative breakdown is separate from the **Project** filter and applies only to code output metrics.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.