Hey there.
I think you’re confusing two (admittedly very similar) concepts.
When you edit the Quality Profile, you change the old, single severity (info, minor, major, critical, blocker) that is applied to every issue of a given rule in the Quality Profile. You can actually see this severity reflected in the issue.
So that seems to be working as dxpected.
What I think you’re really trying to change is the Issue Impact—a new way of displaying severity with only three values (low, medium, and high) and assigned to a software quality. An issue can be associated with multiple software qualities with differing issue impacts (medium impact on reliability, high impact on security, as an example).
You can read a bit more about this change here:
Issue Impacts are not modifiable today, and I’m not sure they will be tomorrow.
That said, we’re currently reviewing these changes before our LTA release this Fall (we know they have been disruptive for some users), and I’ll flag this thread for our PMs.
Can you explain your motivation for changing the severity on the rule? Is it to prevent QGs from failing, because you regularly filter on issues of a specific severity…