dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

This is confirmed/knows. The underlying problem is that almost all
tables in the system have a foreign key to users due to the sharing
solution, hence we need to check all of them before deleting. One could
argue that users should not be deleted, rather deactivated, since you
don't want to lose the history of actions which the user has performed,
such as creating meta-data, saving data values, etc (i.e. one type of
"attack" would be to create a user, modify lots of data and then delete
the user, hence removing all traces of who made the additions). Will
think some more about this.

** Changed in: dhis2
       Status: New => Confirmed

** Changed in: dhis2
    Milestone: None => 2.20

-- 
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1442042

Title:
  Unable to delete users who had a chart

Status in DHIS 2:
  Confirmed

Bug description:
  Deleting a user who had designed one chart as part of a training
  exercise did not work (user was superuser). The UI provided no clues -
  the "progress bar" just continued ad infinitum.

  Had to inspect the server tomcat log to identify what caused the
  block, then use pgremote to look up the userid, inspect the chart
  table to identify the linked chart, and the remove or modify it.

  The ideal fix for this would be
  (a) notify user that the person to be deleted have existing charts;
  (b) allow user to either delete those charts or to transfer them to another user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1442042/+subscriptions