Measure
Scoring settings and rescoring
Manage exclusions and safely reprocess scores after a configuration change.
- Audience
- administrators
- Required role
- Administrator with Measure settings capability.
- Product access
- Measure
- Navigation path
- Measure > Settings > Scoring
Outcome
Change scoring configuration with a reviewable reason and reprocess only the affected work.
Before you begin
- A documented reason for the change
- Examples of pull requests affected by the current behavior
Review defaults
Read the current exclusions and scoring behavior before changing them. Compare representative pull requests to the scoring methodology so a source-data problem is not mistaken for a configuration problem.
Change exclusions
Add only stable generated, vendored, or non-product paths that should not contribute. Broad exclusions can silently remove meaningful work from every Measure view.
Preview impact
Use representative pull requests to verify that the new rule removes the intended evidence and preserves real changes. Record the reason so later administrators can understand the choice.
Request rescoring
Save the settings, then use the available rescore or reanalysis action for the affected scope. Monitor processing status and verify the result before expanding the operation.