dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Okay, it could be that an upgrade routine is misbehaving. I cannot
reproduce this on 2.21 though.

On Thu, Oct 22, 2015 at 6:45 AM, Elmarie Claasen <elmarie@xxxxxxxx>
wrote:

> Hi Lars,
>
> We have since discovered that this "reset" of the dataset future period to
> 0 occurs when we restart tomcat on the server.
> We are not sure if the change to allow future period is only stored in the
> current session and not saved in the database but probably not likely...
> We are currently doing investigation on local VM if this is only occurring
> on our servers (which would point to some server config issue) or if also
> on local VM then we will have to investigate if it is related to our
> ZA_branch or something in the startup routine that resets the value.
>
> Any ideas? And can you keep the bug report open until we have done some
> further investigation?
>
> Regards,
>
> Elmarie Claasen
>
> Project Manager
> Health Information Systems Program
> Tel:      041-367 1027
> Cell:     082 374 2209
> E-mail: elmarie@xxxxxxxx
> Skype:  elmarie.claasen52
>
>
> This message and any attachments are subject to a disclaimer published at
> http://www.hisp.org/policies.html#comms_disclaimer .   Please read the
> disclaimer before opening any attachment or taking any other action in
> terms of this electronic transmission.
> If you cannot access the disclaimer, kindly send an email to
> disclaimer@xxxxxxxx and a copy will be provided to you. By replying to
> this e-mail or opening any attachment you agree to be bound by the
> provisions of the disclaimer.
>
> -----Original Message-----
> From: Elmarie Claasen [mailto:elmarie@xxxxxxxx]
> Sent: 20 October 2015 08:18 PM
> To: 'Bug 1507529'; 'Lars Helge Øverland'
> Subject: RE: [Bug 1507529] Re: Future period setting for datasets is only
> valid for the number of future periods from the date of saving the dataset
>
> Hi Lars,
>
> Yes we are sure - we set those future periods to =1 last month in
> September so that we could capture September data but then after 1 October
> users could no longer open the current month dataset and when we went to
> look it was reflecting a 0 value. This happened on more than one of our
> provincial instances so pretty sure it was not a once off possible mistake.
>
> We have set them back to 1 now and will check again on 1 Nov and am
> prepared to wait and check then and get back to you on that. Not sure how
> else we can test this right now as the system is probably using server date.
>
> Regards,
>
> Elmarie Claasen
>
> Project Manager
> Health Information Systems Program
> Tel:      041-367 1027
> Cell:     082 374 2209
> E-mail: elmarie@xxxxxxxx
> Skype:  elmarie.claasen52
>
>
> This message and any attachments are subject to a disclaimer published at
> http://www.hisp.org/policies.html#comms_disclaimer .   Please read the
> disclaimer before opening any attachment or taking any other action in
> terms of this electronic transmission.
> If you cannot access the disclaimer, kindly send an email to
> disclaimer@xxxxxxxx and a copy will be provided to you. By replying to
> this e-mail or opening any attachment you agree to be bound by the
> provisions of the disclaimer.
>
> -----Original Message-----
> From: bounces@xxxxxxxxxxxxx [mailto:bounces@xxxxxxxxxxxxx] On Behalf Of
> Lars Helge Øverland
> Sent: 20 October 2015 08:16 AM
> To: elmarie@xxxxxxxx
> Subject: [Bug 1507529] Re: Future period setting for datasets is only
> valid for the number of future periods from the date of saving the dataset
>
> 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 subscribed to the bug
> report.
> 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
>
>
> --
>
>
> *This message and any attachments are subject to a disclaimer published at
> http://www.hisp.org/policies.html#comms_disclaimer
> <http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the
> disclaimer before opening any attachment or taking any other action in
> terms of this electronic transmission.  If you cannot access the
> disclaimer, kindly send an email to disclaimer@xxxxxxxx
> <disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to
> this e-mail or opening any attachment you agree to be bound by the
> provisions of the disclaimer.*
>


-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
http://www.dhis2.org <https://www.dhis2.org/>

-- 
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