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

Sort order for operational risks in final deliverable annex D #111

Closed
ThierryPGT opened this Issue Jul 16, 2018 · 7 comments

Comments

3 participants
@ThierryPGT

ThierryPGT commented Jul 16, 2018

The current order for operational risks is very difficult to understand, no real logic.

For GDPR compliance rapport, it would be very usefull to order the table as the assets appear in the risk analysis,"For example :
capture

In this case it would be :
Gouvernance
DPO
Licéité et légitimité
Consentement
Intérêt légitime
Droit à l'information
..

Thanks in advance
Thierry

@jerolomb

This comment has been minimized.

Contributor

jerolomb commented Jul 19, 2018

In fact there is a logic. It's the following : The sort is on the MAX risk (to avoid scrolling in case of risks are not evaluated), so for exemple if you have the "Droit à la limitation du traitement" which have the highest value in its risk. It will be first in the table.

As the sort is at least than describe above or is there a bug ?

So we ll study your request.

@ThierryPGT

This comment has been minimized.

ThierryPGT commented Jul 19, 2018

Ok I undestand.
It's not a bug at all.
The annex A is the only proof, where you can find consultant notes.
If there is some risks not evaluated, I think (now) that they must appear in the Deliverable. because it's a choice.
I think that, if there no other reasons to sort Max --> Min
The order of risks in the analysis as sense. For GRPD, when you want to see all risks for a treatment the only way is to cut and copy data in the annex A. If the order is the same of the analysis, it's become very easy.

@ThierryPGT

This comment has been minimized.

ThierryPGT commented Jul 20, 2018

Another thing is the same range.
If you export risk-op in csv, it's the same problem
capture
It this case, it's better to insert the whole path of object to know the hierarchical structure
CU
Thierry

@jfrocha

This comment has been minimized.

Contributor

jfrocha commented Jul 24, 2018

We have created a new tag for operational risks ordering by Id of risk. ${TABLE_AUDIT_RISKS_OP_ORDER_BY_POSITION}

It is not by default in third deliverable, so you need customize your template.

We will check for CSV export.

Commit related : monarc-project/zm-client@586aa45

@ThierryPGT

This comment has been minimized.

ThierryPGT commented Aug 27, 2018

Hello,
sorry but It dont work :-(
This is a basic Case
capture
Here the first page of the deliverable :
capture.

Here the json file if jour want to test :

Thanks in advance
CU

Thierry

@jfrocha

This comment has been minimized.

Contributor

jfrocha commented Oct 23, 2018

We improved sort order of operational risks.
The Tag ${TABLE_AUDIT_RISKS_OP_ORDER_BY_POSITION} is not longer use.
Get back to default tag.
Commit related

@jfrocha

This comment has been minimized.

Contributor

jfrocha commented Oct 23, 2018

FIX some issue with the order of the table
monarc-project/zm-client@3f72b5e

@jfrocha jfrocha closed this Oct 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment