Skip to content
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

[Front Office] Directly setting up the impacts in the risks view table #521

Open
ruslanbaidan opened this issue Dec 7, 2023 Discussed in #502 · 1 comment
Open

[Front Office] Directly setting up the impacts in the risks view table #521

ruslanbaidan opened this issue Dec 7, 2023 Discussed in #502 · 1 comment

Comments

@ruslanbaidan
Copy link
Contributor

Discussed in #502

Motivation

Monarc users frequently face difficulties when needing to enter the impact levels, because they don’t know how to access them.
It would be more intuitive if the impact table could be directly accessed by clicking on the impact cells.

Possible solution

Based on the fact that it is possible to set impacts only for all the linked risks linked to asset at the same time.
As a solution of direct impact setup in the table view could be - opening the same dialog of impacts edit and set the values for the linked asset's risks, where mouse was clicked.
There could be added a specific message informing about the asset for which the impacts are set and selecting it in the analysis tree.
However, there could be some concerns regarding risks linked to a global assets that are presented in the analysis more then once.

@ruslanbaidan
Copy link
Contributor Author

There are a lot of tooltips for each of the place where the level of impact, threat probability or vulnerability qualification set.
When mouse is hold for 3 seconds on every place, like consequence title or selected numbers there is a descriptive tooltip appears that shows the scales' details and meaning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Low Priority
Development

No branches or pull requests

1 participant