dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

** Changed in: dhis2
    Milestone: 2.16 => 2.18

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

Title:
  orgunit-tree-is-incorrectly-persisted-after-editing-user-V2

Status in DHIS 2:
  New

Bug description:
  I've copied the bug description from bug #891005 from 2011 as I have
  exactly the same issue. The only way to regain access to the full
  orgunit tree for the admin seems to be a backup recovery.

  ---

  Hi Morten ,
  I have tried to describe steps to reproduce this bug. I think the procedure will work, but it took me some time to figure out how to reproduce it!

  1)Login as admin
  2)Add a new user "test_user1"
  3)Assing "Data entry clerk"
  4)Assign "Badija"
  5)Press "Add"
  6)Add a new user "test_user2"
  7)Assing "Data entry clerk"
  8)Assign "Badija"
  9)Press "Add"
  10)From the main user screen, edit the "test_user1"
  11)Press "Bo city council", Select in group
  12)Press "Save".
  13)Edit the "test_user2" .

   The orgunit tree which is displayed is not the full orgunit tree of the current user (admin)
   but rather the orgunit tree of "test_user1" which had been edited in the previous step. It is expected
  that what would be shown would be the full orgunit tree from the "admin" user

  Extra credit: Edit the orgunits for the admin user by clicking a few which are displayed and press "Save"
  Log off and login again.
  Go to "Maintenance->Orgunits". The only orgunits which are displayed are the ones which have been assigned with no way to recover the
  full orgunit tree, without direct manipulation of usermemberships by SQL (DELETE FROM usermembership where userinfoid = 13;)

  It would be expected that the admin user should always have access to
  the full orgunit tree regardless of what orgunits have been assigned
  to this user (or that the assignment, and hence data entry capability)
  of the admin user should be disallowed (a la DHIS 1.4) or allowed
  regardless of which orgunits have actually been assigned.

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