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

Create exportCAAT component with wizard for customizing output #120

Closed
lukemalinowski opened this issue Sep 11, 2019 · 1 comment
Closed

Comments

@lukemalinowski
Copy link
Contributor

Full Data: The current function of the CAAT component.

Condensed/Interactive:
Use Case:
A user wants to fold each NIST Sub-Family into single row rather than multiple rows for every result. If they select the condensed mode - we will have a 'wizard model' come out and ask what 'standard text' we want for each column for that Sub-Family Finding - walking them across the spreadsheet.

As the user is walking though each sub-family step - It would be good if we can have another model that has a datatable of the 'detailed results' of those findings for the sub-family that they could open and close for review if needed.

UX consideration: we can we can suggest a 'default' answer -
a) like Severity ( if 8 / 10 are high or they are all the same) or
b) if they have already provided an answer - such as 'System Name' - that is unlikely to change. ( perhaps the last answer is good enough for most cases ).
c) Could use vuetify modal

Once they walk through, they can save it as a csv/xlsx.

Derived from mitre/heimdall-vue#14

@lukemalinowski lukemalinowski changed the title exportCAAT Create exportCAAT component with wizard for customizing output Sep 11, 2019
@aaronlippold aaronlippold reopened this Sep 20, 2019
@Bialogs Bialogs transferred this issue from mitre/heimdall-lite Aug 26, 2020
@aaronlippold aaronlippold added this to the RoadMap milestone Nov 14, 2020
@rbclark rbclark removed this from the RoadMap milestone Nov 18, 2020
@Amndeep7
Copy link
Contributor

It seems like we have a CAAT export so I'm gonna close this issue unless there's something missing from the functionality that currently exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants