dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi Lars,
This issue is continuing to plague our installations, even on 2.12.
Could we add some sort of warning like "Are you sure you want to add a
new root?" when people attempt to add a new root? After a recent
training, we ended up with about 10 new roots, which was absolutely
not the intention of the users.

Regards,
Jason


On Mon, Aug 20, 2012 at 3:10 PM, Lars Helge Øverland
<larshelge@xxxxxxxxx> wrote:
> Hi Jason, thanks for the report. I have tested a bit and maybe found the error.
>
> Currently the org unit tree only allows you to unselect by clicking on
> the root org unit (you cannot unselect by clicking on any other org
> unit in the tree). This was done to make it possible to create
> multiple roots in the tree. A user assigned to the root can see all
> new roots being made.
>
> An unwanted effect of this is that a user assigned to an org unit
> lower in the tree (e.g. a district) can also unselect the current org
> unit by clicking on that district. So when creating a new org unit,
> after unselecting the current org unit, it will be created at the same
> level as the district. But the user is only assigned to the district
> and is thus prohibited to see other org units at the same level -
> giving the impression that the newly created org unit disappeared in
> thin air.
>
> The fix to this problem is to only allow unselect of org units for the
> root of the full org unit hierarchy, not for the "virtual" root that
> has been assigned to users lower in three. Will be fixed and
> backported.
>
> Lars
>
>
> On Fri, Aug 17, 2012 at 6:51 AM, Jason Pickering
> <jason.p.pickering@xxxxxxxxx> wrote:
>> Hi Devs,
>>
>> I do not have an exact procedure to recreate this bug,  but it has
>> been reported numerous times by different users which attempt to
>> create an orgunit as a child of an existing orgunit. For some reason
>> (perhaps related to a bad internet connection but no clue really) . I
>> can verify that a new "root" orgunit will be created with a NULL
>> parentid. However, in version 2.8 the newly created root orgunit
>> (which should be a child of an existing orgunit) does not appear.
>> Since I cannot define a procedure for this to happen, I cannot really
>> report this as a bug, but wanted to bring it up for discussion and see
>> if maybe a warning could be added if the parentID is NULL. This is
>> such an uncommon operation, that it might help to justify such a
>> warning.
>>
>> Best regards,
>> Jason
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp