Exclusions

These configurations enable you to auto exclude PRs and Commits from the metrics, based on certain conditions.

Auto Exclude PRs by Cycle Time

Here you can set a threshold of cycle time days, and PRs having cycle time more than this will be excluded from all metrics.

Auto Exclude PRs by PR Size

Here you can set a threshold of PR size, and PRs having LoC more than this will be excluded from all metrics.

Auto Exclude PRs by Keywords

Here you can set a keywords which will be searched in certain attributes of the Pull Request - Title, Description, Label - any PRs matching these criteria will be excluded from all metrics.

Auto Exclude PRs by Branches

By setting branch patterns, you can configure that all PRs following the set path of source and destination branches will be auto excluded from all metrics.

This can be done via 2 methods:

• Many to Many mapping

• One to One mapping

Auto Exclude Commits from Metrics

Commits with these keywords will not be counted towards metrics.

Exclude File Types

You can exclude certain file types from any calculation so that unwanted data does skew up the metrics. For more details view Exclusions.

• For our processing and calculations, we automatically exclude files and directories that start or end with the following: .settings, dist, tmp, out-tsc, node_modules, bower_components, .idea, typings, .vscode, vendor/, coverage.

• Additionally, if any files contain the following in their paths, they are also excluded: src, assets, images.

• All of these options can be adjusted on the settings page, where you can also specify additional files to be excluded.

What Happens When Items Are Excluded?

Commits

If a commit is excluded, either manually or automatically:

• It will not be shown in Coding and Cockpit screens.

• It will not be included in the related metric calculations.

• It will continue to be shown in Team Pulse and Dev 360.

Pull Requests

If a PR is excluded, either manually or automatically:

• It will not be shown in Process, Pull Requests, and Cockpit screens.

• It will not be included in the related metric calculations.

• It will continue to be shown in Team Pulse and Dev 360.

Team Pulse and Dev 360 Enhancements

When viewing Team Pulse and Dev 360, you'll have enhanced visibility into excluded activities:

• Included vs. Excluded counts when hovering over the activity chips.

• Visual distinction for excluded activities by blurring the bubbles.

• The activity panel on the right clearly indicates when excluded activities are enabled.

This provides a consistent view of excluded activities across the application while still maintaining visibility into the complete activity history in Team Pulse and Dev 360.

Important Note

For any exclusions, only the ongoing data will reflect the changes, previous data will remain unchanged.