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. For information on accessing the filters listed below, refer to 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

​

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.

Scorecards (table view only)

• Filter Level by Is “No level” to find entities that haven’t reached the first level of a Scorecard yet, a quick way to see where adoption has stalled.
• Filter Level by Is not “Level 3” alongside Entity owner to see which teams still have work left on a migration Scorecard.

​

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.

​

Entity

The filters in this section focus on scoping data to specific entities, entity types, or the groups they belong to.

​

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.

​

Deployments

The filters in this section are specific to deployment metrics and let you scope data by attributes such as deployment status and environment.

​

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.

​

Incidents

The filters in this section are specific to incident-related metrics.

​

Custom metrics

The filters in this section are specific to the custom metrics you created in Cortex.

​

Scorecard (table view only)

The filter in this section applies to table view when a Scorecard column is in the report. Refer to Scorecards in table view for more information.

​

‘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. For information on grouping metrics, refer to 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.

​

Entity

The ‘group by’ options in this section let you segment data by entity-related attributes such as entity type, domain, or group.

​

Version control

The ‘group by’ options in this section are specific to version control metrics and let you segment data by pull request attributes.

​

Deployments

The ‘group by’ options in this section are specific to deployment metrics and let you scope data by attributes such as environment.

​

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.

​

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.

​

Scorecards (table view only)

There are no Scorecard-specific ‘group by’ options. Because Scorecard results are evaluated per entity, adding a Scorecard column limits grouping to the Entity options and relationship groupings. Team and user options aren’t available while a Scorecard column is in the table.

​

Relationships

The ‘group by’ options in this section list the custom entity relationship types defined in your catalog. Each relationship type you’ve configured (for example, a service-to-repository or account-to-resource mapping) appears as its own grouping option. Select a relationship type to group and roll up metrics for entities connected through that relationship. Filtering by relationship isn’t supported yet; these options are available for grouping only.