> For the complete documentation index, see [llms.txt](https://docs.cortex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.io/improve/eng-intelligence/data-explorer/data-explorer-reference.md). # Data Explorer reference Filter options vary depending on the metric you're viewing. For example, the **Opened PRs** metric shows version control filters, while **Story points completed** shows project management filters. For information on selecting a metric, see [Available metrics in Data Explorer](/improve/eng-intelligence/data-explorer/available-metrics-in-data-explorer.md#accessing-metrics-in-data-explorer). For information on accessing the filters listed below, refer to [Filtering and grouping metrics](/improve/eng-intelligence/data-explorer.md#step-2-filtering-and-grouping-metrics). ## Filter operators and selectors Some filters support operators and/or selectors. Select an operator/selector from the drop-down menu next to the filter name, then enter a value or values to define the range or condition. ### Numeric operators Available numeric operators: * Equals, Does not equal, >, ≥, <, ≤, Is between, Is empty, Is not empty Numeric operators are found on the following filters: * **Version control** - Lines added, Lines deleted, Files changed, Number of comments, Commits, Cycle time, PR size * **Deployment** - Duration * **Incident** - Time to resolution * **Project management** - Story points, Time spent, Original estimate, Remaining estimate, Number of comments ### String operators Available string operators: * Is, Is not, Is empty, Is not empty, Contains, Excludes String operators are found on the following filters: * **Teams & Users** - Inherited team, User, Team, User label, User label name, Assignee, Assignee team, Assignee user label, Deployer, Incident assignee * **Entity** - Inherited domain, Inherited team owner, Domain, Entity, Entity type, Group, Entity owner * **Version control** - Label * **Deployment** - Environment, Status * **Project management** - Component, Label, Sprint, Status, Work item type {% hint style="info" %} Because they can never be empty, the following three filters have a slightly reduced set of operators **(**no **Is empty** / **Is not empty**): * **Version control** - Repository, Status * **Project management** - Project One filter has its own set (**Equals**, **Does not equal**, **Is empty**, **Is not empty**): * **Version control** - Draft {% endhint %} ### Role selectors The Author/Reviewer role selector is found on the following filters: * **Version control** - User, Team, User label, User label name ## Example filter scenarios Filters are most useful when you combine them to answer a specific question. A few common examples: **Version control** * Filter **Cycle time** by **>** 3 days to find PRs that are taking longer than expected to ship. This can help you spot patterns like review bottlenecks. * Filter **Number of comments** by **Equals** 0 to find PRs that shipped with no review comments, a possible quality or risk signal. * Filter **PR size** by **>** 1,000 lines, or **Files changed** by **>** 10, to see the cycle time for your largest PRs and understand how PR size affects delivery speed. * Filter **Draft** by **Equals** true combined with **Cycle time** by **>** 7 days to catch PRs that have been sitting in draft for a long time, work that's stalled before it even reaches review. **Project management** * Filter **Story points** by **≥** 8 to surface large work items that may need to be broken down into smaller pieces. * Filter **Work item type** by **Is** "Bug" combined with **Time spent** by **>** 3 days to see which bugs are consuming the most engineering time. **Incidents** * Filter **Time to resolution** by **>** 12 hours to identify incidents where response is breaking down. **Deployments** * Filter **Duration** by **>** 30 minutes to spot patterns leading to slow deployments. * Filter **Environment** by **Is** "Staging" combined with **Status** by **Is not** "Success" to catch deployments failing in staging before they'd ever reach production. **Teams and users** * Filter **User label** by **Is** "AI User (last 7 days)" to compare cycle time or PR throughput between people using GitHub Copilot and those who aren't. * Filter **Team** with the **Reviewer** role selector to see how much review load a team is carrying across the org, not just on their own PRs. **Entity** * Filter **Entity type** by **Is** "Service" combined with **Group** by **Is** "Tier 1" to focus metrics on your most critical production services only. ## Filter definitions ### Teams and users The filters in this section focus on scoping data to specific people or teams. Available filters are dependent on the metric being viewed.
FilterDefinition
AssigneeView data for work items assigned to a specific user.
Assignee teamView data for work items assigned to users belonging to a specific team.
Assignee user labelView data for work items assigned to users with a specific user label.
DeployerView data for deployments performed by a specific user.
GroupView data only for entities associated with a specific group.
Incident assigneeView data for incidents assigned to a specific user.
Individual ownerView data for metrics on entities owned by a specific user. For example, if Service X is owned by Marco, filtering by Marco only shows data for Service X even if the work was performed by someone else.
Inherited teamView data for entities whose team is inherited from a parent entity in the hierarchy.
Team

View data for a specific team.

  • For version control metrics, filters by the team of the PR author or reviewer (based on the Version control team types setting).
  • For deployment metrics, filters by the team of the deployer.
  • For incident metrics, filters by the team of the incident assignee.
Team ownerView data for metrics on entities owned by a specific team. Note that this does not include data for entities owned by sub-teams of that team.
UserView data authored by a specified user.
User labelView data authored by users with a specific user label. Cortex automatically creates an AI Usage label for GitHub Copilot usage with values AI User (last 7 days) and Non-AI User (last 7 days).
User label nameView data authored by users with a specific user label value.
### Entity The filters in this section focus on scoping data to specific entities, entity types, or the groups they belong to.
FilterDefinition
Inherited domainView data only for entities whose domain is inherited from a parent entity in the hierarchy.
Inherited team ownerView data only for entities whose team owner is inherited from a parent entity in the hierarchy.
DomainView data only for entities belonging to a specific domain.
EntityView data only for a specific entity.
Entity typeView data only for specific types of entities (such as services or teams).
GroupView data only for entities associated with a specific group.
Entity ownerView data only for entities owned by a specific user or team.
### **Version control** The filters in this section are specific to version control metrics and let you scope data by pull request attributes such as status, label, and repository.
FilterDefinition
LabelView data only for PRs tagged with a specific label.
RepositoryView data only for a specific repository.
StatusView data for PRs in specified statuses.
Lines addedView data for PRs with a specific number of lines added.
Lines deletedView data for PRs with a specific number of lines deleted.
Files changedView data for PRs with a specific number of files changed.
Number of commentsView data for PRs with a specific number of comments.
CommitsView data for PRs with a specific number of commits.
DraftView data filtered by whether PRs are drafts or not.
Cycle timeView data for PRs within a specific cycle time range.
PR sizeView data for PRs within a specific size range (based on total lines of code modified).
### **Deployments** The filters in this section are specific to deployment metrics and let you scope data by attributes such as deployment status and environment.
FilterDefinition
EnvironmentView data only related to a specific environment sent via the deploys API.
StatusView data for deployments in specified statuses.
DurationView data for deployments within a specific duration range.
### **AI tools** There are no AI-specific filters. Only **Teams & Users** and **Entity** filters apply to AI tools metrics. ### **Project management** The filters in this section are specific to project management metrics and let you scope data by work item attributes such as status, type, sprint, and project. {% hint style="info" %} [Unique defaultJQL configurations](/ingesting-data-into-cortex/integrations/jira.md#set-a-default-jql-query-for-your-jira-integration) per entity aren't supported for filtering or segmenting data in Data Explorer. {% endhint %}
FilterDefinition
ComponentView data only for work items assigned to a specific component.
LabelView data only for work items tagged with a specific label.
ProjectView data only for work items belonging to a specific project.
SprintView data only for work items assigned to a specific sprint.
StatusView data for work items in specified statuses.
Work item typeView data for work items of a specific type.
Story pointsView data for work items with a specific story point value or range.
Time spentView data for work items with a specific amount of time logged.
Original estimateView data for work items with a specific original time estimate.
Remaining estimateView data for work items with a specific remaining time estimate.
Number of commentsView data for work items with a specific number of comments.
### **Incidents** The filters in this section are specific to incident-related metrics. {% hint style="info" %} **Team** and **user** filters are only supported for PagerDuty. {% endhint %}
FilterDefinition
Time to resolutionView data for incidents within a specific time-to-resolution range.
### Custom metrics The filters in this section are specific to the custom metrics you created in Cortex.
FilterDefinition
Inherited domainView data only for entities whose domain is inherited from a parent entity in the hierarchy.
Inherited team ownerView data only for entities whose team owner is inherited from a parent entity in the hierarchy.
DomainView data only for entities belonging to a specific domain.
EntityView data only for a specific entity.
Entity typeView data only for specific types of entities (such as services or teams).
GroupView data only for entities associated with a specific group.
Entity ownerView data only for entities owned by a specific user or team.
## 'Group by' definitions 'Group by' options vary depending on the metric you're viewing. For example, the **Cycle time** metric shows version control group by options, while **Story points completed** shows project management group by options. For information on selecting a metric, see [Available metrics in Data Explorer](/improve/eng-intelligence/data-explorer/available-metrics-in-data-explorer.md). For information on grouping metrics, refer to [Grouping metrics](/improve/eng-intelligence/data-explorer.md#grouping-metrics). ### **Teams and users** The 'group by' options in this section let you segment data by specific people or teams. Available options are dependent on the metric being viewed.
Group byDefinition
Team

Group data by team.

  • For version control metrics, groups by the team of the PR author or reviewer (based on the Version control team types setting).
  • For deployment metrics, groups by the team of the deployer.
  • For incident metrics, groups by the team of the incident assignee.
UserGroup data by individual user.
User labelGroup data by user label.
### **Entity** The 'group by' options in this section let you segment data by entity-related attributes such as entity type, domain, or group.
Group byDefinition
EntityGroup data by individual entity.
GroupGroup data by the group the entity belongs to.
DomainGroup data by the domain the entity belongs to.
Entity typeGroup data by entity type (such as services or teams).
Entity ownerGroup data by the user or team that owns the entity.
### **Version control** The 'group by' options in this section are specific to version control metrics and let you segment data by pull request attributes.
Group byDefinition
RepositoryGroup data by repository.
StatusGroup data by PR status.
LabelGroup data by PR label.
### **Deployments** The 'group by' options in this section are specific to deployment metrics and let you scope data by attributes such as environment.
Group byDefinition
EnvironmentThe environment sent via the deploys API.
### **AI tools** There are no AI-specific 'group by' options. Only **Teams & Users** options apply to AI tools metrics. ### **Project management** The 'group by' options in this section are specific to project management metrics and let you segment data by project attributes.
Group byDefinition
ProjectGroup data by project.
SprintGroup data by sprint.
### Incidents There are no incident-specific 'group by' options. **Teams & Users** and **Entity** options apply to incident metrics. ### Custom metrics The 'group by' options in this section are specific to the custom metrics you created in Cortex.
Group byDefinition
DomainThe domain associated with the entity.