You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Change impact score — one number for how big a change's effect is #420
As an engineer reviewing a proposed change, I want a quick sense of how big its effect is before reading every card.
What it does
Beside the change impact findings, give one score built from what they already contain: devices added or removed, traffic opened or closed, policy rules broken, fixed or altered, and what could not be compared.
Acceptance criteria
The score is computed from the findings, and the breakdown is shown, so it can always be explained
Opening counts more than closing, matching change impact's existing severity model
A change that could not be fully compared never scores as "small": the score says it is incomplete
"No change" scores zero, and only when nothing could not be compared
Raised for Studio 6 as one of ten features in my area (policy compliance and change impact). Comment here if you disagree with the scope; the acceptance criteria are what I will build to.
Activity