jerolomb
jerolomb
**Is your feature request related to a problem? Please describe.** The creation of a blank analysis (model) is linked to a model in the Back office **Describe the solution you'd...
**Describe the bug** Creating a risk analysis, from a model in BO containing information risks -> the information risks are not created in the analysis **To Reproduce** Steps to reproduce...
**Describe the bug** Take an existing analysis. Create a custom referential or use the existing one. Link in the knowledge base a measure to a risk. The measure is well...
**Describe the bug** When you delete some risks in the KB, there are not propagated to the instances_risks table so the anr. It results to an inconsistent DB **To Reproduce**...
Detaching the last component of an object in the library set the positions of root instance (parent_id = null) to position-1. It's probably due to zm-core/src/MonarcCore/Model/Table/InstanceTable::manageDeletePosition https://github.com/monarc-project/zm-core/blob/70a5eefa2cc524057960a116b065408b93513133/src/MonarcCore/Model/Table/InstanceTable.php#L120
**Describe the bug** In the evaluation scale, the logo to hide a scale is the opposite **Expected behavior** Same logo for same action **Screenshots** Exemple here to hide in the...
Exemple : set a question to 20 points set 3 answers with 10 points each It must be usefull to prevent to have 30/20. Just block to 30
The tool has to evolve like the norm : First phase changes: - [ ] In the risk treatment plan, the word “reduction” should be changed to “modification.” (ISO 27005:8.2)...