Are you sure this is the case? Could it be that someone just set the "future periods" back to 0? There is no logic in the system that implies this should happen...
-- You received this bug notification because you are a member of DHIS 2 developers, which is subscribed to DHIS. https://bugs.launchpad.net/bugs/1507529 Title: Future period setting for datasets is only valid for the number of future periods from the date of saving the dataset Status in DHIS: New Bug description: When setting a future period for data entry e.g. Dataset = monthly Future period = 1 It will allow data capturing in the current month but by 1st of the next month the future period value is back to zero and you have to reset the future period to allow capturing in the current month. Future periods should remain valid for the number of periods based on the current server date instead of the date on which the change was made. War file details: Version: 2.20 Build revision: 16792 Build date: 2015-09-17 18:35 Can the fix be backported to v2.19 as well if possible To manage notifications about this bug go to: https://bugs.launchpad.net/dhis2/+bug/1507529/+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
