wekan / Tickets / #1289 Error after deleting a user

Anonymous - 2017-10-10

Originally posted by: xet7

@mayjs @huneau

Do you have idea about this?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: mayjs

It seems like we do currently not delete activities and other objects which are associated with the current user.

Afaik, there is no way to delete a user via GUI, which is why this issue did never occur before. I would suggest to add some logic to check if an user exists, and display an appropriate text instead of the username in case it does not.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: ocdtrekkie

This brings up a lot of questions how to properly handled this. Replacing the username of ever deleted user with say "deleted user" leaves a lot of conversations indecipherable. Most sites I recall will leave the username there permanently.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: xet7

Recently Wekan got feature that user can leave board:
https://github.com/wekan/wekan/blob/devel/CHANGELOG.md#v048-2017-10-09-wekan-release

Feature request for Teams/Organizations [#802] includes request for:

Admin Panel: Add/Modify/Remove Teams/Users/Passwords
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: mayjs

@ocdtrekkie that is true, your way would basically only require a variable for every user to mark if it was deleted.

The problem is that we could now have Wekan instances where users were deleted, so I would say the check before displaying the user is required either way.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: ocdtrekkie

"The problem is that we could now have Wekan instances where users where deleted" <- The problem with not having a stable branch. :/

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: ocdtrekkie

But yeah, I think the ideal case would be to replace the deletion method with one that retains the user table data but marks them deleted and hides them from places they should be deleted. @ tagging, the sidebar, etc. Where their username is display, possibly check for deletion and then grey out their name or something.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: xet7

There was some discussion earlier that it would be good to be able to cleanup users etc on Sandstorm also. There are also some regulations like GDPR that require possibility to remove all data of person.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: xet7

I think it's good idea that if there's something broken in MongoDB data, Wekan should be able to fix it and continue working by itself.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: ocdtrekkie

I'd be pretty curious how GDPR actually affects Wekan. Is it mostly based on personal information (of which Wekan likely has little of)? What are you allowed to not delete? Like, can we change a user ID to be their username, and an isDeleted flag, and then dump stuff like their passwords, email addresses, etc.?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: xet7

IANAL, but...

AFAIK currently Trello is only available on USA servers, so some at Europe are looking at migrating to something like Wekan to be GDPR compliant. It will be seen does Atlassian/Trello plan to have servers at EU.

User needs to be able to download all his/her data (in common formats like JSON etc) that some company has on their servers, and also ability to get it deleted in some timeframe. Except for tax data, goverment data, bank info etc. So this is mainly for commercial businesses that have customer data, not for private persons. There are monetary sanctions for those that are not compliant.

In one GDPR talk where I was there was said that deleting info means for all data, in any files, including data in all emails, although that gets complicated when there's many receivers, I have not checked newest info about those.

For Wekan, it mostly means that:

Data encryption [#890] is important

Offline use of Standalone Wekan is important, and it works already

Sandstorm working at offline LAN is important. I did not yet look how to use Sandstorm apps JSON file to download all new apps and update Sandstorm offline. I have run Wekan offline in dev mode, but I don't know is normal mode available offline. Normal install did seem to require open ports and sandcats.io cert.

Support for offline mode [#466] and online sync is important

Currently Wekan is already used to store patient HIPPA data etc as was seen at Hacker News article, etc critical offline data. This brings question about how safe data is at MongoDB, can it be recovered, or could for example SQLite and other databases be used instead. I did not have much success recovering corrupted MySQL data from raw files. There have been some cases that Wekan grains at Sandstorm have been corrupted, I don't know is this because of filesystem corruption on ext4, or could for example ZFS or btrfs be better. Or alternatively some distributed databases that has multiple copies of data, like CockroachDB etc - I have not looked at those yet.

Anyway I presume Wekan usage will grow :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: ocdtrekkie

@xet7 I guess my question is though, is in a given Wekan board, what data is "the user's"? And who is "the user"? Isn't the Wekan board admin the user? Does "the user's data" include any card they added to a Wekan board, or is that now the property of the board admin?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: xet7

@ocdtrekkie

I think we don't need to worry to so much detail, it depends on each Wekan admin's situation and what they need to do. We just make possible to use GUI and API to find, add, edit and delete data, and have some permission settings.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-10

Originally posted by: xet7

If someone want's to take security to extreme with Wekan with encryption [#890] then each users data could be separately encrypted with time-limited keys on hardened operating systems etc.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-20

Originally posted by: xet7

@soohwa

Is this now fixed with your pull request of disable/enable user? I merged it to devel a moment ago.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-31

Originally posted by: ghost

The problem seems no longer occur if you take ownership just before deleting the user. But that's a different problem. The problem is what to do if you want to delete the data belonging to the user instead of transferring them to the administrator? Maybe the admin should be able to define a data purge policy ? In case of deleting a user:

Transfering to the admin

Or delete the datas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-10-31

Originally posted by: xet7

@soohwa

Could you add those options to API ?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-11-02

Originally posted by: ghost

At the moment we do not have a board delete function. What should be the default option for boards that the user has created?

Archiving (not recommended because of the relation with the user)?

Deletion (recommended but in addition it is also necessary to delete the link with the cards where the user is assigned) ?

Transfer to the administrator?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-11-02

Originally posted by: xet7

@soohwa

I don't know about any default for board. I would prefer implementation of all 3 options, and have a choise what to do.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2019-05-22

Originally posted by: DaBlitzStein

I cannot belive this is still happening now.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2019-05-22

Originally posted by: xet7

Moved to here from https://github.com/wekan/wekan/pull/2384

From @DaBlitzStein

when you delete an user breaks the panels and you have to redo all the work because "ghost" users. 2.74.

This occurs even if the user don't have any task. After register and added to a panel.

attach1.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2019-05-22

Originally posted by: xet7

@DaBlitzStein

Thanks for testing new Wekan delete user feature! As usual, new features can have bugs. I don't know does @Akuket have time to look at this. I try to look how to fix this.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2019-07-09

Originally posted by: lhpitn

hi, it lookes like we got the same problem (wecan isntalled using snap on debian), is there any way to access the database and remove the broken reference to that not anymore existing users using the debian shell? We also tryed to export and inport the board to fix that issue but were unable to import it back into wekan (no valid json error ) Thanks in advance.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2021-01-13

Originally posted by: sennewood

In favor of the GDPR it's mandatory for us to be able to delete users.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2021-01-13

Originally posted by: xet7

For those who require this, I recommend funding development of this and other GDPR related features with some amount of money at https://wekan.team/commercial-support/

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Error after deleting a user

Milestone

Searches

Help

#1289 Error after deleting a user

Discussion