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

[FR] Include user/analyst ID in timeline event export (CSV) #65

Closed
cudeso opened this issue Feb 2, 2022 · 4 comments · Fixed by #107 or #108
Closed

[FR] Include user/analyst ID in timeline event export (CSV) #65

cudeso opened this issue Feb 2, 2022 · 4 comments · Fixed by #107 or #108
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@cudeso
Copy link

cudeso commented Feb 2, 2022

Is your feature request related to a problem? Please describe.
The CSV export of the events in the timeline does not contain the user/analyst who added the event. The data can be found via the activity log but it would be great if this is also included in the export.

Describe the solution you'd like
Add "username" to the CSV export in event timeline

@cudeso cudeso added the enhancement New feature or request label Feb 2, 2022
@m-terlinde
Copy link

m-terlinde commented Feb 2, 2022 via email

@cudeso
Copy link
Author

cudeso commented Feb 2, 2022

If you work with multiple analysts on one case it's not always directly known who adds a specific event.
Maybe instead of the username add the userid (integer) for compliancy reasons?

@whikernel
Copy link
Contributor

For now the timeline export is done locally in JS with the data available in the current view. The user name or user ID are not part of it.

The event table actually don't have a created_by field, there's only the last update information. Which means the only way to trace back who created the event is by looking at the activity history. That's a good point, we'll add this field 👍

As for the export, we can try to add another button Download with users identifier int he dropdown.
GDPR compliance is actually a good question since the plafeform registers all activities by default to keep an automatic follow up of the investigations...

@m-terlinde
Copy link

@whikernel I think GDPR compliance regarding user's action isn't so hard. We have a good reason to save the analyst's account in combination with the timeline entry. This ensures transparency through the incident and I agree with @cudeso, that this is essential.

I'd like the option only for the export, because I doubt, that 90 % of the use cases for the export need the user transparency.
E. g. I don't want customers to trace the analysts, etc.

whikernel added a commit that referenced this issue May 8, 2022
whikernel added a commit that referenced this issue May 8, 2022
Adds : 
- Modification history in db for events 
- Display of history in UI 
- Add creation date and user info in timeline export as an option. Fixes #65
@whikernel whikernel self-assigned this May 8, 2022
@whikernel whikernel added this to the v1.4.3 milestone May 8, 2022
@whikernel whikernel linked a pull request May 8, 2022 that will close this issue
@whikernel whikernel mentioned this issue May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants