An unknown number of platform users read an incorrect severity number. The issue started on UTC-5 23-06-29 16:47 and was proactively discovered 1.1 months (TTD) later by our engineering team, who noticed the inconsistency while running local automated tests and reported it [1]. The problem was resolved in 4.8 days (TTF) resulting in a total impact of 1.3 months (TTR).
An indentation bug introduced in merge [2] generated an early exit from the function that calculates the severity score of the finding, impacting the max-open-severity-score results.
We solved it by fixing the indentation of the code in a merge request [3].
The bug was not detected before reaching production because the tests that verified the module in charge of calculating the indicator did not cover this particular case; therefore, new tests that covered the module correctly were added [4]. MISSING_TEST