-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Impact not updated when quick presets are updated #2014
Comments
@stolpeo can you do a RCA? |
RCAIf a quick preset exists that has not set a value for at least one of the settings and this quick preset is selected, the javascript throws an error and creates an inconsistent state that causes all subsequent quick preset selections to fail. The line that is causing this is located here:
|
Solution
|
RCA 2There is another error that only displays the preset sets in the editor once a case from the project was loaded. It fails if you go directly to the editor (when reloading the page for example) because the caseListStore is only initialized when a case was loaded. Fix is easy. |
Describe the bug
For a particular case (details in internal chat), impact is not adjusted when quick presets are changed.
To Reproduce
See internal channel.
Expected behavior
Impact should be changed.
Additional context
N/A
The text was updated successfully, but these errors were encountered: