All of this has been changed with locking exceptions, so invalidating
this bug.
** Changed in: dhis2
Status: New => Invalid
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/642520
Title:
Data locking doesn't lock
Status in DHIS 2:
Invalid
Bug description:
I locked 1 monthly dataset, at specified month, with specify org unit.
But then I log in by the user of that org unit and edit the data entry
form. And it still saved in to database what I have edited. Is this
right or wrong? Vietnam hasn't used this function. But I thought if
data is lock, mean user can't edit that data value of selected
dataset, period, org unit anymore.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/642520/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
